diff options
author | Henrik Rydberg <[email protected]> | 2014-07-14 10:26:56 -0700 |
---|---|---|
committer | Dmitry Torokhov <[email protected]> | 2014-08-08 09:17:01 -0700 |
commit | e08d9afa9345f9a0e13cfff1d116b3a9b10d9dcb (patch) | |
tree | c8d00350261b69e444bf5ff17e1da247b045b19c /tools/perf/util/scripting-engines/trace-event-python.c | |
parent | ae84197f8a5e29d9b949fb515493d05bf7723f5c (diff) |
Input: synaptics - use firmware data for Cr-48
The profile sensor clickpad in a Cr-48 Chromebook does a reasonable job
of tracking individual fingers. This tracking isn't perfect, but,
experiments show that it works better than just passing "semi-mt" data
to userspace, and making userspace try to deduce where the fingers are
given a bounding box.
This patch tries to report correct two-finger positions instead of the
{(min_x, min_y), (max_x, max_y)} for profile sensor clickpads on Cr-48
chromebooks. Note that this device's firmware always reports the higher
(smaller y) finger in the "sgm" packet, and the lower (larger y) finger
in the "agm" packet. Thus, when a new finger arrives on the pad, the
kernel driver uses input core's contact tracking facilities to match
contacts with slots.
Inspired by patch by Daniel Kurtz <[email protected]> and Chung-yih
Wang <[email protected]>
Signed-off-by: Henrik Rydberg <[email protected]>
Reviewed-by: Benson Leung <[email protected]>
Signed-off-by: Dmitry Torokhov <[email protected]>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions