archive mirror
 help / color / mirror / Atom feed
From: Pavel Machek <>
	kernel list <>,,
Subject: [PATCH] Documentation: leds: standartizing LED names
Date: Fri, 20 Aug 2021 10:33:27 +0200	[thread overview]
Message-ID: <20210820083327.GB22757@amd> (raw)

[-- Attachment #1: Type: text/plain, Size: 2762 bytes --]


I pushed this into the LED tree. It was long overdue. If you have LED
with functionality that is common across systems (for example LEDs on
ethernet ports are quite common), please add proposed naming here.

Best regards,

commit 09f1273064eea23ec41fb206f6eccc2bf79d1fa1
Author: Pavel Machek <>
Date:   Fri Aug 20 10:26:24 2021 +0200

    Documentation: leds: standartizing LED names
    We have a list of valid functions, but LED names in sysfs are still
    far from being consistent. Create list of "well known" LED names so we
    nudge people towards using same LED names (except color) for same
    Signed-off-by: Pavel Machek <>

diff --git a/Documentation/leds/well-known-leds.txt b/Documentation/leds/well-known-leds.txt
new file mode 100644
index 000000000000..4a8b9dc4bf52
--- /dev/null
+++ b/Documentation/leds/well-known-leds.txt
@@ -0,0 +1,58 @@
+-*- org -*-
+It is somehow important to provide consistent interface to the
+userland. LED devices have one problem there, and that is naming of
+directories in /sys/class/leds. It would be nice if userland would
+just know right "name" for given LED function, but situation got more
+Anyway, if backwards compatibility is not an issue, new code should
+use one of the "good" names from this list, and you should extend the
+list where applicable.
+Legacy names are listed, too; in case you are writing application that
+wants to use particular feature, you should probe for good name, first,
+but then try the legacy ones, too.
+Notice there's a list of functions in include/dt-bindings/leds/common.h .
+* Keyboards
+Good: "input*:*:capslock"
+Good: "input*:*:scrolllock"
+Good: "input*:*:numlock"
+Legacy: "shift-key-light" (Motorola Droid 4, capslock)
+Set of common keyboard LEDs, going back to PC AT or so.
+Legacy: "tpacpi::thinklight" (IBM/Lenovo Thinkpads)
+Legacy: "lp5523:kb{1,2,3,4,5,6}" (Nokia N900)
+Frontlight/backlight of main keyboard.
+Legacy: "button-backlight" (Motorola Droid 4)
+Some phones have touch buttons below screen; it is different from main
+keyboard. And this is their backlight.
+* Sound subsystem
+Good: "platform:*:mute"
+Good: "platform:*:micmute"
+LEDs on notebook body, indicating that sound input / output is muted.
+* System notification
+Legacy: "status-led:{red,green,blue}" (Motorola Droid 4)
+Legacy: "lp5523:{r,g,b}" (Nokia N900)
+Phones usually have multi-color status LED.
+* Power management
+Good: "platform:*:charging" (allwinner sun50i)
+* Screen
+Good: ":backlight" (Motorola Droid 4)


[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

                 reply	other threads:[~2021-08-20  8:33 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210820083327.GB22757@amd \ \ \ \ \ \
    --subject='Re: [PATCH] Documentation: leds: standartizing LED names' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).