diff options
| author | Dmitry Osipenko <[email protected]> | 2020-07-09 20:12:03 +0300 |
|---|---|---|
| committer | Linus Walleij <[email protected]> | 2020-07-16 10:50:40 +0200 |
| commit | e6827bc3faa4da29ddbf48f48d04e87ca7c1c3c7 (patch) | |
| tree | 99513e17a424bfa0f6cb2f0214d2316c4e984159 /tools/perf/util/scripting-engines/trace-event-python.c | |
| parent | 15d9e7e847c04e7e118fc3edb969068b201bd0b3 (diff) | |
gpio: max77620: Initialize hardware state of interrupts
I noticed on Nexus 7 that after rebooting from downstream kernel to
upstream, the GPIO interrupt is triggering non-stop despite interrupts
being disabled for all of GPIOs. This happens because Nexus 7 uses a
soft-reboot, meaning that bootloader should take care of resetting
hardware, but the bootloader doesn't do it well. As a result, GPIO
interrupt may be left ON at a boot time. Let's mask all GPIO interrupts
at the driver's initialization time in order to resolve the issue.
Signed-off-by: Dmitry Osipenko <[email protected]>
Reviewed-by: Andy Shevchenko <[email protected]>
Acked-by: Laxman Dewangan <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Linus Walleij <[email protected]>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions