1. 13 May, 2020 1 commit
    • Peter Hutterer's avatar
      evdev: warn if our event processing lags by 10ms or more · bd7b9106
      Peter Hutterer authored
      Take a snapshot of the time every 10 libinput_dispatch() calls. During event
      processing, check if the event timestamp is more than 10ms in the past and
      warn if it is. This should provide a warning to users when the compositor is
      too slow to processes events but events aren't coming in fast enough to
      trigger SYN_DROPPED.
      
      Because we check the device event time against the dispatch time we may get
      warnings for multiple devices on delayed processing. This is intended, it's
      good to know which devices were affected.
      
      In the test suite we need to ignore the warning though, since we compose the
      events in very specific ways it's common to exceed that threshold
      (particularly when calling litest_touch_move_to).
      Signed-off-by: Peter Hutterer's avatarPeter Hutterer <peter.hutterer@who-t.net>
      bd7b9106
  2. 12 Feb, 2020 1 commit
    • Peter Hutterer's avatar
      test: add a test case for checking EVDEV_ABS overrides · 0dcb02d3
      Peter Hutterer authored
      Problem: it's still not a 100% check because the way real udev handles the
      EVDEV_ABS overrides ignores any that are set through udev properties only. So
      we manually have to trigger the keyboard builtin for our test device which
      can give us false positives (e.g. it wouldn't have detected #424). But still,
      it'll alert us if the actual overridden values are different to what we
      expect.
      Signed-off-by: Peter Hutterer's avatarPeter Hutterer <peter.hutterer@who-t.net>
      0dcb02d3
  3. 31 Jan, 2020 1 commit
  4. 14 Mar, 2019 2 commits
  5. 03 Feb, 2019 1 commit
  6. 05 Nov, 2018 1 commit
  7. 29 Oct, 2018 1 commit
    • Peter Hutterer's avatar
      quirks: add the ability to disable custom event codes/types · 981f3a47
      Peter Hutterer authored
      This is a more flexible approach than adding a model flag and the C code to
      just call libevdev_disable_event_code(). There's a risk users will think this
      is is a configuration API but there are some devices out there (e.g. the
      Microsoft Sculpt mouse) that need a more generic solution.
      
      Case in point: the Sculpt mouse insists on holding BTN_SIDE down at all times.
      We cannot ship any quirks for that device because we only have the receiver's
      generic VID/PID. So a local override is required, but we might as well make
      that one generic enough to catch other devices too in the future.
      Signed-off-by: Peter Hutterer's avatarPeter Hutterer <peter.hutterer@who-t.net>
      981f3a47
  8. 21 Oct, 2018 1 commit
  9. 14 Sep, 2018 1 commit
  10. 13 Aug, 2018 2 commits
  11. 02 Aug, 2018 1 commit
  12. 19 Jul, 2018 1 commit
    • myfreeweb's avatar
      Add versionsort test · db2dd43c
      myfreeweb authored
      And make local versionsort testable even when the native one is present.
      db2dd43c
  13. 05 Jul, 2018 1 commit
  14. 26 Jun, 2018 1 commit
  15. 11 Jun, 2018 1 commit
  16. 08 Jun, 2018 2 commits
  17. 03 May, 2018 2 commits
  18. 30 Apr, 2018 1 commit
  19. 26 Apr, 2018 1 commit
  20. 23 Mar, 2018 1 commit
  21. 30 Nov, 2017 1 commit
  22. 20 Nov, 2017 1 commit
  23. 19 Nov, 2017 1 commit
  24. 21 Sep, 2017 1 commit
  25. 06 Sep, 2017 1 commit
  26. 04 Sep, 2017 1 commit
  27. 11 Jul, 2017 1 commit
  28. 10 Jul, 2017 1 commit
  29. 03 Jul, 2017 1 commit
    • Peter Hutterer's avatar
      touchpad: add pressure-base palm detection · 25d54b90
      Peter Hutterer authored
      If a touch goes past the fixed pressure threshold it is labelled as a palm and
      stays a palm. Default value is one that works well here on a T440 and is
      virtually impossible to trigger by a normal finger or thumb. A udev property
      is exposed so we can handle this in the udev hwdb and the new tool introduce a
      few commits ago can help finding the palm detection threshold.
      
      Unlike the other palm detection features, once a palm goes past the threshold
      it remains a palm until the touch is released. This means palm overrides any
      other palm detection features. For code simplicity, we don't combine the
      states but merely check for pressure before and after the other palm detection
      functions. If the pressure triggers, it will trigger before anything else. And
      if something else is already active (e.g. edge where the pressure doesn't work
      well) it will trigger as soon as the palm is released.
      
      The palm threshold should thus be chosen with some room to spare between the
      highest finger pressure.
      
      https://bugs.freedesktop.org/show_bug.cgi?id=94236Signed-off-by: Peter Hutterer's avatarPeter Hutterer <peter.hutterer@who-t.net>
      25d54b90
  30. 02 Jun, 2017 1 commit
  31. 26 Apr, 2017 1 commit
  32. 09 Feb, 2017 1 commit
  33. 26 Jan, 2017 2 commits
  34. 20 Jan, 2017 1 commit
  35. 15 Jan, 2017 1 commit