Thread (18 messages) 18 messages, 5 authors, 2012-03-12

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

From: Grant Likely <hidden>
Date: 2012-03-12 16:32:19
Also in: linux-mmc, linux-tegra, lkml

On Tue, 21 Feb 2012 11:46:03 +0100, Linus Walleij [off-list ref] wrote:
On Mon, Feb 20, 2012 at 7:27 AM, Stephen Warren [off-list ref] wrote:
quoted
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 <redacted>
Acked-by: Linus Walleij <redacted>

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.

g.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help