[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <4F5E301D.9030700@wwwdotorg.org>
Date: Mon, 12 Mar 2012 11:19:25 -0600
From: Stephen Warren <swarren@...dotorg.org>
To: Grant Likely <grant.likely@...retlab.ca>
CC: Linus Walleij <linus.walleij@...aro.org>,
Linus Walleij <linus.walleij@...ricsson.com>,
Randy Dunlap <rdunlap@...otime.net>,
Olof Johansson <olof@...om.net>,
Colin Cross <ccross@...roid.com>, Chris Ball <cjb@...top.org>,
linux-doc@...r.kernel.org, linux-mmc@...r.kernel.org,
linux-tegra@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/2] Documentation/gpio.txt: Explain expected pinctrl
interaction
On 03/12/2012 10:32 AM, Grant Likely wrote:
> On Tue, 21 Feb 2012 11:46:03 +0100, Linus Walleij <linus.walleij@...aro.org> wrote:
>> On Mon, Feb 20, 2012 at 7:27 AM, Stephen Warren <swarren@...dia.com> wrote:
>>
>>> Update gpio.txt based on recent discussions regarding interaction with the
>>> pinctrl subsystem.
>>>
>>> Previously, gpio_request() was described as explicitly not performing any
>>> required mux setup operations etc.
>>>
>>> Now, gpio_request() is explicitly as explicitly performing any required mux
>>> setup operations where possible. In the case it isn't, platform code is
>>> required to have set up any required muxing or other configuration prior to
>>> gpio_request() being called, in order to maintain the same semantics.
>>>
>>> This is achieved by gpiolib drivers calling e.g. pinctrl_request_gpio() in
>>> their .request() operation.
>>>
>>> Signed-off-by: Stephen Warren <swarren@...dia.com>
>>
>> Acked-by: Linus Walleij <linus.walleij@...aro.org>
>>
>> Grant can you take this one? I'd prefer for you to have a look at
>> it as well.
>
> I've taken this one, but left the 2nd for Olof.
Grant, did you take V2 of this patch? I assume not since you replied to V1.
For reference, that's:
http://lkml.org/lkml/2012/3/5/533
Thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists