summaryrefslogtreecommitdiffstats
path: root/drivers/gpio
diff options
context:
space:
mode:
authorStephen Warren <swarren@nvidia.com>2012-03-05 17:22:14 -0700
committerGrant Likely <grant.likely@secretlab.ca>2012-03-12 11:27:07 -0600
commit0dc665d426691fd75fe9b6b16295ad0c02677d21 (patch)
treee45f9a48aeab4d1dd3ad20ef175a9d4cedda4ba2 /drivers/gpio
parent46158aad96b0a90b52fd345f89951a50b3d1a81f (diff)
downloadtalos-obmc-linux-0dc665d426691fd75fe9b6b16295ad0c02677d21.tar.gz
talos-obmc-linux-0dc665d426691fd75fe9b6b16295ad0c02677d21.zip
Documentation/gpio.txt: Explain expected pinctrl interaction
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. Cc: Randy Dunlap <rdunlap@xenotime.net> Cc: linux-doc@vger.kernel.org Signed-off-by: Stephen Warren <swarren@nvidia.com> Reviewed-by: Linus Walleij <linus.walleij@linaro.org> Signed-off-by: Grant Likely <grant.likely@secretlab.ca>
Diffstat (limited to 'drivers/gpio')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud