[PATCH v2 libinput 5/6] touchpad: add touch-size-based palm detection

Signed-off-by: Peter Hutterer --- src/evdev-mt-touchpad.c| 66 -- src/evdev-mt-touchpad.h| 4 +++ src/libinput-util.c| 25 +++ src/libinput-util.h| 1 +

[PATCH v2 libinput 2/6] test: loosen up litest to allow major/minor handling

The max values on ABS_MT_TOUCH_MAJOR/MINOR aren't hard limits, they basically represent the size of a finger with (afaict) a suggestion that anything greater than the max may be a palm. Disable the 0-100% range checks for those axes so we can send custom events. Signed-off-by: Peter Hutterer

[PATCH v2 libinput 3/6] util: rename the pressure range parser to a more generic range_parser

Signed-off-by: Peter Hutterer --- src/evdev-mt-touchpad.c | 2 +- src/libinput-util.c | 2 +- src/libinput-util.h | 2 +- test/test-misc.c| 12 ++-- 4 files changed, 9 insertions(+), 9 deletions(-) diff --git a/src/evdev-mt-touchpad.c

[PATCH v2 libinput 1/6] test: force-release major/minor on the default touch up

Signed-off-by: Peter Hutterer --- test/litest.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/test/litest.c b/test/litest.c index abd72188..1863934b 100644 --- a/test/litest.c +++ b/test/litest.c @@ -1653,6 +1653,8 @@ touch_up(struct litest_device *d, unsigned

[PATCH v2 libinput 4/6] touchpad: add touch-size based touch handling

Apple touchpads don't use ABS_MT_PRESSURE but they are multitouch touchpads, so the current pressure-based handling code doesn't apply because it expects slot-based pressure for mt touchpads. Apple does however send useful data for ABS_MT_WIDTH_MAJOR/MINOR, so let's use that instead. The data

[PATCH v3 libinput 0/6] Add touch-size based touch and palm handling for Apple touchpads

For reference, v1 was https://lists.freedesktop.org/archives/wayland-devel/2017-March/033593.html v1 was more complicated than this set: * it tried to use physical measurements for touch sizes * it tried to use those measurements combined with the resolution to estimate touch size even when

[PATCH libinput] touchpad: set keyboard to non-active when the keyboard is removed

If the keyboard is removed while dwt thinks it is in active state, that state is never reset and subsequent touches are ignored. https://bugs.freedesktop.org/show_bug.cgi?id=101743 Signed-off-by: Peter Hutterer --- src/evdev-mt-touchpad.c | 1 + test/test-touchpad.c

Re: [PATCH RFC libinput] filter: force touchpads to a fixed report rate

Hi, On 10-07-17 07:11, Peter Hutterer wrote: From: Hans de Goede Some devices, specifically some bluetooth touchpads generate quite unreliable timestamps for their events. The problem seems to be that (some of) these touchpads sample at aprox 90 Hz, but the bluetooth

[PATCH wayland] connection: Print the content of arrays in closures

The current behaviour when WAYLAND_DEBUG is set is to print “array”, which is quite unhelpful. This patch prints a list of the bytes present in the array. It doesn’t try to interpret it as uint32_t or anything, leaving that to the reader because this information isn’t present in the protocol