Fix doc bug noted by Uwe Kleine-König: gpio_set_direction() is long gone, replaced by gpio_direction_input() and gpio_direction_output().
Unified · Split
| @@ -148,7 +148,7 @@ pin ... that won't always match the specified output value, because of · 147 unmodified lines | ||
| 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 @@ map between them using calls like: · 84 unmodified lines | ||
| 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 |