From: Chase Venters <chase.venters@clientec.com>
To: Richard Purdie <rpurdie@rpsys.net>
Cc: Pavel Machek <pavel@suse.cz>,
vojtech@suse.cz, lenz@cs.wisc.edu,
kernel list <linux-kernel@vger.kernel.org>,
Russell King <rmk@arm.linux.org.uk>
Subject: Re: best way to handle LEDs
Date: Wed, 2 Nov 2005 02:01:45 -0600 [thread overview]
Message-ID: <200511020202.07958.chase.venters@clientec.com> (raw)
In-Reply-To: <1130891953.8489.83.camel@localhost.localdomain>
On Tuesday 01 November 2005 06:38 pm, Richard Purdie wrote:
> led triggers would be connected to leds via sysfs. Each trigger would
> probably have a number you could echo into an led's trigger attribute.
> Sensible default mappings could be had by assigning a default trigger to
> a device by name in the platform code that declares the led.
>
> A trigger of "0" would mean the led becomes under userspace control via
> sysfs for whatever userspace wishes to do with it.
Any reason to represent the triggers as numbers in sysfs? I'm a fan of how the
IO scheduler is chosen on a block device. The file looks like:
noop [anticipatory] deadline cfq
You get a list of all available triggers, which one is active (and it's easy
enough for user space code to parse). Obviously, to select a trigger, you
just write its name to the file. Instead of 0, you say user, etc...
Cheers,
Chase Venters
next prev parent reply other threads:[~2005-11-02 8:02 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-01 23:44 best way to handle LEDs Pavel Machek
2005-11-02 0:39 ` Richard Purdie
2005-11-02 1:03 ` John Lenz
2005-11-02 8:01 ` Chase Venters [this message]
2005-11-02 13:56 ` Pavel Machek
2005-11-02 14:38 ` Richard Purdie
2005-11-02 21:11 ` Pavel Machek
2005-11-02 22:05 ` Richard Purdie
2005-11-02 1:57 ` root
2005-11-02 11:40 ` Geert Uytterhoeven
2005-11-02 2:47 ` Ben Dooks
2005-11-02 9:48 ` Alessandro Zummo
2005-11-02 9:51 ` Pavel Machek
2005-11-03 2:31 ` John Lenz
2005-11-07 23:30 ` Pavel Machek
2005-11-08 0:27 ` John Lenz
2005-11-08 9:28 ` Pavel Machek
2005-11-08 12:07 ` Richard Purdie
2005-11-08 13:14 ` Pavel Machek
2005-11-02 10:18 ` Paul Mundt
2005-11-02 20:26 ` Robert Schwebel
2005-11-02 21:13 ` Pavel Machek
2005-11-02 21:33 ` Robert Schwebel
2005-11-03 2:52 ` John Lenz
2005-11-03 6:21 ` Robert Schwebel
2005-11-03 8:15 ` Russell King
2005-11-03 9:57 ` Pavel Machek
2005-11-03 14:49 ` Russell King
2005-11-03 15:34 ` Vojtech Pavlik
2005-11-03 16:01 ` Russell King
2005-11-03 16:11 ` Vojtech Pavlik
2005-11-03 16:38 ` linux-os (Dick Johnson)
2005-11-03 16:35 ` Pavel Machek
2005-11-04 0:41 ` Stefan Smietanowski
2005-11-03 14:26 ` Rich Walker
2005-11-03 3:09 ` Rob Landley
2005-11-03 8:37 ` Geert Uytterhoeven
2005-11-03 9:59 ` 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=200511020202.07958.chase.venters@clientec.com \
--to=chase.venters@clientec.com \
--cc=lenz@cs.wisc.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
--cc=rmk@arm.linux.org.uk \
--cc=rpurdie@rpsys.net \
--cc=vojtech@suse.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 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.