summaryrefslogtreecommitdiffstats
path: root/drivers/media/dvb-frontends/atbm8830_priv.h
diff options
context:
space:
mode:
authorJason Gerecke <killertofu@gmail.com>2017-04-19 23:47:24 +0200
committerJiri Kosina <jkosina@suse.cz>2017-04-20 11:33:45 +0200
commit6f107fab8f18228936cd3df88a3bb6050865c2c8 (patch)
treea8ca8bf1ea48be8d4c3c70b97e39016aa336b99b /drivers/media/dvb-frontends/atbm8830_priv.h
parentHID: wacom: Treat HID_DG_TOOLSERIALNUMBER as unsigned (diff)
downloadlinux-6f107fab8f18228936cd3df88a3bb6050865c2c8.tar.xz
linux-6f107fab8f18228936cd3df88a3bb6050865c2c8.zip
HID: wacom: Override incorrect logical maximum contact identifier
It apears that devices designed around Wacom's G11 chipset (e.g. Lenovo ThinkPad Yoga 260, Lenovo ThinkPad X1 Yoga, Dell XPS 12 9250, Dell Venue 8 Pro 5855, etc.) suffer from a common issue in their HID descriptors. The logical maximum is not updated for the "Contact Identifier" usage, leaving it as just "1" despite these devices being capable of tracking far more touches. Commit 60a221869803 began ignoring usages with out-of-range values, causing problems for devices based on this chipset. Touches after the first will have an out-of-range Contact Identifier, and ignoring that usage will cause the kernel to incorrectly slot each finger's events (along with all the knock-on userspace effects that entails). This commit checks for these buggy descriptors and updates the maximum where required. Prior chipsets have used "255" as the maximum (and the G11, at least, doesn't seem to actually use IDs outside the range of 1..CONTACTMAX) so continue using this value. Cc: stable@vger.kernel.org Fixes: 60a221869803 ("HID: wacom: generic: add support for touchring") Signed-off-by: Jason Gerecke <jason.gerecke@wacom.com> Signed-off-by: Jiri Kosina <jkosina@suse.cz>
Diffstat (limited to 'drivers/media/dvb-frontends/atbm8830_priv.h')
0 files changed, 0 insertions, 0 deletions