Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755940Ab1BNQCZ (ORCPT ); Mon, 14 Feb 2011 11:02:25 -0500 Received: from mail-gw0-f46.google.com ([74.125.83.46]:34034 "EHLO mail-gw0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755748Ab1BNQCX convert rfc822-to-8bit (ORCPT ); Mon, 14 Feb 2011 11:02:23 -0500 MIME-Version: 1.0 In-Reply-To: <1297698493.965.5475.camel@petert> References: <1294343654-20354-1-git-send-email-ptyser@xes-inc.com> <1297698493.965.5475.camel@petert> From: Grant Likely Date: Mon, 14 Feb 2011 09:02:02 -0700 X-Google-Sender-Auth: ofvjAk76P0c2NLxqCyn5Rm4nB04 Message-ID: Subject: Re: [PATCH 1/3] gpiolib: Add ability to get GPIO pin direction To: Peter Tyser Cc: linux-kernel@vger.kernel.org, Alek Du , Samuel Ortiz , David Brownell , Eric Miao , "Uwe Kleine-K?nig" , Mark Brown , Joe Perches Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1018 Lines: 23 On Mon, Feb 14, 2011 at 8:48 AM, Peter Tyser wrote: > On Thu, 2011-01-06 at 13:54 -0600, Peter Tyser wrote: >> Add a new get_direction() function to the gpio_chip structure. ?This is >> useful so that the direction of a pin can be determined when its >> exported. ?Previously, the direction defaulted to 'in' regardless of the >> actual configuration of the GPIO pin which resulted in the 'direction' >> sysfs file often being incorrect. >> >> If a GPIO driver implements get_direction(), it is called in >> gpio_request() to set the initial direction of the pin accurately. > > I see Grant was just added as a GPIO maintainer, so added him on CC. > > Anything gating getting these 3 patches being picked up? I'll take a look at them later today. g. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/