Initial data: There are two android tv consoles, both on android 6 and the Asus touchscreen monitor, which tach works through the usbhid kernel module. Same architecture armv8l, the same versions of 3.14.29 cores, but different android assemblies Also differ in processors: s912 ) and s905x (X96)

The essence of the problem: On one set-top box, the touchscreen starts up normally and works out of the box, on the other - not

The first console (on s905x):

After connecting usb touchscreen, the kernel says the following:

usb 1-2: new full-speed USB device number 3 using xhci-hcd input: ILITEK ILITEK Multi-Touch as /devices/c9000000.dwc3/xhci-hcd.0.auto/usb1/1-2/1-2:1.0/0003:222A:0045.0003/input/input5 hid-multitouch 0003:222A:0045.0003: input,hiddev0: USB HID v1.10 Device [ILITEK ILITEK Multi-Touch] on usb-xhci-hcd.0.auto-2/input0 

Next, the devices are created in / dev and everything works:

 root@p212:/ # ls /dev/usb/ hiddev0 input1-1:1.0 usbmisc1-1:1.0 

The second prefix:

After connecting usb touchscreen, the kernel says only the following and nothing more:

 usb 1-2: new full-speed USB device number 3 using xhci-hcd 

In / dev / usb, respectively, is empty, the touch does not work

In both cases, when connecting to / sys / bus / usb / devices /, a new device appears and it can be seen that it works under the usbhid driver. Also, on both consoles identical lsusb pins

 Bus 001 Device 003: ID 222a:0045 

Please tell me which way to dig, where there may be a problem with the second prefix.

  • Well, they probably have different implementation of xhci, respectively, and drivers, respectively, and the code is different, etc. Be sure to say that the power cord is connected, i.e. all the original ones really coincide until a certain moment. Oh, check out VBUS. - 0andriy

0