On Wed, Jun 17, 2020 at 02:39:47PM -0700, Harry Cutts wrote: > Hi Kernel input people, > > On Chrome OS, we've observed a couple of graphics tablets getting > INPUT_PROP_DIRECT set despite them being traditional digitizers > without screens. The two tablets we've seen this for are the Huion > H610PRO (VID:PID 256c:006d) and the UGTABLET 10 inch PenTablet > (28bd:0905). Reverting "HID: input: Set INPUT_PROP_-property for > HID_UP_DIGITIZERS" (8473a93d1ba5385f63a128a285702ccc1d3ae2cc) fixes > the Huinon, at least. (We didn't get a chance to test it with the > UGTABLET.) Do we know if this is a shortcoming of that patch, are > those tablets just describing themselves incorrectly in their HID > descriptors? (in which case I guess we'd just have to add quirks for > them) fwiw, both huion and ugtablet are ones i know are regularly giving me troubles in libinput because what they say they do and what they do isn't in sync. HUION also re-uses usbids. 006d is a relatively new one I think, we have at least 7 different devices with 0256c:006e in libwacom and need to match on the name there, but with the Huion HS610 even that breaks - it uses the same vid/pid *and* name of other devices despite having different properties [1]. HS610, HS64 and your H610PRO all seem to use 000d, so... yay? I've CC'd Nikolai, he has much more kernel-level experience with these devices than I do. Cheers, Peter [1] https://github.com/linuxwacom/libwacom/pull/235
