summaryrefslogtreecommitdiffstats
path: root/drivers/gpio/gpio-f7188x.c
diff options
context:
space:
mode:
authorVladimir Zapolskiy <vladimir_zapolskiy@mentor.com>2019-01-18 10:53:43 +0200
committerLinus Walleij <linus.walleij@linaro.org>2019-01-21 14:59:50 +0100
commit3ae4f3aac05ab9cc7d93ef3e87bb0bd159cb6bfa (patch)
tree60489f26103ceeab411b26b0b3e67c78b9b5e724 /drivers/gpio/gpio-f7188x.c
parentb597c3a939ecc58d69aadd188515fa9549be3144 (diff)
downloadlinux-stable-3ae4f3aac05ab9cc7d93ef3e87bb0bd159cb6bfa.tar.gz
linux-stable-3ae4f3aac05ab9cc7d93ef3e87bb0bd159cb6bfa.tar.bz2
linux-stable-3ae4f3aac05ab9cc7d93ef3e87bb0bd159cb6bfa.zip
gpio: rcar: select General Output Register to set output states
R-Car GPIO controller provides two interfaces to set GPIO line output signal state, and for a particular GPIO line the selected interface is determined by OUTDTSEL bit value. At the moment the driver supports only one of two interfaces, namely OUTDT General Output Register is used to control the output signal. While this selection is the default one on reset, it is not explicitly configured on probe, thus it might be possible that kernel and userspace consumers of a GPIO won't be able to set the wanted GPIO output signal. Below is a simple test case to reproduce the described problem and verify this fix in the kernel on H3 ULCB by setting non-default OUTDTSEL configuration from a bootloader: u-boot > mw.l 0xe6055440 0x3000 1 ... userspace > echo default-on > /sys/devices/platform/leds/leds/led5/trigger userspace > echo default-on > /sys/devices/platform/leds/leds/led6/trigger Signed-off-by: Vladimir Zapolskiy <vladimir_zapolskiy@mentor.com> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
Diffstat (limited to 'drivers/gpio/gpio-f7188x.c')
0 files changed, 0 insertions, 0 deletions