Eric Lee / smarc-ti-linux-kernel

Download as
Browse Code »

Commit be1ff386e768ee4fc19bb7da48cee4fc4cb4e75b

Authored by David Brownell
Committed by Linus Torvalds
1 parent 6570c45995
Exists in master and in 20 other branches dlt-processor-sdk-linux-03.00.00.04, newt-ti-linux-3.12.y, processor-sdk-linux-01.00.00, processor-sdk-linux-02.00.01, smarc-ti-linux-3.12.10, smarc-ti-linux-3.12.y, smarc-ti-linux-3.14.y, smarc-ti-linux-3.15.y, smarc-ti-lsk-linux-4.1.y, smarct3x-processor-sdk-04.01.00.06, smarct3x-processor-sdk-linux-02.00.01, smarct3x-processor-sdk-linux-03.00.00.04, smarct4x-800-processor-sdk-linux-02.00.01, smarct4x-processor-sdk-04.01.00.06, smarct4x-processor-sdk-linux-02.00.01, smarct4x-processor-sdk-linux-03.00.00.04, ti-linux-3.12.y, ti-linux-3.14.y, ti-linux-3.15.y, ti-lsk-linux-4.1.y

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: David Brownell <dbrownell@users.sourceforge.net>
Cc: <ukleinek@informatik.uni-freiburg.de>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

Showing 1 changed file with 2 additions and 2 deletions Side-by-side Diff

Documentation/gpio.txt
Diff comments   View file @ be1ff38
... ... @@ -148,7 +148,7 @@
148 148 issues including wire-OR and output latencies.
149 149  
150 150 The get/set calls have no error returns because "invalid GPIO" should have
151   -been reported earlier in gpio_set_direction(). However, note that not all
  151 +been reported earlier from gpio_direction_*(). However, note that not all
152 152 platforms can read the value of output pins; those that can't should always
153 153 return zero. Also, using these calls for GPIOs that can't safely be accessed
154 154 without sleeping (see below) is an error.
... ... @@ -239,7 +239,7 @@
239 239 Those return either the corresponding number in the other namespace, or
240 240 else a negative errno code if the mapping can't be done. (For example,
241 241 some GPIOs can't used as IRQs.) It is an unchecked error to use a GPIO
242   -number that hasn't been marked as an input using gpio_set_direction(), or
  242 +number that wasn't set up as an input using gpio_direction_input(), or
243 243 to use an IRQ number that didn't originally come from gpio_to_irq().
244 244  
245 245 These two mapping calls are expected to cost on the order of a single