From: Pavel Machek <pavel@suse.cz>
To: Robert Schwebel <r.schwebel@pengutronix.de>
Cc: vojtech@suse.cz, rpurdie@rpsys.net, 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 22:13:34 +0100 [thread overview]
Message-ID: <20051102211334.GH23943@elf.ucw.cz> (raw)
In-Reply-To: <20051102202622.GN23316@pengutronix.de>
Hi!
> > yellow off: not charging
> > yellow on: charging
> > yellow fast blink: charge error
> >
> > I think even slow blinking was used somewhere. I have some code from
> > John Lenz (attached); it uses sysfs interface, exports led collor, and
> > allows setting different frequencies.
> >
> > Is that acceptable, or should some other interface be used?
>
> IMHO reducing digital outputs to LEDs goes not far enough. All System-
> on-Chip CPUs have General Purpose I/O pins today, which can act as
> inputs or outputs and may be used for LEDs, matrix keyboard lines,
We have some leds that are *not* on GPIO pins (like driven by
ACPI). We'd like to support those, too.
Pavel
--
Thanks, Sharp!
next prev parent reply other threads:[~2005-11-02 21:14 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-01 23:44 Pavel Machek
2005-11-02 0:39 ` Richard Purdie
2005-11-02 1:03 ` John Lenz
2005-11-02 8:01 ` Chase Venters
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 [this message]
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=20051102211334.GH23943@elf.ucw.cz \
--to=pavel@suse.cz \
--cc=lenz@cs.wisc.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=r.schwebel@pengutronix.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®