Tablet PC pen and touch input is disabled after booting into Windows #15
Assignees
Labels
bug
Confirmed / reproduced bugs
Comments
|
Closing to match upstream bug status. |
0lvin
pushed a commit
to free-z4u/roc-rk3328-cc-official
that referenced
this issue
Dec 25, 2018
…nd G11 A tablet PC booted into Windows may have its pen/touch hardware switched into "Wacom mode" similar to what we do with explicitly-supported hardware. Some devices appear to maintain this state across reboots, preventing their use with the generic HID driver. This patch adds support for detecting the presence of the mode switch feature report used by devices based on the G9 and G11 chips and has the HID codepath always attempt to reset the device back to sending standard HID reports. Fixes: https://sourceforge.net/p/linuxwacom/bugs/307/ Fixes: https://sourceforge.net/p/linuxwacom/bugs/310/ Fixes: linuxwacom/input-wacom#15 Co-authored-by: Benjamin Tissoires <benjamin.tissoires@redhat.com> Signed-off-by: Jason Gerecke <jason.gerecke@wacom.com> Reviewed-by: Benjamin Tissoires <benjamin.tissoires@redhat.com> Signed-off-by: Jiri Kosina <jkosina@suse.cz>
ghost
pushed a commit
to crevanthsv/kernel_xiaomi_sakura
that referenced
this issue
May 15, 2021
…nd G11 A tablet PC booted into Windows may have its pen/touch hardware switched into "Wacom mode" similar to what we do with explicitly-supported hardware. Some devices appear to maintain this state across reboots, preventing their use with the generic HID driver. This patch adds support for detecting the presence of the mode switch feature report used by devices based on the G9 and G11 chips and has the HID codepath always attempt to reset the device back to sending standard HID reports. Fixes: https://sourceforge.net/p/linuxwacom/bugs/307/ Fixes: https://sourceforge.net/p/linuxwacom/bugs/310/ Fixes: linuxwacom/input-wacom#15 Co-authored-by: Benjamin Tissoires <benjamin.tissoires@redhat.com> Signed-off-by: Jason Gerecke <jason.gerecke@wacom.com> Reviewed-by: Benjamin Tissoires <benjamin.tissoires@redhat.com> Signed-off-by: Jiri Kosina <jkosina@suse.cz>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Based on Sourceforge Bug #307 and Sourceforge Bug #310
Based on the hid-recorder output from the Lenovo Thinkpad Yoga 260 (056a:5048) and the Lenovo Thinkpad X1 Yoga (056a:503e), it looks like the device is sending events with an unexpected report ID. Instead of having the ID specified for the generic HID packets, the ID is of the "vendor defined" HID packets that the driver can't automatically decode. That's really odd since since most devices use the former automatically.
This can apparently be worked around by using the device's reset switch, but the pen and touch stops working again once the system is booted into Windows. This likely indicates the sensor is persisting the mode change that is done by the Wacom driver for Windows. To fix this bug, we need to manually change the mode so it sends standard HID reports again.
The text was updated successfully, but these errors were encountered: