From: Geert Uytterhoeven <geert@linux-m68k.org>
To: lgxue@hotmail.com
Cc: Bryan Wu <cooloney@gmail.com>, Richard Purdie <rpurdie@rpsys.net>,
Rob Landley <rob@landley.net>,
"Milo(Woogyom) Kim" <milo.kim@ti.com>,
linux-leds@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-doc@vger.kernel.org
Subject: Re: [PATCH] Add the LED burst trigger
Date: Thu, 26 Dec 2013 12:18:37 +0100 [thread overview]
Message-ID: <CAMuHMdUnOyeJ8opD9wwcS0RGJ-js+p3fXkA0iVJO1Vcri_RcbA@mail.gmail.com> (raw)
In-Reply-To: <1387895407-28031-1-git-send-email-lgxue@hotmail.com>
On Tue, Dec 24, 2013 at 3:30 PM, <lgxue@hotmail.com> wrote:
> +Three properties are exported. They are freq, times and delay_off.
> +
> + freq - the blink frequency, default value is 3 means 3HZ
Please write "3 Hz". In the kernel "HZ" means the number of jiffies per
second, and "3 HZ" thus represents a 3-second period.
> + times - burst blink times in one cycle, no default value
> + delay_off - off time between two burst blinks, default value is 500 ms
> +
> +2. Case studies
> +
> + Example 1
> +
> + echo burst > trigger
> + echo 2 > times
> +
> + The behaviour is like below:
> +
> + on(1/6s)off(1/6s)on(1/6s)off(1/6m)
> + ...off 500ms...
> + on(1/6s)off(1/6s)on(1/3s)off(1/6m)
on(1/6s)off(1/6s)on(1/6s)off(1/6s)
> + ...off 500ms
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2013-12-26 11:18 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
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 [this message]
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=CAMuHMdUnOyeJ8opD9wwcS0RGJ-js+p3fXkA0iVJO1Vcri_RcbA@mail.gmail.com \
--to=geert@linux-m68k.org \
--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).