Linux系统下Libinput驱动的应用（主要在触摸屏校准）

在浸泡在旧的解决问题方法的过去，突然来了个新的情况（LUbuntu17.10下实现触摸屏的校准），这让我想到

“一个幽灵在欧洲的上空徘徊，XXXX的一声枪响”

惊醒了某些沉睡的领导，老办法不行了，要学习研究新办法了。

于是任务来了。

         经查文档之后发现，  Ubuntu17.10以及Fedora 22等Linux系统都使用了整合evdev驱动之后的libinput驱动，之前的触摸校准的方式原理还是一样，配置方式还是一样，libinput需要的校准参数（A，B，C，D，E，F）不一样了，而evdev的校准参数（Xmin,Xmax,Ymin,Ymax）；

找不到写的了，先贴下来：

链接：https://wayland.freedesktop.org/libinput/doc/latest/absolute_axes.html

• Touchscreens

Absolute axes

Devices with absolute axes are those that send positioning data for an axis in a device-specific coordinate range, defined by a minimum and a maximum value.

Compare this to relative devices (e.g. a mouse) that can only detect directional data, not positional data.

libinput supports three types of devices with absolute axes:

• multi-touch screens
• single-touch screens
• graphics tablets

Touchpads are technically absolute devices but libinput converts the axis values to directional motion and posts events as relative events. Touchpads do not count as absolute devices in libinput.

For all absolute devices in libinput, the default unit for x/y coordinates is in mm off the top left corner on the device, or more specifically off the device's sensor. If the device is physically rotated from its natural position and this rotation was communicated to libinput (e.g. by setting the device left-handed), the coordinate origin is the top left corner of in the current rotation.

Handling of absolute coordinates

In most use-cases, absolute input devices are mapped to a single screen. For direct input devices such as touchscreens the aspect ratio of the screen and the device match. Mapping the input device position to the output position is thus a simple mapping between two coordinates. libinput provides the API for this with

• libinput_event_pointer_get_absolute_x_transformed() for pointer events
• libinput_event_touch_get_x_transformed() for touch events

libinput's API only provides the call to map into a single coordinate range. If the coordinate range has an offset, the compositor is responsible for applying that offset after the mapping. For example, if the device is mapped to the right of two outputs, add the output offset to the transformed coordinate.

Devices without x/y resolution

An absolute device that does not provide a valid resolution is considered buggy and must be fixed in the kernel. Some touchpad devices do not provide resolution, those devices are correctly handled within libinput (touchpads are not absolute devices, as mentioned above).

Calibration of absolute devices

Absolute devices may require calibration to map precisely into the output range required. This is done by setting a transformation matrix, see libinput_device_config_calibration_set_matrix() which is applied to each input coordinate.

⎛⎝⎜cosθsinθ0−sinθcosθ0