* Multi-touch USB weird response
@ 2021-07-29 12:57 Jorge Fernandez Monteagudo
2021-07-29 15:06 ` Valdis Klētnieks
0 siblings, 1 reply; 3+ messages in thread
From: Jorge Fernandez Monteagudo @ 2021-07-29 12:57 UTC (permalink / raw)
To: kernelnewbies
[-- Attachment #1.1: Type: text/plain, Size: 8627 bytes --]
Hi all,
I'm using a 5.8.x kernel and an USB multitouch device is reporting a weird response in some situations. I put a coin or some object in the left edge of the touch without entering the working area and then the next taps to the touch are ignored.
With the evtest tool to get all the messages from multitouch I'm reading a lot of EV_MSC events with code MSC_TIMESTAMP. Is it correct? Where this events storm could come from? Maybe is it configurable some way?
# evtest /dev/input/event4
Input driver version is 1.0.1
Input device ID: bus 0x3 vendor 0x2b7f product 0xd200 version 0x110
Input device name: "Advanced Silicon S.A. CoolTouch® System Interface"
Supported events:
Event type 0 (EV_SYN)
Event type 1 (EV_KEY)
Event code 330 (BTN_TOUCH)
Event type 3 (EV_ABS)
Event code 0 (ABS_X)
Value 29660
Min 0
Max 32767
Resolution 106
Event code 1 (ABS_Y)
Value 11404
Min 0
Max 32767
Resolution 188
Event code 47 (ABS_MT_SLOT)
Value 0
Min 0
Max 9
Event code 53 (ABS_MT_POSITION_X)
Value 0
Min 0
Max 32767
Resolution 106
Event code 54 (ABS_MT_POSITION_Y)
Value 0
Min 0
Max 32767
Resolution 188
Event code 57 (ABS_MT_TRACKING_ID)
Value 0
Min 0
Max 65535
Event type 4 (EV_MSC)
Event code 5 (MSC_TIMESTAMP)
Properties:
Property type 1 (INPUT_PROP_DIRECT)
Testing ... (interrupt to exit)
Event: time 1627381396.770902, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 35023100
Event: time 1627381396.770902, -------------- SYN_REPORT ------------
Event: time 1627381396.780891, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 35029400
Event: time 1627381396.780891, -------------- SYN_REPORT ------------
Event: time 1627381396.789895, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 35035700
Event: time 1627381396.789895, -------------- SYN_REPORT ------------
Event: time 1627381396.798896, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 35041900
Event: time 1627381396.798896, -------------- SYN_REPORT ------------
Event: time 1627381396.807889, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 35048200
Event: time 1627381396.807889, -------------- SYN_REPORT ------------
Event: time 1627381396.816893, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 35054400
Event: time 1627381396.816893, -------------- SYN_REPORT ------------
Event: time 1627381396.825891, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 35060700
Event: time 1627381396.825891, -------------- SYN_REPORT ------------
Event: time 1627381396.834905, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 35067000
Event: time 1627381396.834905, -------------- SYN_REPORT ------------
Event: time 1627381396.843914, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 35073300
Event: time 1627381396.843914, -------------- SYN_REPORT ------------
Event: time 1627381396.852890, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 35079600
Event: time 1627381396.852890, -------------- SYN_REPORT ------------
Event: time 1627381396.861899, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 35085900
Event: time 1627381396.861899, -------------- SYN_REPORT ------------
Event: time 1627381396.871900, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 35092200
Event: time 1627381396.871900, -------------- SYN_REPORT ------------
Event: time 1627381396.880903, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 35098500
Event: time 1627381396.880903, -------------- SYN_REPORT ------------
Event: time 1627381396.889894, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 35104800
Event: time 1627381396.889894, -------------- SYN_REPORT ------------
Event: time 1627381396.898894, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 35111100
Event: time 1627381396.898894, -------------- SYN_REPORT ------------
Event: time 1627381396.907897, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 35117400
Event: time 1627381396.907897, -------------- SYN_REPORT ------------
Event: time 1627381396.916905, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 35123700
Event: time 1627381396.916905, -------------- SYN_REPORT ------------
Event: time 1627381396.925887, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 35130000
Event: time 1627381396.925887, -------------- SYN_REPORT ------------
Event: time 1627381396.934912, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 35136300
Event: time 1627381396.934912, -------------- SYN_REPORT ------------
Event: time 1627381396.943900, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 35142500
Event: time 1627381396.943900, -------------- SYN_REPORT ------------
Event: time 1627381396.953893, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 35148800
Event: time 1627381396.953893, -------------- SYN_REPORT ------------
Event: time 1627381396.962898, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 35155100
Event: time 1627381396.962898, -------------- SYN_REPORT ------------
Event: time 1627381396.971896, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 35161400
Event: time 1627381396.971896, -------------- SYN_REPORT ------------
Event: time 1627381396.980906, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 35167700
Event: time 1627381396.980906, -------------- SYN_REPORT ------------
Event: time 1627381396.989911, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 35174000
Event: time 1627381396.989911, -------------- SYN_REPORT ------------
Event: time 1627381396.998905, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 35180300
Event: time 1627381396.998905, -------------- SYN_REPORT ------------
Event: time 1627381397.007899, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 35186600
Event: time 1627381397.007899, -------------- SYN_REPORT ------------
Event: time 1627381397.016905, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 35192900
Event: time 1627381397.016905, -------------- SYN_REPORT ------------
Event: time 1627381397.025898, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 35199200
Event: time 1627381397.025898, -------------- SYN_REPORT ------------
Event: time 1627381397.034915, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 35205500
Event: time 1627381397.034915, -------------- SYN_REPORT ------------
Event: time 1627381397.044908, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 35211800
Event: time 1627381397.044908, -------------- SYN_REPORT ------------
Event: time 1627381397.053890, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 35218100
Event: time 1627381397.053890, -------------- SYN_REPORT ------------
Event: time 1627381397.062903, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 35224400
Event: time 1627381397.062903, -------------- SYN_REPORT ------------
Event: time 1627381397.071902, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 35230700
Event: time 1627381397.071902, -------------- SYN_REPORT ------------
Event: time 1627381397.080904, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 35237000
Event: time 1627381397.080904, -------------- SYN_REPORT ------------
Event: time 1627381397.089901, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 35243200
Event: time 1627381397.089901, -------------- SYN_REPORT ------------
Event: time 1627381397.098905, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 35249500
Event: time 1627381397.098905, -------------- SYN_REPORT ------------
Event: time 1627381397.107902, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 35255800
Event: time 1627381397.107902, -------------- SYN_REPORT ------------
Event: time 1627381397.116900, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 35262100
Event: time 1627381397.116900, -------------- SYN_REPORT ------------
Event: time 1627381397.126884, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 35268400
Event: time 1627381397.126884, -------------- SYN_REPORT ------------
Event: time 1627381397.135916, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 35274700
Event: time 1627381397.135916, -------------- SYN_REPORT ------------
Event: time 1627381397.144906, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 35281000
Event: time 1627381397.144906, -------------- SYN_REPORT ------------
Event: time 1627381397.153898, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 35287300
Event: time 1627381397.153898, -------------- SYN_REPORT ------------
Event: time 1627381397.162902, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 35293500
Event: time 1627381397.162902, -------------- SYN_REPORT ------------
Regards
Jorge
[-- Attachment #1.2: Type: text/html, Size: 12402 bytes --]
[-- Attachment #2: Type: text/plain, Size: 170 bytes --]
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Multi-touch USB weird response
2021-07-29 12:57 Multi-touch USB weird response Jorge Fernandez Monteagudo
@ 2021-07-29 15:06 ` Valdis Klētnieks
0 siblings, 0 replies; 3+ messages in thread
From: Valdis Klētnieks @ 2021-07-29 15:06 UTC (permalink / raw)
To: Jorge Fernandez Monteagudo; +Cc: kernelnewbies
[-- Attachment #1.1: Type: text/plain, Size: 1105 bytes --]
On Thu, 29 Jul 2021 12:57:03 -0000, Jorge Fernandez Monteagudo said:
> Event: time 1627381396.770902, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 35023100
> Event: time 1627381396.770902, -------------- SYN_REPORT ------------
> Event: time 1627381396.780891, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 35029400
> Event: time 1627381396.780891, -------------- SYN_REPORT ------------
> Event: time 1627381396.789895, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 35035700
> Event: time 1627381396.789895, -------------- SYN_REPORT ------------
> Event: time 1627381396.798896, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 35041900
> Event: time 1627381396.798896, -------------- SYN_REPORT ------------
> Event: time 1627381396.807889, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 35048200
Looks like somebody's got a timer that pops every 0.01 seconds or so.
(looks closer to 0.0098 or so actually)
'git grep SYN_REPORT' tells me that these two files are a good place to start reading:
Documentation/input/multi-touch-protocol.rst
Documentation/input/event-codes.rst
[-- Attachment #1.2: Type: application/pgp-signature, Size: 494 bytes --]
[-- Attachment #2: Type: text/plain, Size: 170 bytes --]
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
^ permalink raw reply [flat|nested] 3+ messages in thread
* RE: Multi-touch USB weird response
@ 2021-07-30 7:43 Jorge Fernandez Monteagudo
0 siblings, 0 replies; 3+ messages in thread
From: Jorge Fernandez Monteagudo @ 2021-07-30 7:43 UTC (permalink / raw)
To: Valdis Klētnieks; +Cc: kernelnewbies
>> Event: time 1627381396.770902, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 35023100
>> Event: time 1627381396.770902, -------------- SYN_REPORT ------------
>> Event: time 1627381396.780891, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 35029400
>> Event: time 1627381396.780891, -------------- SYN_REPORT ------------
>> Event: time 1627381396.789895, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 35035700
>> Event: time 1627381396.789895, -------------- SYN_REPORT ------------
>> Event: time 1627381396.798896, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 35041900
>> Event: time 1627381396.798896, -------------- SYN_REPORT ------------
>> Event: time 1627381396.807889, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 35048200
>
>Looks like somebody's got a timer that pops every 0.01 seconds or so.
>(looks closer to 0.0098 or so actually)
>'git grep SYN_REPORT' tells me that these two files are a good place to start reading:
>
>Documentation/input/multi-touch-protocol.rst
>Documentation/input/event-codes.rst
Thanks for the info! Yes I would like to know who is sending these packages. I'm sniffing the USB and I suspect the device in this edge situation is sending the same touch event every 8ms. Maybe a firmware bug...
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2021-07-30 7:49 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-07-29 12:57 Multi-touch USB weird response Jorge Fernandez Monteagudo
2021-07-29 15:06 ` Valdis Klētnieks
2021-07-30 7:43 Jorge Fernandez Monteagudo
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).