>> 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@xxxxxxxxxxxxxxxxx https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
