Hi!
> Add Documentation/ABI/testing/sysfs-class-led-trigger-blkdev to
> document:
>
> * /sys/class/leds/<led>/blink_time
> * /sys/class/leds/<led>/check_interval
> * /sys/class/leds/<led>/blink_on_{read,write,discard,flush}
> * /sys/class/leds/<led>/link_dev_by_path
> * /sys/class/leds/<led>/unlink_dev_by_path
> * /sys/class/leds/<led>/linked_devices
>
> +What: /sys/class/leds/<led>/check_interval
> +Date: September 2022
> +Contact: Ian Pilcher <arequipeno@xxxxxxxxx>
> +Description:
> + Frequency (in milliseconds) with which block devices linked to
> + this LED will be checked for activity and the LED will
> + (potentially) be blinked.
Frequency -> interval.
> +What: /sys/class/leds/<led>/link_dev_by_path
> +Date: September 2022
> +Contact: Ian Pilcher <arequipeno@xxxxxxxxx>
> +Description:
> + Associate a block device with this LED by writing the path to
> + the device special file (e.g. /dev/sda) to this attribute.
> + Symbolic links are followed.
Following symbolic links to paths written to file is "interesting".
> +What: /sys/class/leds/<led>/linked_devices
> +Date: September 2022
> +Contact: Ian Pilcher <arequipeno@xxxxxxxxx>
> +Description:
> + Directory containing links to all block devices that are
> + associated with this LED. (Note that the names of the
> + symbolic links in this directory are *kernel* names, which
> + may not match the device special file paths written to
> + link_device and unlink_device.)
As is mismatch between kernel names here and what names the other file
expects.
Can we get something more reasonable?
Thanks,
Pavel
--
People of Russia, stop Putin before his war on Ukraine escalates.
Attachment:
signature.asc
Description: PGP signature
