RE: Multi-touch USB weird response

2021-07-30 Thread Jorge Fernandez Monteagudo 
>> 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

Re: Multi-touch USB weird response

2021-07-29 Thread Valdis Klētnieks 
On Thu, 29 Jul 2021 12:57:03 -, 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 


pgp922sF7l_Oq.pgp
Description: PGP signature
___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

Multi-touch USB weird response

2021-07-29 Thread Jorge Fernandez Monteagudo 
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
  Min0
  Max32767
  Resolution 106
Event code 1 (ABS_Y)
  Value  11404
  Min0
  Max32767
  Resolution 188
Event code 47 (ABS_MT_SLOT)
  Value  0
  Min0
  Max9
Event code 53 (ABS_MT_POSITION_X)
  Value  0
  Min0
  Max32767
  Resolution 106
Event code 54 (ABS_MT_POSITION_Y)
  Value  0
  Min0
  Max32767
  Resolution 188
Event code 57 (ABS_MT_TRACKING_ID)
  Value  0
  Min0
  Max65535
  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 
3500
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 
3513
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.9