From: Pavel Machek <pavel@ucw.cz>
To: "Gaël PORTAY" <g.portay@overkiz.com>,
"Rob Landley" <rob@landley.net>, "Bryan Wu" <cooloney@gmail.com>,
"Richard Purdie" <rpurdie@rpsys.net>,
"Milo(Woogyom) Kim" <milo.kim@ti.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-leds@vger.kernel.org
Subject: Re: [RFC PATCH] led: add Cycle LED trigger.
Date: Sun, 23 Jun 2013 11:53:07 +0200 [thread overview]
Message-ID: <20130623095305.GA3669@amd.pavel.ucw.cz> (raw)
In-Reply-To: <20130622164300.GB19420@earth.universe>
On Sat 2013-06-22 18:43:01, Sebastian Reichel wrote:
> On Sat, Jun 22, 2013 at 01:26:20PM +0200, Pavel Machek wrote:
> > On Tue 2013-06-18 18:24:23, Gaël PORTAY wrote:
> > > Currently, none of available triggers supports playing with the LED brightness
> > > level. The cycle trigger provides a way to define custom brightness cycle.
> > > For example, it is easy to customize the cycle to mock up the rhythm of human
> > > breathing which is a nice cycle to tell the user the system is doing something.
> > >
> > > This trigger is meant to be usable for waiting an event to happen, for example
> > > when the system gets ready. Those cycles may be used to reflect well known
> > > system status (e.g. idle mode, startup...).
> > >
> > > This implementation provides several interfaces:
> > > - to define the cycle itself:
> > > * plot: definition of plot points using plot or rawplot files,
> > > each points defines the brightness level
> > > * interval: constant time interval between each plot point
> > > - to control the cycle:
> > > * repeat: the number of repetition of the whole plot cycle
> > > 0 for an infinite loop
> > > * control: used to control the cycle trigger
> > > + "start"/"stop": to start/stop the cycle
> > > + "reset" to clear the cycle counter and the internal plot point index
> > > + "pause"/"resume" to pause/resume the cycle
> > >
> > > Signed-off-by: Gaël PORTAY <g.portay@overkiz.com>
> >
> > I'd say this should go to userspace.... and maybe should handle RGB
> > leds. ... like the one on n900/HTC dream/....
> >
> > Actually, there's probably some daemon in maemo that already does
> > this.
>
> Actually the n900 has hardware support for this. There's a
> programmable LED driver on the board, which is called LP5523.
>
> So... I don't think there's a daemon in maemo ;)
Uh. It seems that LP5523 should get gcc support, not kernel
support. It has limited memory, but 3 cores, and seems turing
complete.
Not sure what is reasonable interface for that, but I guess subset
that "makes sense" is enough.
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:[~2013-06-23 9:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-18 16:24 [RFC PATCH] led: add Cycle LED trigger Gaël PORTAY
2013-06-18 22:05 ` Joe Perches
2013-06-20 9:44 ` Gaël PORTAY
2013-06-20 17:58 ` Bryan Wu
2013-06-27 13:00 ` Gaël PORTAY
2013-06-20 18:12 ` Joe Perches
2013-06-22 11:26 ` Pavel Machek
2013-06-22 16:43 ` Sebastian Reichel
2013-06-22 19:45 ` Pavel Machek
2013-06-27 13:40 ` Gaël PORTAY
2013-06-23 9:53 ` Pavel Machek [this message]
2013-06-22 19:51 ` Geert Uytterhoeven
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=20130623095305.GA3669@amd.pavel.ucw.cz \
--to=pavel@ucw.cz \
--cc=cooloney@gmail.com \
--cc=g.portay@overkiz.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=milo.kim@ti.com \
--cc=rob@landley.net \
--cc=rpurdie@rpsys.net \
/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).