On 11/12/2018 08:05 PM, Pavel Machek wrote: > Hi! > >>>>> My system looks like this: >>>>> >>>>> input16::capslock tpacpi::bay_active tpacpi::standby >>>>> input16::numlock tpacpi::dock_active tpacpi::thinklight >>>>> input16::scrolllock tpacpi::dock_batt tpacpi::thinkvantage >>>>> input5::capslock tpacpi::dock_status1 tpacpi::unknown_led >>>>> input5::numlock tpacpi::dock_status2 tpacpi::unknown_led2 >>>>> input5::scrolllock tpacpi:green:batt tpacpi::unknown_led3 > >>> But it is not just for backwards compatibility. See my examples above, >>> it is needed to tell which device the LED is asociated with, and it is >>> absolutely required for USB devices (for example). >> >> For USB devices there is already ledtrig-usbport available, which >> provides sysfs interface for defining and reading the usb ports, >> the status of which the LED indicates. Since the USB devices can be >> attached/removed dynamically, it would be impossible to reflect >> the associations in the LED class device name. > > I'm not talking USB activity. I'm talking USB devices with LEDs on > them, like for example keyboards. > > Please take a look at example above. input16::numlock ; > input5::numlock . You absolutely need device part. It would be redundant since there is "device" symbolic link created in given LED class device sysfs directory, pointing to the corresponding input device directory, like in case of my USB keyboard: #/sys/class/leds/input5::scrolllock$ ls -l total 0 -rw-r--r-- 1 root root 4096 Nov 12 20:22 brightness lrwxrwxrwx 1 root root 0 Nov 12 20:22 device -> ../../input5 -r--r--r-- 1 root root 4096 Nov 12 20:22 max_brightness drwxr-xr-x 2 root root 0 Nov 12 20:22 power lrwxrwxrwx 1 root root 0 Nov 12 20:04 subsystem -> ../../../../../../../../../../../class/leds -rw-r--r-- 1 root root 4096 Nov 12 20:22 trigger >>> And even for "embedded" stuff like routers, we want eth0:green:link, >>> eth0:yellow:activity and not some kind of hack. >> >> eth0 is not something you can be certain of at the stage of defining DT >> node. > > In the common case DT is used for, yes, you can, because whole system > is in one box. Only when all kernel modules are built-in. > (And really DT does not matter. We are talking kernel <-> user > interface here). OK, I was fixed on the devicename understood as LED controller name. >>> Ideally, colors would come from fixed list, functions would come from >>> fixed list, and device part would come from name used elsewhere in the >>> kernel. >>> >>> (And yes, it probably means we should have something in device tree to >>> link LED to its device. device = "name" would be good start...) >> >> Why would you need such link? > > Because userspace needs that information? > > Say you have raid array, with "error" leds for each drive (your list > already contains "hdderr"). Now userland detects problem with hdparm > on /dev/sdi. It would like to turn on corresponding LED. > > How do you propose we do that? Similarly as in case of USB keyboard. -- Best regards, Jacek Anaszewski
