summaryrefslogtreecommitdiffstats
path: root/rust/compiler_builtins.rs
diff options
context:
space:
mode:
authorJason Gerecke <killertofu@gmail.com>2022-12-02 00:11:41 +0100
committerJiri Kosina <jkosina@suse.cz>2022-12-20 15:29:10 +0100
commit1db1f392591aff13fd643f0ec7c1d5e27391d700 (patch)
tree0a3a34eb2a7e4ee194a77b2e98ad3a6aa9b59ed9 /rust/compiler_builtins.rs
parentHID: amd_sfh: Add missing check for dma_alloc_coherent (diff)
downloadlinux-1db1f392591aff13fd643f0ec7c1d5e27391d700.tar.xz
linux-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 'rust/compiler_builtins.rs')
0 files changed, 0 insertions, 0 deletions