Re: [PATCH 1/2] Documentation/gpio.txt: Explain expected pinctrl interaction

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

On 03/12/2012 10:32 AM, Grant Likely wrote:
> On Tue, 21 Feb 2012 11:46:03 +0100, Linus Walleij <linus.walleij@xxxxxxxxxx> wrote:
>> On Mon, Feb 20, 2012 at 7:27 AM, Stephen Warren <swarren@xxxxxxxxxx> 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@xxxxxxxxxx>
>> Acked-by: Linus Walleij <linus.walleij@xxxxxxxxxx>
>> 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:

To unsubscribe from this list: send the line "unsubscribe linux-tegra" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at

[ARM Kernel]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Photo]     [Yosemite News]    [Yosemite Photos]     [Free Online Dating]     [Linux Kernel]     [Linux SCSI]     [XFree86]

Add to Google Powered by Linux