summaryrefslogtreecommitdiffstats
path: root/ipc
diff options
context:
space:
mode:
authorJason Gerecke <killertofu@gmail.com>2017-01-25 12:08:37 -0800
committerJiri Kosina <jkosina@suse.cz>2017-01-26 21:46:44 +0100
commit4922cd26f03c1c71bf7dd6cbdb638e7e36a4a50b (patch)
tree3a0bc15207ded7bc67070ff66114d97f20db4512 /ipc
parent5ba13c6495010cd39e0ecb89ce1e546189bd6006 (diff)
downloadlinux-stable-4922cd26f03c1c71bf7dd6cbdb638e7e36a4a50b.tar.gz
linux-stable-4922cd26f03c1c71bf7dd6cbdb638e7e36a4a50b.tar.bz2
linux-stable-4922cd26f03c1c71bf7dd6cbdb638e7e36a4a50b.zip
HID: wacom: Support 2nd-gen Intuos Pro's Bluetooth classic interface
In addition to its USB interface, the second-generation Intuos Pro includes a Bluetooth radio that offers two pairing interfaces: classic and low-energy. The classic interface functions just like the earlier Bluetooth-enabled Intuos4 and Graphire4 tablets, appearing as a HID device that our driver can work with. The low-energy interface is intented to be used by userspace applications that make use of its paper-to-digital capabilities. Despite the USB interface using Wacom's new vendor-defined HID usages, the Bluetooth interface provides us with useless black-box "blob" report descriptors like past devices. We thus have to explicitly add support for the PIDs and reports used. These devices pack a /lot/ of information into a single Bluetooth input report. Each report contains up to seven snapshots of the pen state, four snapshots of the touch state (of five touches each), pad state, and battery data. Thankfully this isn't too hard for the driver to report -- it just takes a fair amount of code to extract! Signed-off-by: Jason Gerecke <jason.gerecke@wacom.com> Reviewed-by: Ping Cheng <pingc@wacom.com> Signed-off-by: Jiri Kosina <jkosina@suse.cz>
Diffstat (limited to 'ipc')
0 files changed, 0 insertions, 0 deletions