diff options
author | Daniel Mack <daniel@zonque.org> | 2019-05-07 06:03:46 +0300 |
---|---|---|
committer | Dmitry Torokhov <dmitry.torokhov@gmail.com> | 2019-05-16 02:29:14 +0300 |
commit | b283d0c353dee57869bdff59e0f01500f1316411 (patch) | |
tree | f7d02c0a5a2e4a9aafae611f9c382de25ba3ef8c /drivers/input/misc/da9063_onkey.c | |
parent | 7f7a0208369ff2cc5590acb9b1388e3d1ade98e9 (diff) | |
download | linux-b283d0c353dee57869bdff59e0f01500f1316411.tar.xz |
Input: eeti_ts - read hardware state once after wakeup
For systems in which the touch IRQ is acting as wakeup source, and that do
not support level-driven interrupts, the interrupt controller might not
latch the GPIO IRQ during sleep. In such cases, the interrupt will never
occur again after resume, hence the touch screen appears dead.
To fix this, check for the assertion of the attn gpio, and read form the
controller once in the resume path to read the hardware status and
to arm the IRQ again.
Introduce a mutex to guard eeti_ts_read() against parallel invocations
from different contexts.
Signed-off-by: Daniel Mack <daniel@zonque.org>
Reported-by: Sven Neumann <Sven.Neumann@teufel.de>
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Diffstat (limited to 'drivers/input/misc/da9063_onkey.c')
0 files changed, 0 insertions, 0 deletions