From: Pavel Machek <pavel@ucw.cz>
To: Jacek Anaszewski <jacek.anaszewski@gmail.com>
Cc: Baolin Wang <baolin.wang@linaro.org>,
rteysseyre@gmail.com, bjorn.andersson@linaro.org,
broonie@kernel.org, linux-leds@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 1/2] leds: core: Introduce LED pattern trigger
Date: Mon, 6 Aug 2018 00:08:30 +0200 [thread overview]
Message-ID: <20180805220829.GA3338@amd> (raw)
In-Reply-To: <3d7e8701-d92b-9f51-befa-a585b5957488@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 687 bytes --]
Hi!
> > +What: /sys/class/leds/<led>/repeat
> > +Date: August 2018
> > +KernelVersion: 4.19
> > +Description:
> > + Specify a pattern repeat number. 0 means repeat indefinitely.
>
> In current implementation this file on read returns the number
> of remaining repeat intervals. I'd add that to this description.
Lets not do this.
LEDs such as the one on N900 can do repeats automatically, in
hardware. But in such case we may not be able to determine how many
repetitions were done (and how many are left).
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2018-08-05 22:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-05 4:04 [PATCH v4 1/2] leds: core: Introduce LED pattern trigger Baolin Wang
2018-08-05 16:10 ` Jacek Anaszewski
2018-08-05 22:08 ` Pavel Machek [this message]
2018-08-06 1:53 ` Baolin Wang
2018-08-06 7:09 ` Pavel Machek
2018-08-06 7:33 ` Baolin Wang
2018-08-06 8:06 ` Pavel Machek
2018-08-06 8:31 ` Baolin Wang
2018-08-06 11:41 ` Jacek Anaszewski
2018-08-06 11:43 ` Baolin Wang
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=20180805220829.GA3338@amd \
--to=pavel@ucw.cz \
--cc=baolin.wang@linaro.org \
--cc=bjorn.andersson@linaro.org \
--cc=broonie@kernel.org \
--cc=jacek.anaszewski@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--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).