1. 18 Apr, 2017 1 commit
  2. 22 Jan, 2017 1 commit
  3. 07 Oct, 2016 1 commit
  4. 04 Oct, 2016 2 commits
  5. 03 Aug, 2016 1 commit
  6. 23 Jun, 2016 1 commit
  7. 19 Jun, 2016 1 commit
  8. 12 Jan, 2016 1 commit
    • Benjamin Tissoires's avatar
      Input: elantech - mark protocols v2 and v3 as semi-mt · 6544a1df
      Benjamin Tissoires authored
      When using a protocol v2 or v3 hardware, elantech uses the function
      elantech_report_semi_mt_data() to report data. This devices are rather
      creepy because if num_finger is 3, (x2,y2) is (0,0). Yes, only one valid
      touch is reported.
      
      Anyway, userspace (libinput) is now confused by these (0,0) touches,
      and detect them as palm, and rejects them.
      
      Commit 3c0213d1
      
       ("Input: elantech - fix semi-mt protocol for v3 HW")
      was sufficient enough for xf86-input-synaptics and libinput before it has
      palm rejection. Now we need to actually tell libinput that this device is
      a semi-mt one and it should not rely on the actual values of the 2 touches.
      
      Cc: stable@vger.kernel.org
      Signed-off-by: default avatarBenjamin Tissoires <benjamin.tissoires@redhat.com>
      Signed-off-by: default avatarDmitry Torokhov <dmitry.torokhov@gmail.com>
      6544a1df
  9. 06 Nov, 2015 1 commit
  10. 07 Aug, 2015 1 commit
  11. 16 Jul, 2015 1 commit
  12. 05 Jun, 2015 1 commit
  13. 02 Jun, 2015 1 commit
  14. 13 May, 2015 1 commit
  15. 06 Apr, 2015 1 commit
  16. 01 Feb, 2015 1 commit
  17. 08 Jan, 2015 1 commit
  18. 25 Nov, 2014 1 commit
  19. 14 Nov, 2014 2 commits
  20. 08 Nov, 2014 2 commits
  21. 08 Sep, 2014 3 commits
  22. 26 Aug, 2014 2 commits
  23. 08 Jun, 2014 2 commits
  24. 05 May, 2014 1 commit
  25. 23 Apr, 2014 1 commit
  26. 18 Dec, 2013 1 commit
  27. 05 Dec, 2013 1 commit
  28. 25 Aug, 2013 1 commit
  29. 07 Jul, 2013 1 commit
    • Matteo Delfino's avatar
      Input: elantech - fix for newer hardware versions (v7) · 9eebed7d
      Matteo Delfino authored
      
      
      * Fix version recognition in elantech_set_properties
      
        The new hardware reports itself as v7 but the packets'
        structure is unaltered.
      
      * Fix packet type recognition in elantech_packet_check_v4
      
        The bitmask used for v6 is too wide, only the last three bits of
        the third byte in a packet (packet[3] & 0x03) are actually used to
        distinguish between packet types.
        Starting from v7, additional information (to be interpreted) is
        stored in the remaining bits (packets[3] & 0x1c).
        In addition, the value stored in (packet[0] & 0x0c) is no longer
        a constant but contains additional information yet to be deciphered.
        This change should be backwards compatible with v6 hardware.
      
      Additional-author: Giovanni Frigione <gio.frigione@gmail.com>
      Signed-off-by: default avatarMatteo Delfino <kendatsuba@gmail.com>
      Signed-off-by: default avatarDmitry Torokhov <dmitry.torokhov@gmail.com>
      9eebed7d
  30. 19 Sep, 2012 1 commit
  31. 10 Apr, 2012 2 commits
  32. 21 Nov, 2011 1 commit