Le 02/10/2014 12:47, Dr. Werner Fink a écrit :
Hi,
just to be noted, that is not required to boot with openSUSE. Any nmodern Linux is enough, that is that there should be is the /sys file system and the filled /dev/input/ directory.
I'd like to know the output of
for n in /dev/input/event*; do udevadm info -a --name=$n done
then we might catch the input device for gpio-keys.8 and the power switch therein.
Here are the results (from ChromeOS): 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/12ca0000.i2c/i2c-4/i2c-104/104-001e/cros-ec-keyb.3/input/input0/event0': KERNEL=="event0" SUBSYSTEM=="input" DRIVER=="" looking at parent device '/devices/12ca0000.i2c/i2c-4/i2c-104/104-001e/cros-ec-keyb.3/input/input0': KERNELS=="input0" SUBSYSTEMS=="input" DRIVERS=="" ATTRS{name}=="cros-ec-i2c" ATTRS{phys}=="i2c-4-mux (chan_id 0)" ATTRS{uniq}=="" ATTRS{properties}=="0" looking at parent device '/devices/12ca0000.i2c/i2c-4/i2c-104/104-001e/cros-ec-keyb.3': KERNELS=="cros-ec-keyb.3" SUBSYSTEMS=="platform" DRIVERS=="cros-ec-keyb" looking at parent device '/devices/12ca0000.i2c/i2c-4/i2c-104/104-001e': KERNELS=="104-001e" SUBSYSTEMS=="i2c" DRIVERS=="cros-ec-i2c" ATTRS{name}=="cros-ec-i2c" looking at parent device '/devices/12ca0000.i2c/i2c-4/i2c-104': KERNELS=="i2c-104" SUBSYSTEMS=="i2c" DRIVERS=="" ATTRS{name}=="i2c-4-mux (chan_id 0)" looking at parent device '/devices/12ca0000.i2c/i2c-4': KERNELS=="i2c-4" SUBSYSTEMS=="i2c" DRIVERS=="" ATTRS{name}=="s3c2410-i2c" looking at parent device '/devices/12ca0000.i2c': KERNELS=="12ca0000.i2c" SUBSYSTEMS=="platform" DRIVERS=="s3c-i2c" 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/12c70000.i2c/i2c-1/1-0067/input/input1/event1': KERNEL=="event1" SUBSYSTEM=="input" DRIVER=="" looking at parent device '/devices/12c70000.i2c/i2c-1/1-0067/input/input1': KERNELS=="input1" SUBSYSTEMS=="input" DRIVERS=="" ATTRS{name}=="Cypress APA Trackpad (cyapa)" ATTRS{phys}=="i2c-1-0067/input0" ATTRS{uniq}=="" ATTRS{properties}=="5" looking at parent device '/devices/12c70000.i2c/i2c-1/1-0067': KERNELS=="1-0067" SUBSYSTEMS=="i2c" DRIVERS=="cyapa" ATTRS{product_id}=="CYTRA-116002-00" ATTRS{name}=="cyapa" ATTRS{firmware_version}=="2.13" ATTRS{baseline}=="107 92" looking at parent device '/devices/12c70000.i2c/i2c-1': KERNELS=="i2c-1" SUBSYSTEMS=="i2c" DRIVERS=="" ATTRS{name}=="s3c2410-i2c" looking at parent device '/devices/12c70000.i2c': KERNELS=="12c70000.i2c" SUBSYSTEMS=="platform" DRIVERS=="s3c-i2c" 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/sound.8/sound/card0/input2/event2': KERNEL=="event2" SUBSYSTEM=="input" DRIVER=="" looking at parent device '/devices/sound.8/sound/card0/input2': KERNELS=="input2" SUBSYSTEMS=="input" DRIVERS=="" ATTRS{name}=="DAISY-I2S HDMI Jack" ATTRS{phys}=="ALSA" ATTRS{uniq}=="" ATTRS{properties}=="0" looking at parent device '/devices/sound.8/sound/card0': KERNELS=="card0" SUBSYSTEMS=="sound" DRIVERS=="" ATTRS{id}=="DAISYI2S" ATTRS{number}=="0" looking at parent device '/devices/sound.8': KERNELS=="sound.8" SUBSYSTEMS=="platform" DRIVERS=="daisy-snd-max98095" 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/sound.8/sound/card0/input3/event3': KERNEL=="event3" SUBSYSTEM=="input" DRIVER=="" looking at parent device '/devices/sound.8/sound/card0/input3': KERNELS=="input3" SUBSYSTEMS=="input" DRIVERS=="" ATTRS{name}=="DAISY-I2S Headphone Jack" ATTRS{phys}=="ALSA" ATTRS{uniq}=="" ATTRS{properties}=="0" looking at parent device '/devices/sound.8/sound/card0': KERNELS=="card0" SUBSYSTEMS=="sound" DRIVERS=="" ATTRS{id}=="DAISYI2S" ATTRS{number}=="0" looking at parent device '/devices/sound.8': KERNELS=="sound.8" SUBSYSTEMS=="platform" DRIVERS=="daisy-snd-max98095" 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/sound.8/sound/card0/input4/event4': KERNEL=="event4" SUBSYSTEM=="input" DRIVER=="" looking at parent device '/devices/sound.8/sound/card0/input4': KERNELS=="input4" SUBSYSTEMS=="input" DRIVERS=="" ATTRS{name}=="DAISY-I2S Mic Jack" ATTRS{phys}=="ALSA" ATTRS{uniq}=="" ATTRS{properties}=="0" looking at parent device '/devices/sound.8/sound/card0': KERNELS=="card0" SUBSYSTEMS=="sound" DRIVERS=="" ATTRS{id}=="DAISYI2S" ATTRS{number}=="0" looking at parent device '/devices/sound.8': KERNELS=="sound.8" SUBSYSTEMS=="platform" DRIVERS=="daisy-snd-max98095" 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/gpio-keys.7/input/input5/event5': KERNEL=="event5" SUBSYSTEM=="input" DRIVER=="" looking at parent device '/devices/gpio-keys.7/input/input5': KERNELS=="input5" SUBSYSTEMS=="input" DRIVERS=="" ATTRS{name}=="gpio-keys.7" ATTRS{phys}=="gpio-keys/input0" ATTRS{uniq}=="" ATTRS{properties}=="0" looking at parent device '/devices/gpio-keys.7': KERNELS=="gpio-keys.7" SUBSYSTEMS=="platform" DRIVERS=="gpio-keys" ATTRS{keys}=="116" ATTRS{switches}=="0" ATTRS{disabled_keys}=="" ATTRS{disabled_switches}=="" Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org