Thread (3 messages) 3 messages, 2 authors, 2019-05-22

Re: [PATCH] HID: multitouch: handle faulty Elo touch device

From: Jiri Kosina <jikos@kernel.org>
Date: 2019-05-22 10:38:15
Also in: lkml

On Tue, 21 May 2019, Benjamin Tissoires wrote:
On Tue, May 21, 2019 at 3:38 PM Benjamin Tissoires
[off-list ref] wrote:
quoted
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.
Grmbl, I forgot:
Fixes: 01eaac7e5713 ("HID: multitouch: remove one copy of values")
CC: stable@vger.kernel.org # v5.0+
I've now pushed this to for-5.2/fixes. Thanks,

-- 
Jiri Kosina
SUSE Labs
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help