On Thursday 08 January 2015 15:58:54 Andrew Duggan wrote:
On 12/24/2014 03:53 PM, Gabriele Mazzotta wrote:According to the RMI4 specification, gesture interrupts are cleared
[...snip...]
Yes, 0x50 does appear to be the address of the palm detect interruptHi,Thanks, I will see if I can get any additional information on this.Also, if you can get the firmware id from your touchpad that would alsofirmware id: 1522295
be useful.
$ sudo ./rmihidtool -f /dev/hidraw0
Andrew
I think I found the source of the problem.
$ ./rmihidtool /dev/hidraw1 -r 0x50 1
0x01 #PalmDetect Interrupt Enable, right?
enable register.
$ ./rmihidtool /dev/hidraw1 -w 0x50 0 #Disable PalmDetect InterruptThat is weird behavior and I haven't seen anything like that before. I
It makes more sense now that widths greater than 12 trigger the bug.
will file a bug to see if firmware has any idea why this is happening.
only once specific flag registers, F11_2D_Data8 and F11_2D_Data9, are
read. So I tried to read those register and found that the following
command stops the events:
$ rmihidtool /dev/hidraw1 -r 0x24 1 # I was looking for F11_2D_Data8
I'm not sure I got the right address as reading any register close to
0x24 (such as 0x25, 0x26) has the same effect. I would have expected
this to happen only reading one specific register.
I also honestly don't know why palms are detected when the width is at
least 12, PalmDetectThreshold is 0 and so the palm detection should
be inhibited.
Thanks for provide all of this detail.GabrieleAndrew