diff options
author | Thierry Reding <treding@nvidia.com> | 2017-10-16 14:40:23 +0200 |
---|---|---|
committer | Linus Walleij <linus.walleij@linaro.org> | 2017-10-19 22:32:41 +0200 |
commit | 3ee9e605caea401b060a1f9f81343b8bd0952fbd (patch) | |
tree | 2ffd92fd57c1971d096af8b0cf7c25623b7b1426 /drivers/gpio | |
parent | 0747c3ecfbed25cb6e31b09a834091757a3ef866 (diff) | |
download | linux-stable-3ee9e605caea401b060a1f9f81343b8bd0952fbd.tar.gz linux-stable-3ee9e605caea401b060a1f9f81343b8bd0952fbd.tar.bz2 linux-stable-3ee9e605caea401b060a1f9f81343b8bd0952fbd.zip |
pinctrl: armada-37xx: Stop using struct gpio_chip.irq_base
The Armada 37xx driver always initializes the IRQ base to 0, hence the
subtraction is a no-op. Remove the subtraction and thereby the last user
of struct gpio_chip's .irq_base field.
Note that this was also actually a bug and only worked because of the
above assumption. If the IRQ base had been dynamically allocated, the
subtraction would've caused the wrong mask to be generated since the
struct irq_data.hwirq field is an index local to the IRQ domain. As a
result, it should now be safe to also allocate this chip's IRQ base
dynamically, unless there are consumers left that refer to the IRQs by
their global number.
Signed-off-by: Thierry Reding <treding@nvidia.com>
Acked-by: Gregory CLEMENT <gregory.clement@free-electrons.com>
Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
Diffstat (limited to 'drivers/gpio')
0 files changed, 0 insertions, 0 deletions