diff options
| author | Nick Dyer <nick.dyer@itdev.co.uk> | 2016-04-25 23:18:52 +0200 |
|---|---|---|
| committer | Dmitry Torokhov <dmitry.torokhov@gmail.com> | 2016-04-25 23:27:57 +0200 |
| commit | eb43335c409543506dd84b59f5c6bdd35cecf2c7 (patch) | |
| tree | d150da86ad97f0121d3ac936c147ea177a7aee8c /drivers/input/input-compat.c | |
| parent | Input: zforce_ts - fix dual touch recognition (diff) | |
| download | linux-eb43335c409543506dd84b59f5c6bdd35cecf2c7.tar.xz linux-eb43335c409543506dd84b59f5c6bdd35cecf2c7.zip | |
Input: atmel_mxt_ts - use mxt_acquire_irq in mxt_soft_reset
If using IRQF_TRIGGER_FALLING, then there is a race here: if the reset
completes before we enable the IRQ, then CHG is already low and touch
will be broken.
This has been seen on Chromebook Pixel 2.
A workaround is to reconfig T18 COMMSCONFIG to enable the RETRIGEN bit
using mxt-app:
mxt-app -W -T18 44
mxt-app --backup
Tested-by: Tom Rini <trini@konsulko.com>
Signed-off-by: Nick Dyer <nick.dyer@itdev.co.uk>
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Diffstat (limited to 'drivers/input/input-compat.c')
0 files changed, 0 insertions, 0 deletions