root@c7x0:/sys# udevinfo -a -p /sys/class/input/event1/
udevinfo starts with the device the node belongs to and then walks up the
device chain, to print for every device found, all possibly useful attributes
in the udev key format.
Only attributes within one device section may be used together in one rule,
to match the device for which the node will be created.
device '/sys/class/input/event1' has major:minor 13:65
looking at class device '/sys/class/input/event1':
SUBSYSTEM=="input"
SYSFS{dev}=="13:65"
follow the "device"-link to the physical device:
looking at the device chain at '/sys/devices/platform/sharp-scoop/corgi-ssp/corgi-ts':
BUS=="platform"
ID=="corgi-ts"
DRIVER=="corgi-ts"
looking at the device chain at '/sys/devices/platform/sharp-scoop/corgi-ssp':
BUS=="platform"
ID=="corgi-ssp"
DRIVER=="corgi-ssp"
looking at the device chain at '/sys/devices/platform/sharp-scoop':
BUS=="platform"
ID=="sharp-scoop"
DRIVER=="sharp-scoop"
looking at the device chain at '/sys/devices/platform':
BUS==""
ID=="platform"
DRIVER=="unknown"
root@c7x0:/sys#