Commit be1ff386 authored by David Brownell's avatar David Brownell Committed by Linus Torvalds

minor gpio doc update

Fix doc bug noted by Uwe Kleine-König:  gpio_set_direction() is long
gone, replaced by gpio_direction_input() and gpio_direction_output().
Signed-off-by: default avatarDavid Brownell <dbrownell@users.sourceforge.net>
Cc: <ukleinek@informatik.uni-freiburg.de>
Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
parent 6570c459
...@@ -148,7 +148,7 @@ pin ... that won't always match the specified output value, because of ...@@ -148,7 +148,7 @@ pin ... that won't always match the specified output value, because of
issues including wire-OR and output latencies. issues including wire-OR and output latencies.
The get/set calls have no error returns because "invalid GPIO" should have The get/set calls have no error returns because "invalid GPIO" should have
been reported earlier in gpio_set_direction(). However, note that not all been reported earlier from gpio_direction_*(). However, note that not all
platforms can read the value of output pins; those that can't should always platforms can read the value of output pins; those that can't should always
return zero. Also, using these calls for GPIOs that can't safely be accessed return zero. Also, using these calls for GPIOs that can't safely be accessed
without sleeping (see below) is an error. without sleeping (see below) is an error.
...@@ -239,7 +239,7 @@ map between them using calls like: ...@@ -239,7 +239,7 @@ map between them using calls like:
Those return either the corresponding number in the other namespace, or Those return either the corresponding number in the other namespace, or
else a negative errno code if the mapping can't be done. (For example, else a negative errno code if the mapping can't be done. (For example,
some GPIOs can't used as IRQs.) It is an unchecked error to use a GPIO some GPIOs can't used as IRQs.) It is an unchecked error to use a GPIO
number that hasn't been marked as an input using gpio_set_direction(), or number that wasn't set up as an input using gpio_direction_input(), or
to use an IRQ number that didn't originally come from gpio_to_irq(). to use an IRQ number that didn't originally come from gpio_to_irq().
These two mapping calls are expected to cost on the order of a single These two mapping calls are expected to cost on the order of a single
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment