From: Pavel Machek <pavel@ucw.cz>
To: Marek Behun <marek.behun@nic.cz>
Cc: Oleh Kravchenko <oleg@kaa.org.ua>,
Jacek Anaszewski <jacek.anaszewski@gmail.com>,
linux-leds@vger.kernel.org
Subject: Re: How to synchronize leds in trigger
Date: Wed, 26 Feb 2020 15:15:57 +0100 [thread overview]
Message-ID: <20200226141557.GK4080@duo.ucw.cz> (raw)
In-Reply-To: <20200130104424.22cec119@nic.cz>
[-- Attachment #1: Type: text/plain, Size: 945 bytes --]
Hi!
> > I'm happy to invest my time to implement such functionality.
> > I think it can be really useful for LEDs array like CR0014114 <https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.5&id=b9dd69155371ebd7055c182e30423edc9104239f>.
> >
> > In few days I can publish my vision,
> > but before that could you please explain why it will took months?
> > Where it can be hard to implement?
>
> Just look at how long the API for RGB LEDs is being agreed upon. It is
> over a year already, if not longer, and still not merged.
Sorry about that.
Anyway, you have a pretty good driver with RGB support disabled, IIRC,
and it only had one tiny thing left to fix.
If you want to re-submit that, maybe we can have that for 5.7.
Best regards,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2020-02-26 14:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-27 21:51 How to synchronize leds in trigger Oleh Kravchenko
2020-01-28 19:58 ` Jacek Anaszewski
2020-01-30 7:57 ` Oleh Kravchenko
2020-01-30 9:44 ` Marek Behun
2020-01-31 16:39 ` Dan Murphy
2020-02-26 14:15 ` Pavel Machek [this message]
2020-02-26 16:50 ` Marek Behun
2020-01-30 10:37 ` Pavel Machek
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=20200226141557.GK4080@duo.ucw.cz \
--to=pavel@ucw.cz \
--cc=jacek.anaszewski@gmail.com \
--cc=linux-leds@vger.kernel.org \
--cc=marek.behun@nic.cz \
--cc=oleg@kaa.org.ua \
/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).