From 4b3632517eab79c64c1d043202de7f939590d664 Mon Sep 17 00:00:00 2001 From: David Brownell Date: Mon, 23 Jul 2007 18:43:57 -0700 Subject: [PATCH] --- yaml --- r: 62776 b: refs/heads/master c: be1ff386e768ee4fc19bb7da48cee4fc4cb4e75b h: refs/heads/master v: v3 --- [refs] | 2 +- trunk/Documentation/gpio.txt | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/[refs] b/[refs] index b58a460d13a5..3a60023b7ede 100644 --- a/[refs] +++ b/[refs] @@ -1,2 +1,2 @@ --- -refs/heads/master: 6570c45995a6339597462434a81f358a38941ac4 +refs/heads/master: be1ff386e768ee4fc19bb7da48cee4fc4cb4e75b diff --git a/trunk/Documentation/gpio.txt b/trunk/Documentation/gpio.txt index 218a8650f48d..6bc2ba215df9 100644 --- a/trunk/Documentation/gpio.txt +++ b/trunk/Documentation/gpio.txt @@ -148,7 +148,7 @@ pin ... that won't always match the specified output value, because of issues including wire-OR and output latencies. 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 return zero. Also, using these calls for GPIOs that can't safely be accessed without sleeping (see below) is an error. @@ -239,7 +239,7 @@ map between them using calls like: 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, 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(). These two mapping calls are expected to cost on the order of a single