diff options
author | Richard Purdie <rpurdie@rpsys.net> | 2007-10-31 15:00:07 +0100 |
---|---|---|
committer | Richard Purdie <rpurdie@rpsys.net> | 2008-02-07 09:47:00 +0000 |
commit | 6c152beefbf90579d21afc4f7e075b1f801f9a75 (patch) | |
tree | c5814496de9e29662d558deddb31e0a0c4549cd7 /Documentation/leds-class.txt | |
parent | cec035de8265b18252742ef359b12e9694641112 (diff) | |
download | talos-obmc-linux-6c152beefbf90579d21afc4f7e075b1f801f9a75.tar.gz talos-obmc-linux-6c152beefbf90579d21afc4f7e075b1f801f9a75.zip |
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/leds-class.txt')
-rw-r--r-- | Documentation/leds-class.txt | 5 |
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 |