diff options
| author | Benjamin Tissoires <[email protected]> | 2019-05-21 13:38:31 +0000 |
|---|---|---|
| committer | Jiri Kosina <[email protected]> | 2019-05-22 10:37:37 +0000 |
| commit | 81bcbad53bab4bf9f200eda303d7a05cdb9bd73b (patch) | |
| tree | 76314d947dd582c731813e161c439315c98e7d95 /tools/perf/scripts/python/syscall-counts.py | |
| parent | HID: wacom: Sync INTUOSP2_BT touch state after each frame if necessary (diff) | |
| download | kernel-81bcbad53bab4bf9f200eda303d7a05cdb9bd73b.tar.gz kernel-81bcbad53bab4bf9f200eda303d7a05cdb9bd73b.zip | |
HID: multitouch: handle faulty Elo touch device
Since kernel v5.0, one single win8 touchscreen device failed.
And it turns out this is because it reports 2 InRange usage per touch.
It's a first, and I *really* wonder how this was allowed by Microsoft in
the first place. But IIRC, Breno told me this happened *after* a firmware
upgrade...
Anyway, better be safe for those crappy devices, and make sure we have
a full slot before jumping to the next.
This won't prevent all crappy devices to fail here, but at least we will
have a safeguard as long as the contact ID and the X and Y coordinates
are placed in the report after the grabage.
Fixes: 01eaac7e5713 ("HID: multitouch: remove one copy of values")
CC: [email protected] # v5.0+
Reported-and-tested-by: Breno Leitao <[email protected]>
Signed-off-by: Benjamin Tissoires <[email protected]>
Signed-off-by: Jiri Kosina <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/syscall-counts.py')
0 files changed, 0 insertions, 0 deletions