summaryrefslogtreecommitdiff
path: root/include/asm-generic
diff options
context:
space:
mode:
authorLinus Walleij <linus.walleij@linaro.org>2012-11-21 11:48:09 +0400
committerLinus Walleij <linus.walleij@linaro.org>2012-11-21 13:07:48 +0400
commit316511c0134acec8f4ea730bd1897c7a1124a7c1 (patch)
tree810d6d4444f05b399edf588c16eea1ba188903eb /include/asm-generic
parent2e8b2eab94c35d83bb7da71c63b4695f32ddca88 (diff)
downloadlinux-316511c0134acec8f4ea730bd1897c7a1124a7c1.tar.xz
gpiolib: rename pin range arguments
To be crystal clear on what the arguments mean in this funtion dealing with both GPIO and PIN ranges with confusing naming, we now have gpio_offset and pin_offset and we are on the clear that these are offsets into the specific GPIO and pin controller respectively. The GPIO chip itself will of course keep track of the base offset into the global GPIO number space. Reviewed-by: Viresh Kumar <viresh.kumar@linaro.org> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
Diffstat (limited to 'include/asm-generic')
-rw-r--r--include/asm-generic/gpio.h4
1 files changed, 2 insertions, 2 deletions
diff --git a/include/asm-generic/gpio.h b/include/asm-generic/gpio.h
index ec58fdbddb59..9fd3093d855a 100644
--- a/include/asm-generic/gpio.h
+++ b/include/asm-generic/gpio.h
@@ -283,7 +283,7 @@ struct gpio_pin_range {
};
int gpiochip_add_pin_range(struct gpio_chip *chip, const char *pinctl_name,
- unsigned int offset, unsigned int pin_base,
+ unsigned int gpio_offset, unsigned int pin_offset,
unsigned int npins);
void gpiochip_remove_pin_ranges(struct gpio_chip *chip);
@@ -291,7 +291,7 @@ void gpiochip_remove_pin_ranges(struct gpio_chip *chip);
static inline int
gpiochip_add_pin_range(struct gpio_chip *chip, const char *pinctl_name,
- unsigned int offset, unsigned int pin_base,
+ unsigned int gpio_offset, unsigned int pin_offset,
unsigned int npins)
{
return 0;