From: Pavel Machek <pavel@ucw.cz>
To: Joe Xue <lgxue@hotmail.com>
Cc: "cooloney@gmail.com" <cooloney@gmail.com>,
"rpurdie@rpsys.net" <rpurdie@rpsys.net>,
"rob@landley.net" <rob@landley.net>,
"milo.kim@ti.com" <milo.kim@ti.com>,
"linux-leds@vger.kernel.org" <linux-leds@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>
Subject: Re: [PATCH] Add the LED burst trigger
Date: Sat, 28 Dec 2013 11:16:22 +0100 [thread overview]
Message-ID: <20131228101622.GA13564@amd.pavel.ucw.cz> (raw)
In-Reply-To: <BLU172-W8D850A8DEA8C0D87FBF45ACCC0@phx.gbl>
Hi!
> Good idea.
> I have finished but I'll change it to this way soon and test it in next some days.
>
> What the idea about the character to indicate stop?
>
> I mean this patten maybe indicate just once maybe indicate repeatedly until the next patten.
>
> What about "/"?
> If there is a "/" at end then stop it else repeat it?
Actually, I'd put a do_repeat attribute somewhere instead of using
magic character for automatic repeats.
And while " " for pause and "#" for light would work. Maybe we chould
do "\0" for pause and "\177" for light... and interpret everything
between as an intensity. That will make it useful for LEDs with
variable intensites, too...
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:[~2013-12-28 10:16 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-24 14:30 [PATCH] Add the LED burst trigger lgxue
2013-12-25 23:09 ` Pavel Machek
2013-12-26 1:02 ` Joe Xue
2013-12-26 14:26 ` Pavel Machek
2013-12-26 15:02 ` Joe Xue
2013-12-26 16:58 ` Joe Xue
2013-12-27 12:39 ` Rob Landley
2013-12-27 13:05 ` Pavel Machek
2013-12-27 0:31 ` Joe Xue
2013-12-27 9:57 ` Pavel Machek
2013-12-28 2:08 ` Joe Xue
2013-12-28 10:16 ` Pavel Machek [this message]
2013-12-28 13:39 ` Joe Xue
2013-12-28 19:26 ` Pavel Machek
2013-12-29 0:23 ` Joe Xue
2013-12-29 10:58 ` Pavel Machek
2013-12-28 18:51 ` Geert Uytterhoeven
2013-12-28 19:29 ` how to represent sequence of brightnesses in /sys (was Re: [PATCH] Add the LED burst trigger) Pavel Machek
2013-12-28 19:34 ` Geert Uytterhoeven
2013-12-28 21:25 ` Pavel Machek
2013-12-28 21:50 ` Greg KH
2013-12-28 23:50 ` Pavel Machek
2013-12-29 1:43 ` Greg KH
2013-12-29 11:21 ` Pavel Machek
2014-01-03 0:16 ` Bryan Wu
2014-01-06 0:37 ` Pavel Machek
2013-12-27 12:33 ` [PATCH] Add the LED burst trigger Geert Uytterhoeven
2013-12-27 11:57 ` One Thousand Gnomes
2013-12-27 12:57 ` Pavel Machek
2013-12-27 14:18 ` One Thousand Gnomes
2013-12-27 15:23 ` Pavel Machek
2013-12-27 18:13 ` One Thousand Gnomes
2013-12-27 18:34 ` Geert Uytterhoeven
2013-12-27 19:37 ` Pavel Machek
2013-12-27 22:45 ` Richard Purdie
2013-12-26 11:18 ` Geert Uytterhoeven
2013-12-30 0:15 ` Joe Xue
-- strict thread matches above, loose matches on Subject: below --
2013-12-26 16:01 lgxue
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=20131228101622.GA13564@amd.pavel.ucw.cz \
--to=pavel@ucw.cz \
--cc=cooloney@gmail.com \
--cc=lgxue@hotmail.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).