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 <bjorn.andersson@linaro.org>,
Mark Brown <broonie@kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
Linux LED Subsystem <linux-leds@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v12 1/2] leds: core: Introduce LED pattern trigger
Date: Fri, 21 Sep 2018 23:04:40 +0200 [thread overview]
Message-ID: <20180921210440.GA18062@amd> (raw)
In-Reply-To: <324778a9-a32c-ae6e-337a-39845f214bfc@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2888 bytes --]
On Fri 2018-09-21 22:59:40, Jacek Anaszewski wrote:
> Hi Baolin,
>
> On 09/21/2018 05:31 AM, Baolin Wang wrote:
> > Hi Jacek and Pavel,
> >
> > On 11 September 2018 at 10:47, Baolin Wang <baolin.wang@linaro.org> wrote:
> >> This patch adds one new led trigger that LED device can configure
> >> the software or hardware pattern and trigger it.
> >>
> >> Consumers can write 'pattern' file to enable the software pattern
> >> which alters the brightness for the specified duration with one
> >> software timer.
> >>
> >> Moreover consumers can write 'hw_pattern' file to enable the hardware
> >> pattern for some LED controllers which can autonomously control
> >> brightness over time, according to some preprogrammed hardware
> >> patterns.
> >>
> >> Signed-off-by: Raphael Teysseyre <rteysseyre@gmail.com>
> >> Signed-off-by: Baolin Wang <baolin.wang@linaro.org>
> >> ---
> >> Changes from v11:
> >> - Change -1 means repeat indefinitely.
> >>
> >> Changes from v10:
> >> - Change 'int' to 'u32' for delta_t field.
> >>
> >> Changes from v9:
> >> - None.
> >>
> >> Changes from v8:
> >> - None.
> >>
> >> Changes from v7:
> >> - Move the SC27XX hardware patterns description into its own ABI file.
> >>
> >> Changes from v6:
> >> - Improve commit message.
> >> - Optimize the description of the hw_pattern file.
> >> - Simplify some logics.
> >>
> >> Changes from v5:
> >> - Add one 'hw_pattern' file for hardware patterns.
> >>
> >> Changes from v4:
> >> - Change the repeat file to return the originally written number.
> >> - Improve comments.
> >> - Fix some build warnings.
> >>
> >> Changes from v3:
> >> - Reset pattern number to 0 if user provides incorrect pattern string.
> >> - Support one pattern.
> >>
> >> Changes from v2:
> >> - Remove hardware_pattern boolen.
> >> - Chnage the pattern string format.
> >>
> >> Changes from v1:
> >> - Use ATTRIBUTE_GROUPS() to define attributes.
> >> - Introduce hardware_pattern flag to determine if software pattern
> >> or hardware pattern.
> >> - Re-implement pattern_trig_store_pattern() function.
> >> - Remove pattern_get() interface.
> >> - Improve comments.
> >> - Other small optimization.
> >> ---
> >
> > Do you have any comments for the v12 patch set? Thanks.
>
> We will probably have to remove hw_pattern from ledtrig-pattern
> since we are unable to come up with generic interface for it.
> Unless thread [0] will end up with some brilliant ideas. So far
> we're waiting for Pavel's reply.
I believe same semantics as pattern works well for hw_pattern, and
suggested code changes to make it more robust. I don't really
understand what issues you see there.
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-09-21 21:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-11 2:47 [PATCH v12 1/2] leds: core: Introduce LED pattern trigger Baolin Wang
2018-09-11 2:47 ` [PATCH v12 2/2] leds: sc27xx: Add pattern_set/clear interfaces for LED controller Baolin Wang
2018-09-21 3:31 ` [PATCH v12 1/2] leds: core: Introduce LED pattern trigger Baolin Wang
2018-09-21 20:59 ` Jacek Anaszewski
2018-09-21 21:04 ` Pavel Machek [this message]
2018-09-21 21:12 ` Pavel Machek
2018-09-21 21:17 ` Pavel Machek
2018-09-21 22:11 ` Jacek Anaszewski
2018-09-21 22:18 ` Pavel Machek
2018-09-22 3:30 ` Baolin Wang
2018-09-22 19:44 ` Pavel Machek
2018-09-23 12:25 ` Jacek Anaszewski
2018-09-25 11:15 ` Baolin Wang
2018-09-25 20:00 ` Jacek Anaszewski
2018-09-26 3:13 ` Baolin Wang
2018-09-27 21:47 ` Pavel Machek
2018-09-24 23:54 ` Bjorn Andersson
2018-09-25 11:24 ` 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=20180921210440.GA18062@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=linus.walleij@linaro.org \
--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).