From: Oleh Kravchenko <oleg@kaa.org.ua>
To: Jacek Anaszewski <jacek.anaszewski@gmail.com>,
linux-leds@vger.kernel.org
Subject: Re: How to synchronize leds in trigger
Date: Thu, 30 Jan 2020 09:57:08 +0200 [thread overview]
Message-ID: <54c07894-f302-fe1e-9f03-aa30ea1abca1@kaa.org.ua> (raw)
In-Reply-To: <d44bcd3c-bc6f-9168-bfbd-c71469d5e771@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 953 bytes --]
Hello Jacek,
On 28.01.20 21:58, Jacek Anaszewski wrote:
> Currently LED framework does not support that.
> We would need a global pattern trigger, that would allow registering
> a set of LEDs for events firing at different time slots.
>
> It is feasible, but it would take months to agree upon interface
> and implementation. The question is whether it wouldn't be an overkill.
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?
> What prevents you from solving this problem in userspace?
User-space don't fast enough to provide correct timings.
--
Best regards,
Oleh Kravchenko
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-01-30 7:57 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 [this message]
2020-01-30 9:44 ` Marek Behun
2020-01-31 16:39 ` Dan Murphy
2020-02-26 14:15 ` Pavel Machek
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=54c07894-f302-fe1e-9f03-aa30ea1abca1@kaa.org.ua \
--to=oleg@kaa.org.ua \
--cc=jacek.anaszewski@gmail.com \
--cc=linux-leds@vger.kernel.org \
/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).