From: Pavel Machek <pavel@ucw.cz>
To: Arseniy Krasnov <AVKrasnov@sberdevices.ru>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-leds@vger.kernel.org" <linux-leds@vger.kernel.org>,
kernel <kernel@sberdevices.ru>
Subject: Re: [RFC PATCH v1 1/1] leds: support to use own workqueue for each LED
Date: Sun, 30 Oct 2022 21:15:27 +0100 [thread overview]
Message-ID: <20221030201527.GA23195@duo.ucw.cz> (raw)
In-Reply-To: <b7304844-a654-2120-2159-29f6134dbadb@sberdevices.ru>
[-- Attachment #1: Type: text/plain, Size: 1007 bytes --]
Hi!
> >> This allows to set own workqueue for each LED. This may be useful, because
> >> default 'system_wq' does not guarantee execution order of each work_struct,
> >> thus for several brightness update requests (for multiple leds), real
> >> brightness switch could be in random order.
> >
> > So.. what?
> >
> > Even if execution order is switched, human eye will not be able to
> > tell the difference.
> Hello,
>
> Problem arises on one of our boards where we have 14 triples of leds(each
> triple contains R G B). Test case is to play complex animation on all leds:
> smooth switch from on RGB state to another. Sometimes there are glitches in
> this process - divergence from expectable RGB state. We fixed this by using
> ordered workqueue.
Are there other solutions possible? Like batch and always apply _all_
the updates you have queued from your the worker code?
Best regards,
Pavel
--
People of Russia, stop Putin before his war on Ukraine escalates.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2022-10-30 20:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-30 6:04 [RFC PATCH v1 0/1] Support " Arseniy Krasnov
2022-10-30 6:07 ` [RFC PATCH v1 1/1] leds: support " Arseniy Krasnov
2022-10-30 12:20 ` Pavel Machek
2022-10-30 14:01 ` Arseniy Krasnov
2022-10-30 20:15 ` Pavel Machek [this message]
2022-10-31 7:01 ` Arseniy Krasnov
2022-10-31 14:47 ` Dmitry Rokosov
2022-11-09 18:01 ` Dmitry Rokosov
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=20221030201527.GA23195@duo.ucw.cz \
--to=pavel@ucw.cz \
--cc=AVKrasnov@sberdevices.ru \
--cc=kernel@sberdevices.ru \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®