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 v2] leds: Add arbitrary pattern trigger
Date: Fri, 20 Mar 2015 22:05:49 +0100 [thread overview]
Message-ID: <20150320210549.GA10475@amd> (raw)
In-Reply-To: <CAK5ve-L7zLZ=L-3U12y65VD_Xv=mDC8YuJp+Nix7SfzRxCb7MQ@mail.gmail.com>
Hi!
> > Add a new led trigger supporting arbitrary patterns.
> > This is useful for embedded systems with no screen or network access.
> >
> > Export two sysfs attributes: "pattern", and "repeat".
> >
> > When "repeat"=-1, repeat the pattern indefinitely. Otherwise,
> > repeat it the specified number of times. "pattern" specifies
> > the pattern as comma separated couples of "brightness duration"
> > values. See detailled documentation in patch.
> >
>
> Thanks for pushing this. But as we discussed in previous patches
> provided by Joe Xue, we won't merge this kind of complex trigger patch
> into kernel. I think we need to think about a new LED API to user
> space and make it easier to handle.
So, how do you propose to control intelligent LED controllers, such as
the one in N900? This pattern engine quite nicely matches the stuff
hardware can do.
And for a cell phone, it is quite important to be able to use the
hardware LED pattern engine, to save power. (And so that the LED keeps
working while machine is suspended -- important for Android phones).
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
prev parent reply other threads:[~2015-03-20 21:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-20 14:42 [PATCH v2] leds: Add arbitrary pattern trigger Raphaël Teysseyre
2015-03-20 20:42 ` Bryan Wu
2015-03-20 21:05 ` Pavel Machek [this message]
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=20150320210549.GA10475@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).