diff options
author | Daniel Kurtz <djkurtz@chromium.org> | 2018-02-16 12:12:43 -0700 |
---|---|---|
committer | Linus Walleij <linus.walleij@linaro.org> | 2018-02-22 15:52:19 +0100 |
commit | 12b10f47e56ac94afa4d7ec5a22f67ccdfe2b90e (patch) | |
tree | 7bb41df37b000895a07049557a6ef09133a96dd4 /fs/afs | |
parent | b5520891a3491cd545e698c03874693aded56c1e (diff) | |
download | linux-12b10f47e56ac94afa4d7ec5a22f67ccdfe2b90e.tar.bz2 |
pinctrl/amd: add get_direction handler
On boot, gpiochip_add_data() initializes the FLAG_IS_OUT bit in
desc->flags iff its gpio_chip does not have ->direction_input() handler,
else it is initialized to 0, which implies the GPIO is an "input".
Later, the sysfs "direction" handler will use gpiod_get_direction() to
get the current direction, but if no ->get_direction() handler is
installed, the result will just be the current (initial) value of flags,
which will always be OUT irregardless of the initial register value.
Add a get_direction() handler to pinctrl-amd to fix this and always
provide the correct value for direction.
Signed-off-by: Daniel Kurtz <djkurtz@chromium.org>
Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
Diffstat (limited to 'fs/afs')
0 files changed, 0 insertions, 0 deletions