Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- Udevadm info starts with the device specified by the devpath and then
- walks up the chain of parent devices. It prints for every device
- found, all possible attributes in the udev rules key format.
- A rule to match, can be composed by the attributes of the device
- and the attributes from one single parent device.
- looking at device '/devices/pci0000:00/808622C1:00/i2c-0/i2c-DRV2604:00/input/input15/event16':
- KERNEL=="event16"
- SUBSYSTEM=="input"
- DRIVER==""
- looking at parent device '/devices/pci0000:00/808622C1:00/i2c-0/i2c-DRV2604:00/input/input15':
- KERNELS=="input15"
- SUBSYSTEMS=="input"
- DRIVERS==""
- ATTRS{properties}=="0"
- ATTRS{uniq}==""
- ATTRS{phys}==""
- ATTRS{name}=="drv260x:haptics"
- looking at parent device '/devices/pci0000:00/808622C1:00/i2c-0/i2c-DRV2604:00':
- KERNELS=="i2c-DRV2604:00"
- SUBSYSTEMS=="i2c"
- DRIVERS=="drv260x-haptics"
- ATTRS{name}=="DRV2604:00"
- looking at parent device '/devices/pci0000:00/808622C1:00/i2c-0':
- KERNELS=="i2c-0"
- SUBSYSTEMS=="i2c"
- DRIVERS==""
- ATTRS{name}=="Synopsys DesignWare I2C adapter"
- looking at parent device '/devices/pci0000:00/808622C1:00':
- KERNELS=="808622C1:00"
- SUBSYSTEMS=="platform"
- DRIVERS=="i2c_designware"
- ATTRS{driver_override}=="(null)"
- looking at parent device '/devices/pci0000:00':
- KERNELS=="pci0000:00"
- SUBSYSTEMS==""
- DRIVERS==""
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement