diff options
| author |   Ben Chan <benchan@chromium.org> | 2018-05-29 15:56:55 -0700 |
|---|---|---|
| committer |   Jiri Kosina <jkosina@suse.cz> | 2018-05-30 08:53:09 +0200 |
| commit | abb36fe691b28f2a64926b61448d6b9610ed879a (patch) | |
| tree | ed1c00fc939fc3b1ac6e4a97a5b3fc7a716c5bfc /include/linux/hid.h | |
| parent | HID: multitouch: fix types returned from mt_need_to_apply_feature() (diff) | |
| download | linux-dev-abb36fe691b28f2a64926b61448d6b9610ed879a.tar.xz linux-dev-abb36fe691b28f2a64926b61448d6b9610ed879a.zip | |
HID: multitouch: fix calculation of last slot field in multi-touch reports
According to [1] and also seemingly agreed by [2], the Scan Time usage
(0x0D 0x56) is a report level usage, not a contact level usage.
However, the hid-multitouch driver currently includes HID_DG_SCANTIME
when calculating `td->last_slot_field', which may lead to
mt_complete_slot() being prematurely called in certain cases (e.g. when
each touch input report includes more than one contact and the Scan Time
usage appears before any contact logical collection).
This patch fixes the issue by skipping mt_store_field() on
HID_DG_SCANTIME, similar to how HID_DG_CONTACTCOUNT and
HID_DG_CONTACTMAX are handled.
[1] https://docs.microsoft.com/en-us/windows-hardware/design/component-guidelines/windows-precision-touchpad-required-hid-top-level-collections#windows-precision-touchpad-input-reports
[2] https://patchwork.kernel.org/patch/1742181/
Fixes: 29cc309d8bf19 ("HID: hid-multitouch: forward MSC_TIMESTAMP")
Signed-off-by: Ben Chan <benchan@chromium.org>
Reviewed-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Signed-off-by: Jiri Kosina <jkosina@suse.cz>
Diffstat (limited to 'include/linux/hid.h')
0 files changed, 0 insertions, 0 deletions