Bug 203049 - External USB touchpad (1357:1000) not recognized as touchpad
Summary: External USB touchpad (1357:1000) not recognized as touchpad
Status: NEW
Alias: None
Product: Drivers
Classification: Unclassified
Component: USB (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: Greg Kroah-Hartman
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-03-26 07:21 UTC by Tassilo Horn
Modified: 2019-03-26 08:30 UTC (History)
0 users

See Also:
Kernel Version: 5.0.4
Subsystem:
Regression: No
Bisected commit-id:


Attachments
"sudo hid-recorder /dev/hidraw{8,9,10}" and then touching and tapping on the touchpad (17.54 KB, text/plain)
2019-03-26 07:21 UTC, Tassilo Horn
Details
sudo usbhid-dump --model=1357:1000 (906 bytes, text/plain)
2019-03-26 07:22 UTC, Tassilo Horn
Details
udevadm info /dev/input/event{256,257,258,259} (4.60 KB, text/plain)
2019-03-26 07:22 UTC, Tassilo Horn
Details

Description Tassilo Horn 2019-03-26 07:21:17 UTC
Created attachment 282023 [details]
"sudo hid-recorder /dev/hidraw{8,9,10}" and then touching and tapping on the touchpad

I've got this touchpad:

https://www.amazon.com/Wireless-VOGEK-Rechargeable-Multi-Touch-Navigation/dp/B07NMTV9S8/

It's not recognized as a touchpad but as four /dev/input/event* devices, one being a mouse, one a keyboard and two being keys.  This means that I can basically use it but multi-touch gestures won't work.  Additionally, mouse and touchpad share the same (GNOME) settings although I'd rather use different settings for mouse & touchpad.

I've tested the device on a Windows 10 computer of a colleague, and there it worked fine out of the box without special driver (just USB HID) and supported multi-touch gestures like 3-finger swipes to switch between applications.

This is what dmesg has to say:

[ 6202.107555] usb 2-11: new full-speed USB device number 11 using xhci_hcd
[ 6202.250296] usb 2-11: New USB device found, idVendor=1357, idProduct=1000, bcdDevice= 1.00
[ 6202.250300] usb 2-11: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 6202.250303] usb 2-11: Product: Smart Control
[ 6202.250306] usb 2-11: Manufacturer: HL 0000 00 00 00 01
[ 6202.253563] input: HL 0000 00 00 00 01 Smart Control as /devices/pci0000:00/0000:00:14.0/usb2/2-11/2-11:1.0/0003:1357:1000.001C/input/input63
[ 6202.308083] hid-generic 0003:1357:1000.001C: input,hidraw8: USB HID v1.01 Keyboard [HL 0000 00 00 00 01 Smart Control] on usb-0000:00:14.0-11/input0
[ 6202.310380] input: HL 0000 00 00 00 01 Smart Control as /devices/pci0000:00/0000:00:14.0/usb2/2-11/2-11:1.1/0003:1357:1000.001D/input/input64
[ 6202.310646] hid-generic 0003:1357:1000.001D: input,hidraw9: USB HID v1.01 Mouse [HL 0000 00 00 00 01 Smart Control] on usb-0000:00:14.0-11/input1
[ 6202.312485] input: HL 0000 00 00 00 01 Smart Control Consumer Control as /devices/pci0000:00/0000:00:14.0/usb2/2-11/2-11:1.2/0003:1357:1000.001E/input/input65
[ 6202.367911] input: HL 0000 00 00 00 01 Smart Control System Control as /devices/pci0000:00/0000:00:14.0/usb2/2-11/2-11:1.2/0003:1357:1000.001E/input/input66
[ 6202.368279] hid-generic 0003:1357:1000.001E: input,hidraw10: USB HID v1.01 Device [HL 0000 00 00 00 01 Smart Control] on usb-0000:00:14.0-11/input2

I'll attach the output of "sudo hid-recorder /dev/hidraw{8,9,10}", "sudo usbhid-dump --model=1357:1000", and what udevadm has to say.
Comment 1 Tassilo Horn 2019-03-26 07:22:06 UTC
Created attachment 282025 [details]
sudo usbhid-dump --model=1357:1000
Comment 2 Tassilo Horn 2019-03-26 07:22:37 UTC
Created attachment 282027 [details]
udevadm info /dev/input/event{256,257,258,259}
Comment 3 Greg Kroah-Hartman 2019-03-26 07:42:49 UTC
On Tue, Mar 26, 2019 at 07:21:17AM +0000, bugzilla-daemon@bugzilla.kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=203049
> 
>             Bug ID: 203049
>            Summary: External USB touchpad (1357:1000) not recognized as
>                     touchpad
>            Product: Drivers
>            Version: 2.5
>     Kernel Version: 5.0.4


All USB bugs should be sent to the linux-usb@vger.kernel.org mailing
list, and not entered into bugzilla.  Please bring this issue up there,
if it is still a problem in the latest kernel release.

Note You need to log in before you can comment on or make changes to this bug.