diff options
author | Jason Gerecke <killertofu@gmail.com> | 2022-12-01 15:11:41 -0800 |
---|---|---|
committer | Jiri Kosina <jkosina@suse.cz> | 2022-12-20 15:29:10 +0100 |
commit | 1db1f392591aff13fd643f0ec7c1d5e27391d700 (patch) | |
tree | 0a3a34eb2a7e4ee194a77b2e98ad3a6aa9b59ed9 /include/linux/swap.h | |
parent | 53ffa6a9f83b2170c60591da1ead8791d5a42e81 (diff) | |
download | linux-stable-1db1f392591aff13fd643f0ec7c1d5e27391d700.tar.gz linux-stable-1db1f392591aff13fd643f0ec7c1d5e27391d700.tar.bz2 linux-stable-1db1f392591aff13fd643f0ec7c1d5e27391d700.zip |
HID: wacom: Ensure bootloader PID is usable in hidraw mode
Some Wacom devices have a special "bootloader" mode that is used for
firmware flashing. When operating in this mode, the device cannot be
used for input, and the HID descriptor is not able to be processed by
the driver. The driver generates an "Unknown device_type" warning and
then returns an error code from wacom_probe(). This is a problem because
userspace still needs to be able to interact with the device via hidraw
to perform the firmware flash.
This commit adds a non-generic device definition for 056a:0094 which
is used when devices are in "bootloader" mode. It marks the devices
with a special BOOTLOADER type that is recognized by wacom_probe() and
wacom_raw_event(). When we see this type we ensure a hidraw device is
created and otherwise keep our hands off so that userspace is in full
control.
Signed-off-by: Jason Gerecke <jason.gerecke@wacom.com>
Tested-by: Tatsunosuke Tobita <tatsunosuke.tobita@wacom.com>
Cc: <stable@vger.kernel.org>
Signed-off-by: Jiri Kosina <jkosina@suse.cz>
Diffstat (limited to 'include/linux/swap.h')
0 files changed, 0 insertions, 0 deletions