diff options
| author | Alexandre Courbot <acourbot@nvidia.com> | 2014-10-23 17:27:07 +0900 |
|---|---|---|
| committer | Linus Walleij <linus.walleij@linaro.org> | 2014-10-28 17:30:59 +0100 |
| commit | e3a2e87893125bcd99bd7e1ddf9bfc421e492572 (patch) | |
| tree | 725e03df58827c8eca35ffb787f43921c55046b2 /Documentation/gpio/driver.txt | |
| parent | ee2a9f7f06a5bff86cf3468fe74bf504640cf5e6 (diff) | |
| download | linux-e3a2e87893125bcd99bd7e1ddf9bfc421e492572.tar.bz2 | |
gpio: rename gpio_lock_as_irq to gpiochip_lock_as_irq
This function actually operates on a gpio_chip, so its prefix should
reflect that fact for consistency with other functions defined in
gpio/driver.h.
Signed-off-by: Alexandre Courbot <acourbot@nvidia.com>
Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
Diffstat (limited to 'Documentation/gpio/driver.txt')
| -rw-r--r-- | Documentation/gpio/driver.txt | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/Documentation/gpio/driver.txt b/Documentation/gpio/driver.txt index 31e0b5db55d8..90d0f6aba7a6 100644 --- a/Documentation/gpio/driver.txt +++ b/Documentation/gpio/driver.txt @@ -158,12 +158,12 @@ Locking IRQ usage Input GPIOs can be used as IRQ signals. When this happens, a driver is requested to mark the GPIO as being used as an IRQ: - int gpio_lock_as_irq(struct gpio_chip *chip, unsigned int offset) + int gpiochip_lock_as_irq(struct gpio_chip *chip, unsigned int offset) This will prevent the use of non-irq related GPIO APIs until the GPIO IRQ lock is released: - void gpio_unlock_as_irq(struct gpio_chip *chip, unsigned int offset) + void gpiochip_unlock_as_irq(struct gpio_chip *chip, unsigned int offset) When implementing an irqchip inside a GPIO driver, these two functions should typically be called in the .startup() and .shutdown() callbacks from the |