Code: Select all
[email protected]:~ $ ls -l /dev/input/by-path
lrwxrwxrwx 1 root root 9 Dez 8 22:44 platform-3f215080.spi-event -> ../event1
lrwxrwxrwx 1 root root 9 Dez 8 22:44 platform-3f980000.usb-usb-0:1.3:1.2-event-mouse -> ../event0
lrwxrwxrwx 1 root root 9 Dez 8 22:44 platform-3f980000.usb-usb-0:1.3:1.2-mouse -> ../mouse0
The by-path entry is showing us what each of the event sources ("event0", "event1", "mouse0") corresponds to. In this case /dev/input/event1 looks like it should be events from the touchscreen.
If you are able to run a command while the touchscreen is connected, and assuming the mapping above still applies (if not, change the "event*" part of the command to match), try leaving this running in a shell:
This should do nothing until your mouse moves, then you should see a stream of hex numbers. Now try the other event source:
This should be equally quiet until the touchscreen is used. Do you get any output? If so, the touchscreen wiring and DT configuration appears to be correct, and the problem is in the higher layers of software.