diff options
author | Linus Walleij <linus.walleij@linaro.org> | 2012-11-20 12:40:15 +0100 |
---|---|---|
committer | Linus Walleij <linus.walleij@linaro.org> | 2012-11-21 08:55:03 +0100 |
commit | 3f0f8670608766ef26a178d4e80cad3ce030fecc (patch) | |
tree | d2f192a4a454bd677983c7eb0b88a0016f128bf6 /kernel/Kconfig.hz | |
parent | 5212d096cbed2eae1e442b3f8bf448e6a577af6f (diff) |
gpiolib: let gpiochip_add_pin_range() specify offset
Like with commit 3c739ad0df5eb41cd7adad879eda6aa09879eb76
it is not always enough to specify all the pins of a gpio_chip
from offset zero to be added to a pin map range, since the
mapping from GPIO to pin controller may not be linear at all,
but need to be broken into a few consecutive sub-ranges or
1-pin entries for complicated cases. The ranges may also be
sparse.
This alters the signature of the function to accept offsets
into both the GPIO-chip local pinspace and the pin controller
local pinspace.
Reviewed-by: Stephen Warren <swarren@nvidia.com>
Reviewed-by: Viresh Kumar <viresh.kumar@linaro.org>
Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
Diffstat (limited to 'kernel/Kconfig.hz')
0 files changed, 0 insertions, 0 deletions