Libinput-touch screen detection

sanjay anvekar sanjayanvekar at yahoo.com
Wed Oct 2 16:40:24 UTC 2019


 Hi Peter,   Thank you for your response. I tried changing udev properties but it didn't help. Here is output from udevadm command.udevadm info /dev/input/event0P: /devices/soc0/soc/2100000.aips-bus/21a4000.i2c/i2c-1/1-0048/input/input0/event0N: input/event0S: input/by-path/platform-21a4000.i2c-eventE: DEVLINKS=/dev/input/by-path/platform-21a4000.i2c-eventE: DEVNAME=/dev/input/event0E: DEVPATH=/devices/soc0/soc/2100000.aips-bus/21a4000.i2c/i2c-1/1-0048/input/input0/event0E: ID_INPUT=1E: ID_PATH=platform-21a4000.i2cE: ID_PATH_TAG=platform-21a4000_i2cE: MAJOR=13E: MINOR=64E: SUBSYSTEM=inputE: USEC_INITIALIZED=2341962

Also tried with 'libinput-debug-events' and following is outputlibinput-debug-events --device /dev/input/event0 --verboseinput device 'touchscreen', /dev/input/event0 not tagged as input devicefailed to create input device '/dev/input/event0'.Failed to initialized device /dev/input/event0
I tested this input device with 'evetest' application and it works, but doesn't work with libinput.
How do I debug further and conclude that it is Kernel driver issue ? Please let me know.
Thanks & Best Regards,Sanjay




    On Wednesday, 2 October, 2019, 02:50:39 pm GMT+1, Peter Hutterer <peter.hutterer at who-t.net> wrote:  
 
 On Tue, Oct 01, 2019 at 04:08:17PM +0000, sanjay anvekar wrote:
> Hi All,   I am new to Wayland. I am using Weston 1.9.0 on imx6x board with
> touchscreen display of resolution 1024x768. I am seeing touchscreen as
> /dev/input/event0 device and it is working. I confirmed functioning of
> touchscreen using "cat /dev/input/event0" command. Unfortunately, I don't
> see touchscreen is listed by libinput application i.e.
> 'libinput-list-devices'. If I connect USB mouse then I see mouse is listed
> by 'libinput-list-devices' application, but not touchscreen. I am running
> Qt application and it is not able to detect touch inputs. Please let me
> know your inputs to resolve this problem.

most likely the udev property ID_INPUT and/or ID_INPUT_TOUCHSCREEN is
missing for this device, libinput debug-events --verbose should print
*something* at least for the device.

If the property is missing though that means that it doesn't export the
correct evdev bits to be picked up by the udev builtin, so most likely the
kernel driver needs to be fixed.

Cheers,
  Peter
  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/wayland-devel/attachments/20191002/b3a8dd01/attachment.html>


More information about the wayland-devel mailing list