2017-04-19 14:11:45 +10:00
|
|
|
/**
|
|
|
|
|
@page touchpad_pressure Touchpad pressure-based touch detection
|
|
|
|
|
|
|
|
|
|
libinput uses the touchpad pressure values to detect wether a finger has
|
|
|
|
|
been placed on the touchpad. This is @ref kernel_pressure_information and
|
|
|
|
|
combines with a libinput-specific hardware database to adjust the thresholds
|
|
|
|
|
on a per-device basis. libinput uses pressure thresholds primarily to filter
|
|
|
|
|
out accidental light touches but pressure information is also used for
|
|
|
|
|
some @ref palm_detection.
|
|
|
|
|
|
|
|
|
|
Pressure thresholds are **not** directly configurable by the user, rather it
|
|
|
|
|
is planned that libinput provides custom pressure thresholds for each device
|
|
|
|
|
where necessary. See @ref touchpad_pressure_hwdb for instructions for your
|
|
|
|
|
local device.
|
|
|
|
|
|
|
|
|
|
@section kernel_pressure_information Information provided by the kernel
|
|
|
|
|
|
|
|
|
|
The kernel sends multiple values to inform userspace about a finger touching
|
|
|
|
|
the touchpad. The most basic is the ```EV_KEY/BTN_TOUCH``` boolean event
|
|
|
|
|
that simply announces physical contact with the touchpad. The decision when
|
|
|
|
|
this event is sent is usually made by the kernel driver and may depend on
|
|
|
|
|
device-specific thresholds. These thresholds are transparent to userspace
|
|
|
|
|
and cannot be modified.
|
|
|
|
|
|
|
|
|
|
Many contemporary touchpad devices provide an absolute pressure axis in
|
|
|
|
|
addition to ```BTN_TOUCH```. This pressure generally increases as the pressure
|
|
|
|
|
increases, however few touchpads are capable of detection pressure. The
|
|
|
|
|
pressure value is usually related to the covered area - as the pressure
|
|
|
|
|
increases a finger flattens and thus covers a larger area. The range
|
|
|
|
|
provided by the kernel is not mapped to a specific physical range and
|
|
|
|
|
often requires adjustment. Pressure is sent by the ```ABS_PRESSURE``` axis
|
|
|
|
|
for single-touch touchpads or ```ABS_MT_PRESSURE``` on multi-touch capable
|
|
|
|
|
touchpads.
|
|
|
|
|
|
|
|
|
|
Some devices provide additional touch size information through
|
|
|
|
|
the ```ABS_MT_TOUCH_MAJOR/ABS_MT_TOUCH_MINOR``` axes and/or
|
|
|
|
|
the ```ABS_MT_WIDTH_MAJOR/ABS_MT_WIDTH_MINOR``` axes. While the kernel
|
|
|
|
|
documentation specifies how these axes are supposed to be mapped, few
|
|
|
|
|
devices forward
|
|
|
|
|
reliable information.
|
|
|
|
|
|
|
|
|
|
@section touchpad_pressure_hwdb Debugging touchpad pressure ranges
|
|
|
|
|
|
|
|
|
|
This section describes how to determine the touchpad pressure ranges
|
|
|
|
|
required for a touchpad device and how to add the required hwdb entry
|
|
|
|
|
locally. Note that the hwdb entry is **not public API** and **may change at
|
|
|
|
|
any time**. Users are advised to @ref reporting_bugs "report a bug" with the
|
|
|
|
|
updated pressure ranges when testing has completed.
|
|
|
|
|
|
2017-06-27 14:16:57 +10:00
|
|
|
Use the ```libinput measure touchpad-pressure``` tool provided by libinput.
|
|
|
|
|
This tool will search for your touchpad device and print some pressure
|
|
|
|
|
statistics, including whether a touch is/was considered logically down.
|
|
|
|
|
Example output of the tool is below:
|
2017-04-19 14:11:45 +10:00
|
|
|
|
|
|
|
|
<pre>
|
2017-06-27 14:16:57 +10:00
|
|
|
$ sudo libinput measure touchpad-pressure
|
|
|
|
|
Ready for recording data.
|
|
|
|
|
Pressure range used: 8:10
|
|
|
|
|
Palm pressure range used: 65535
|
|
|
|
|
Place a single finger on the touchpad to measure pressure values.
|
|
|
|
|
Ctrl+C to exit
|
|
|
|
|
|
|
|
|
|
Sequence 1190 pressure: min: 39 max: 48 avg: 43 median: 44 tags: down
|
|
|
|
|
Sequence 1191 pressure: min: 49 max: 65 avg: 62 median: 64 tags: down
|
|
|
|
|
Sequence 1192 pressure: min: 40 max: 78 avg: 64 median: 66 tags: down
|
|
|
|
|
Sequence 1193 pressure: min: 36 max: 83 avg: 70 median: 73 tags: down
|
|
|
|
|
Sequence 1194 pressure: min: 43 max: 76 avg: 72 median: 74 tags: down
|
|
|
|
|
Touchpad pressure: 47 min: 47 max: 86 tags: down
|
2017-04-19 14:11:45 +10:00
|
|
|
</pre>
|
|
|
|
|
|
2017-06-27 14:16:57 +10:00
|
|
|
The example output shows five completed touch sequences and one ongoing one.
|
|
|
|
|
For each, the respective minimum and maximum pressure values are printed as
|
|
|
|
|
well as some statistics. The ```tags``` show that sequence was considered
|
|
|
|
|
logically down at some point. This is an interactive tool and its output may
|
|
|
|
|
change frequently. Refer to the <i>libinput-measure-touchpad-pressure(1)</i> man
|
|
|
|
|
page for more details.
|
|
|
|
|
|
|
|
|
|
By default, this tool uses the udev hwdb entries for the pressure range. To
|
|
|
|
|
narrow down on the best values for your device, specify the 'logically down'
|
|
|
|
|
and 'logically up' pressure thresholds with the ```--touch-thresholds``
|
|
|
|
|
argument:
|
2017-04-19 14:11:45 +10:00
|
|
|
<pre>
|
2017-06-27 14:16:57 +10:00
|
|
|
$ sudo libinput measure touchpad-pressure --touch-thresholds=10:8
|
2017-04-19 14:11:45 +10:00
|
|
|
</pre>
|
|
|
|
|
|
2017-06-27 14:16:57 +10:00
|
|
|
Interact with the touchpad and check if the output of this tool matches your
|
|
|
|
|
expectations.
|
2017-04-19 14:11:45 +10:00
|
|
|
|
|
|
|
|
Once the thresholds are decided on (e.g. 10 and 8), they can be enabled with
|
|
|
|
|
the following hwdb file:
|
|
|
|
|
|
|
|
|
|
<pre>
|
|
|
|
|
$> cat /etc/udev/hwdb.d/99-touchpad-pressure.hwdb
|
|
|
|
|
libinput:name:*SynPS/2 Synaptics TouchPad:dmi:*svnHewlett-Packard:*pnHPCompaq6910p*
|
|
|
|
|
LIBINPUT_ATTR_PRESSURE_RANGE=10:8
|
|
|
|
|
</pre>
|
|
|
|
|
|
|
|
|
|
The first line is the match line and should be adjusted for the device name
|
|
|
|
|
(see evemu-record's output) and for the local system, based on the
|
|
|
|
|
information in ```/sys/class/dmi/id/modalias```. The modalias should be
|
|
|
|
|
shortened to the specific system's information, usually system vendor (svn)
|
|
|
|
|
and product name (pn).
|
|
|
|
|
|
|
|
|
|
Once in place, you need to run the following to commands, adjusted for your
|
|
|
|
|
device's event node (see @ref faq_hwdb_changes):
|
|
|
|
|
<pre>
|
|
|
|
|
sudo udevadm hwdb --update
|
|
|
|
|
sudo udevadm test /sys/class/input/eventX
|
|
|
|
|
</pre>
|
|
|
|
|
|
|
|
|
|
If the pressure range property shows up correctly, restart X or the
|
|
|
|
|
Wayland compositor and libinput should now use the correct pressure
|
2017-05-24 11:12:28 +10:00
|
|
|
thresholds. The @ref tools can be used to verify the correct
|
2017-04-19 14:11:45 +10:00
|
|
|
functionality first without the need for a restart.
|
|
|
|
|
|
|
|
|
|
Once the pressure ranges are deemed correct,
|
|
|
|
|
@ref reporting_bugs "report a bug" to get the pressure ranges into the
|
|
|
|
|
repository.
|
|
|
|
|
|
|
|
|
|
*/
|