| commit | c7fc5fbafa5a676813d68b0f24ce980d717eb940 | |
| author | Neil Armstrong <narmstrong@baylibre.com> | |
| Thu, 23 Mar 2017 16:27:28 +0000 (23 17:27 +0100) | ||
| committer | Linus Walleij <linus.walleij@linaro.org> | |
| Tue, 28 Mar 2017 09:40:24 +0000 (28 11:40 +0200) | ||
| tree | 97f2f41c05aab3b57f7f6de612afafe6ff5b3b30 | treesnapshot (tar.gz zip) |
| parent | 5fb7edb38dc7122a4d73980c86f4a4e600a535b4 | commitdiff |
pinctrl: meson: use gpio-ranges from DT
When trying to add a gpio-hog, we enter a weird loop where the gpio-ranges
is needed when gpiochip_add_data() is called but in the current implementation
the ranges are added from the driver afterwards.
A simple solution is to rely on the DR gpio-ranges attribute and remove the
call to gpiochip_add_pin_range().
Signed-off-by: Neil Armstrong <narmstrong@baylibre.com>
Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
When trying to add a gpio-hog, we enter a weird loop where the gpio-ranges
is needed when gpiochip_add_data() is called but in the current implementation
the ranges are added from the driver afterwards.
A simple solution is to rely on the DR gpio-ranges attribute and remove the
call to gpiochip_add_pin_range().
Signed-off-by: Neil Armstrong <narmstrong@baylibre.com>
Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
| drivers/pinctrl/meson/pinctrl-meson.c | diffblobblamehistory |