input devices - Identify the entries of xinput - Ask Ubuntu

some of entries of xinput strange

⎡ virtual core pointer                      id=2    [master pointer  (3)] ⎜   ↳ virtual core xtest pointer                id=4    [slave  pointer  (2)] ⎜   ↳ syna7501:00 06cb:12b8 pen                 id=11   [slave  pointer  (2)] ⎜   ↳ syna7501:00 06cb:12b8                     id=12   [slave  pointer  (2)] ⎜   ↳ synps/2 synaptics touchpad                id=16   [slave  pointer  (2)] ⎣ virtual core keyboard                     id=3    [master keyboard (2)]     ↳ virtual core xtest keyboard               id=5    [slave  keyboard (3)]     ↳ power button                              id=6    [slave  keyboard (3)]     ↳ video bus                                 id=7    [slave  keyboard (3)]     ↳ video bus                                 id=8    [slave  keyboard (3)]     ↳ power button                              id=9    [slave  keyboard (3)]     ↳ hp truevision hd                          id=10   [slave  keyboard (3)]     ↳ intel virtual button driver               id=13   [slave  keyboard (3)]     ↳ intel virtual button driver               id=14   [slave  keyboard (3)]     ↳ @ translated set 2 keyboard              id=15   [slave  keyboard (3)]     ↳ hp wmi hotkeys                            id=17   [slave  keyboard (3)]     ↳ hp wireless hotkeys                       id=18   [slave  keyboard (3)] 

things virtual core xtest pointer or 2 syna7501:00 06cb:12b8

where can find documentation these entries? which 1 touch screen example?

...i tried parameter list-props it's not helpful. in fact outputs things want find documentation for.

for example; xinput list-props 11:

device 'syna7501:00 06cb:12b8 pen':     device enabled (137):   1     coordinate transformation matrix (139): 1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000     device accel profile (263): 0     device accel constant deceleration (264):   1.000000     device accel adaptive deceleration (265):   1.000000     device accel velocity scaling (266):    10.000000     device product id (255):    1739, 4792     device node (256):  "/dev/input/event12"     evdev axis inversion (267): 0, 0     evdev axis calibration (268):   <no items>     evdev axes swap (269):  0     axis labels (270):  "abs x" (260), "abs y" (261), "abs pressure" (262)     button labels (271):    "button 0" (259), "button unknown" (258), "button unknown" (258), "button wheel up" (143), "button wheel down" (144)     evdev scrolling distance (272): 0, 0, 0     evdev middle button emulation (273):    0     evdev middle button timeout (274):  50     evdev third button emulation (275): 0     evdev third button emulation timeout (276): 1000     evdev third button emulation button (277):  3     evdev third button emulation threshold (278):   20     evdev wheel emulation (279):    0     evdev wheel emulation axes (280):   0, 0, 4, 5     evdev wheel emulation inertia (281):    10     evdev wheel emulation timeout (282):    200     evdev wheel emulation button (283): 4     evdev drag lock buttons (284):  0 

i want able control parameters.

model these outputs "hp envy x360 - 15-w107ne"

syna7501:00 06cb:12b8 , along pen layer, touchscreen.

from https://www.x.org/wiki/xorginputdriverspec/#index3h2:

virtual core devices available, produce no independent events. events come extension devices. excellent fit server supports multiple core devices , device hot-plugging. recent integration of mpx, multiple virtual core devices may exist. referred master devices.

essentially, virtual core pointer/keyboard can delegated software , hardware perform tasks, capturing mouse, or enabling multiple mouse cursors.

as changing parameters, use command:

xinput set-prop <device-id> <param-id> <values> 

note values depend on parameter. example, flipping the x-axis/y-axis need 2 values- 0 0 results in no inversion, 0 1 results in y-axis inversion- first value x-axis, , second value y-axis.

edit, documentation:

evdev man page: ftp://www.x.org/pub/x11r7.5/doc/man/man4/evdev.4.html