summaryrefslogtreecommitdiff
path: root/Documentation
diff options
context:
space:
mode:
authorRichard Purdie <rpurdie@rpsys.net>2007-10-31 17:00:07 +0300
committerRichard Purdie <rpurdie@rpsys.net>2008-02-07 12:47:00 +0300
commit6c152beefbf90579d21afc4f7e075b1f801f9a75 (patch)
treec5814496de9e29662d558deddb31e0a0c4549cd7 /Documentation
parentcec035de8265b18252742ef359b12e9694641112 (diff)
downloadlinux-6c152beefbf90579d21afc4f7e075b1f801f9a75.tar.xz
leds: Standardise LED naming scheme
As discussed on LKML some notion of 'function' is needed in LED naming. This patch adds this to the documentation and standardises existing LED drivers. Signed-off-by: Richard Purdie <rpurdie@rpsys.net>
Diffstat (limited to 'Documentation')
-rw-r--r--Documentation/leds-class.txt5
1 files changed, 3 insertions, 2 deletions
diff --git a/Documentation/leds-class.txt b/Documentation/leds-class.txt
index 8c35c0426110..877af6efc18b 100644
--- a/Documentation/leds-class.txt
+++ b/Documentation/leds-class.txt
@@ -39,12 +39,13 @@ LED Device Naming
Is currently of the form:
-"devicename:colour"
+"devicename:colour:function"
There have been calls for LED properties such as colour to be exported as
individual led class attributes. As a solution which doesn't incur as much
overhead, I suggest these become part of the device name. The naming scheme
-above leaves scope for further attributes should they be needed.
+above leaves scope for further attributes should they be needed. If sections
+of the name don't apply, just leave that section blank.
Known Issues