From: Pavel Machek <pavel@ucw.cz>
To: Bryan Wu <cooloney@gmail.com>
Cc: "Raphaël Teysseyre" <rteysseyre@gmail.com>,
"Joe Xue" <lgxue@hotmail.com>,
"rpurdie@rpsys.net" <rpurdie@rpsys.net>,
"Linux LED Subsystem" <linux-leds@vger.kernel.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH RFC] leds: Add status code trigger
Date: Tue, 10 Mar 2015 09:00:42 +0100 [thread overview]
Message-ID: <20150310080042.GA27585@amd> (raw)
In-Reply-To: <CAK5ve-KTmkh4XBLAEhvUFme+qmTb9hFKxQnvisxySw1skTLr1w@mail.gmail.com>
Hi!
> > Here is a new trigger. It would allow userspace to make an LED
> > blink with a pattern to show a status (or error) code to a human.
> > This is useful for embedded systems without screen or network
> > access. Obviously, the LED will keep on blinking even if userspace
> > crashes.
>
> Thanks for bringing up this. We did get similar idea and patches
> before. The problem is people are seeking more complicated
> applications like define a script language to do blink such as
> "~~~xxxxx~x~x" and there is a decoder to translate this script to
> program the leds.
>
> It was pointed out we need another API between kernel and user space,
> but I don't have such time to do that.
>
> I will add more people to review this patch and discuss this new
> feature.
And then there are LEDs that can do smooth brightness transitions, and
LEDs that provide RGB colors, and programmable LED engines.
I think I have interface to handle most of the issues: array of
integers in "brightness, length in miliseconds".
So for example slowly blinking LED would be "0 1000msec, 255 1000
msec". On off pattern would be "0 1000msec, 255 0msec, 255 1000msec, 0
0msec".
Rapahael, this should be able to do all the stuff you want to do. It
can also do morse code, slow blinks, and combination of both. Do you
want to try implementing it?
Thanks,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2015-03-10 8:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-19 8:26 [PATCH RFC] leds: Add status code trigger Raphaël Teysseyre
2015-03-09 21:15 ` Bryan Wu
2015-03-10 8:00 ` Pavel Machek [this message]
[not found] ` <BLU172-W3716E59BC9E98F60F424C4AC180@phx.gbl>
2015-03-10 19:22 ` Pavel Machek
2015-03-11 15:10 ` Raphaël Teysseyre
2015-03-11 19:02 ` Pavel Machek
2015-03-12 6:56 ` Raphaël Teysseyre
2015-03-16 10:06 ` [PATCH] leds: Add arbitrary pattern trigger Raphaël Teysseyre
2015-03-16 11:55 ` Pavel Machek
2015-03-16 16:49 ` Raphaël Teysseyre
2015-03-16 12:20 ` Pavel Machek
2015-03-16 12:40 ` Paul Bolle
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=20150310080042.GA27585@amd \
--to=pavel@ucw.cz \
--cc=cooloney@gmail.com \
--cc=lgxue@hotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=rpurdie@rpsys.net \
--cc=rteysseyre@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).