From: John Lenz <lenz@cs.wisc.edu>
To: linux-kernel@vger.kernel.org
Subject: [PATCH 2.6.8.1 0/2] leds: new class for led devices
Date: Thu, 02 Sep 2004 20:33:10 +0000 [thread overview]
Message-ID: <1094157190l.4235l.2l@hydra> (raw)
This is an attempt to provide an alternative to the current arm
specific led interface. This arm interface does not integrate well
with the device model and sysfs.
We create a new class that drivers can register a leds_properties
structure with. Each led that is registered is assigned a number, and
three attributes are exported to sysfs in /sys/class/leds/1/, /sys/
class/leds/2, etc.
color : a read only string attribute that shows the available colors of
this led. If it is a multi-color led, then the colors are seperated by
a "/" (for example "green/blue").
function : a read/write attribute that sets the current function of
this led. The available options are
timer : the led blinks on and off on a timer
idle : the led turns off when the system is idle and on when not idle
power : the led represents the current power state
user : the led is controlled by user space
light : a read/write attribute that allows userspace to see the current
status of the led. If function="user" then writing to this attribute
will change the led on or off. If function != "user" then writing has
no effect.
light is an integer, where 0 means off, 1 means on first color, 2
means on second color, etc. (for example, if color="green/blue" then
light=1 means turn led on to green and if light=2 means turn led on to
blue.
A device and driver symlink point to the actual driver and such, so any
extra attributes can also be registered.
Signed-off-by: John Lenz <lenz@cs.wisc.edu>
next reply other threads:[~2004-09-02 20:35 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-02 20:33 John Lenz [this message]
2004-09-02 20:34 ` [PATCH 2.6.8.1 1/2] leds: new class for led devices John Lenz
2004-09-02 20:38 ` [PATCH 2.6.8.1 2/2] " John Lenz
2004-09-03 4:54 ` [PATCH 2.6.8.1 0/2] " Kalin KOZHUHAROV
2004-09-03 11:32 ` Geert Uytterhoeven
2004-09-03 12:06 ` Jan-Benedict Glaw
2004-09-03 18:47 ` John Lenz
2004-09-03 22:25 ` Russell King
2004-09-03 23:19 ` John Lenz
2004-09-04 11:12 ` Pavel Machek
2004-09-04 20:53 ` Russell King
2004-09-04 21:41 ` Pavel Machek
2004-09-06 7:36 ` John Lenz
2004-09-03 13:17 ` Robert Schwebel
2004-09-03 13:31 ` Robert Schwebel
2004-09-03 8:00 ` Oliver Neukum
2004-09-03 13:51 ` Pavel Machek
2004-09-03 18:38 ` John Lenz
2004-09-03 18:55 ` Russell King
2004-09-03 19:09 ` John Lenz
2004-09-03 19:51 ` Russell King
2004-09-03 20:35 ` John Lenz
2004-09-04 11:09 ` Pavel Machek
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=1094157190l.4235l.2l@hydra \
--to=lenz@cs.wisc.edu \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.