From: Ian Pilcher <arequipeno@gmail.com>
To: linux-block@vger.kernel.org, linux-leds@vger.kernel.org
Cc: axboe@kernel.dk, Ian Pilcher <arequipeno@gmail.com>,
linux-kernel@vger.kernel.org, pavel@ucw.cz,
kernelnewbies@kernelnewbies.org
Subject: [RFC PATCH 1/8] docs: Add block device LED trigger documentation
Date: Wed, 28 Jul 2021 20:53:37 -0500 [thread overview]
Message-ID: <20210729015344.3366750-2-arequipeno@gmail.com> (raw)
In-Reply-To: <20210729015344.3366750-1-arequipeno@gmail.com>
* Document the sysfs attributes (/sys/class/block/led_trigger_*
and /sys/class/block/${DEV}/led_trigger) that can be used to
create, list, and delete block device LED triggers and to
set and clear device/trigger associations.
* Pull API documentation from block/blk-ledtrig.c (once it
exists).
Signed-off-by: Ian Pilcher <arequipeno@gmail.com>
---
Documentation/block/index.rst | 1 +
Documentation/block/led-triggers.rst | 124 +++++++++++++++++++++++++++
2 files changed, 125 insertions(+)
create mode 100644 Documentation/block/led-triggers.rst
diff --git a/Documentation/block/index.rst b/Documentation/block/index.rst
index 86dcf7159f99..a125ecdb4c7b 100644
--- a/Documentation/block/index.rst
+++ b/Documentation/block/index.rst
@@ -25,3 +25,4 @@ Block
stat
switching-sched
writeback_cache_control
+ led-triggers
diff --git a/Documentation/block/led-triggers.rst b/Documentation/block/led-triggers.rst
new file mode 100644
index 000000000000..a67e06c68073
--- /dev/null
+++ b/Documentation/block/led-triggers.rst
@@ -0,0 +1,124 @@
+.. SPDX-License-Identifier: GPL-2.0
+
+============
+LED Triggers
+============
+
+Available when ``CONFIG_BLK_LED_TRIGGERS=y``.
+
+sysfs interface
+===============
+
+Create a new block device LED trigger::
+
+ # echo foo > /sys/class/block/led_trigger_new
+
+The name must be unique among all LED triggers (not just block device LED
+triggers).
+
+Create two more::
+
+ # echo bar baz > /sys/class/block/led_trigger_new
+
+List the triggers::
+
+ # cat /sys/class/block/led_trigger_list
+ baz: 0
+ bar: 0
+ foo: 0
+
+(The number after each trigger is its reference count.)
+
+Associate a trigger with a block device::
+
+ # cat /sys/class/block/sda/led_trigger
+ (none)
+
+ # echo foo > /sys/class/block/sda/led_trigger
+ # cat /sys/class/block/sda/led_trigger
+ foo
+
+Note that ``foo``'s reference count has increased, and it cannot be deleted::
+
+ # cat /sys/class/block/led_trigger_list
+ baz: 0
+ bar: 0
+ foo: 1
+
+ # echo foo > /sys/class/block/led_trigger_del
+ -bash: echo: write error: Device or resource busy
+
+ # dmesg | tail -n 1
+ [23176.475424] blockdev LED trigger foo still in use
+
+Associate the ``foo`` trigger with an LED::
+
+ # cat /sys/class/leds/input1::scrolllock/trigger
+ none usb-gadget usb-host rc-feedback [kbd-scrolllock] kbd-numlock
+ kbd-capslock kbd-kanalock kbd-shiftlock kbd-altgrlock kbd-ctrllock
+ kbd-altlock kbd-shiftllock kbd-shiftrlock kbd-ctrlllock kbd-ctrlrlock
+ disk-activity disk-read disk-write ide-disk mtd nand-disk panic
+ audio-mute audio-micmute rfkill-any rfkill-none foo bar baz
+
+ # echo foo > /sys/class/leds/input1::scrolllock/trigger
+
+ # cat /sys/class/leds/input1::scrolllock/trigger
+ none usb-gadget usb-host rc-feedback [kbd-scrolllock] kbd-numlock
+ kbd-capslock kbd-kanalock kbd-shiftlock kbd-altgrlock kbd-ctrllock
+ kbd-altlock kbd-shiftllock kbd-shiftrlock kbd-ctrlllock kbd-ctrlrlock
+ disk-activity disk-read disk-write ide-disk mtd nand-disk panic
+ audio-mute audio-micmute rfkill-any rfkill-none [foo] bar baz
+
+Reads and writes to ``sda`` should now cause the scroll lock LED on your
+keyboard to blink (assuming that it has one).
+
+Multiple devices can be associated with a trigger::
+
+ # echo foo > /sys/class/block/sdb/led_trigger
+
+ # cat /sys/class/block/led_trigger_list
+ baz: 0
+ bar: 0
+ foo: 2
+
+Activity on either ``sda`` or ``sdb`` should now be shown by your scroll lock
+LED.
+
+Clear ``sda``'s LED trigger::
+
+ # echo > /sys/class/block/sda/led_trigger
+
+ # cat /sys/class/block/sda/led_trigger
+ (none)
+
+ # cat /sys/class/block/led_trigger_list
+ baz: 0
+ bar: 0
+ foo: 1
+
+And ``sdb``'s trigger::
+
+ # echo > /sys/class/block/sdb/led_trigger
+
+Delete the triggers::
+
+ # echo foo bar baz > /sys/class/block/led_trigger_del
+
+ # cat /sys/class/block/led_trigger_list
+
+ # cat /sys/class/leds/input1::scrolllock/trigger
+ none usb-gadget usb-host rc-feedback [kbd-scrolllock] kbd-numlock
+ kbd-capslock kbd-kanalock kbd-shiftlock kbd-altgrlock kbd-ctrllock
+ kbd-altlock kbd-shiftllock kbd-shiftrlock kbd-ctrlllock kbd-ctrlrlock
+ disk-activity disk-read disk-write ide-disk mtd nand-disk panic
+ audio-mute audio-micmute rfkill-any rfkill-none
+
+Also see **Userspace LEDs** (``Documentation/leds/uleds.rst``).
+
+Kernel API
+==========
+
+``#include <linux/blk-ledtrig.h>``
+
+.. kernel-doc:: block/blk-ledtrig.c
+ :export:
--
2.31.1
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2021-07-29 1:56 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-29 1:53 [RFC PATCH 0/8] Add configurable block device LED triggers Ian Pilcher
2021-07-29 1:53 ` Ian Pilcher [this message]
2021-07-29 3:09 ` [RFC PATCH 1/8] docs: Add block device LED trigger documentation Valdis Klētnieks
2021-07-29 15:52 ` Ian Pilcher
2021-07-30 5:22 ` Greg KH
2021-07-29 5:53 ` Greg KH
2021-07-29 11:59 ` Marek Behún
2021-07-29 18:03 ` Ian Pilcher
2021-07-29 1:53 ` [RFC PATCH 2/8] block: Add block device LED trigger list Ian Pilcher
2021-07-29 3:14 ` Valdis Klētnieks
2021-07-29 15:55 ` Ian Pilcher
2021-07-29 1:53 ` [RFC PATCH 3/8] block: Add kernel APIs to create & delete block device LED triggers Ian Pilcher
2021-07-29 3:45 ` Valdis Klētnieks
2021-07-29 16:16 ` Ian Pilcher
2021-07-29 5:52 ` Greg KH
2021-07-29 1:53 ` [RFC PATCH 4/8] block: Add block class attributes to manage LED trigger list Ian Pilcher
2021-07-29 5:54 ` Greg KH
2021-07-29 1:53 ` [RFC PATCH 5/8] block: Add block device LED trigger info to struct genhd Ian Pilcher
2021-07-29 1:53 ` [RFC PATCH 6/8] block: Add kernel APIs to set & clear per-block device LED triggers Ian Pilcher
2021-07-29 1:53 ` [RFC PATCH 7/8] block: Add block device attributes to set & clear " Ian Pilcher
2021-07-29 1:53 ` [RFC PATCH 8/8] block: Blink device LED when request is sent to low-level driver Ian Pilcher
2021-07-29 8:54 ` [RFC PATCH 0/8] Add configurable block device LED triggers Pavel Machek
2021-07-29 17:03 ` Ian Pilcher
2021-07-29 18:35 ` Pavel Machek
2021-07-29 19:14 ` Ian Pilcher
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210729015344.3366750-2-arequipeno@gmail.com \
--to=arequipeno@gmail.com \
--cc=axboe@kernel.dk \
--cc=kernelnewbies@kernelnewbies.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@ucw.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).