From: Jacek Anaszewski <jacek.anaszewski@gmail.com>
To: Johan Adolfsson <Johan.Adolfsson@axis.com>,
Lee Jones <lee@kernel.org>, Pavel Machek <pavel@kernel.org>
Cc: "linux-leds@vger.kernel.org" <linux-leds@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Kernel <Kernel@axis.com>
Subject: Re: [PATCH RFC] leds: leds-lp50xx: Handle reg to get correct multi_index
Date: Mon, 12 May 2025 20:10:04 +0200 [thread overview]
Message-ID: <0bf10848-0fa2-438a-92dc-6d3b29760b64@gmail.com> (raw)
In-Reply-To: <PAWPR02MB92814A311B18A6FD8A448D249B97A@PAWPR02MB9281.eurprd02.prod.outlook.com>
On 5/12/25 12:59, Johan Adolfsson wrote:
>
> From: Jacek Anaszewski <jacek.anaszewski@gmail.com>
> Sent: Saturday, May 10, 2025 17:32
> To: Johan Adolfsson; Lee Jones; Pavel Machek
> Cc: linux-leds@vger.kernel.org; linux-kernel@vger.kernel.org; Kernel
> Subject: Re: [PATCH RFC] leds: leds-lp50xx: Handle reg to get correct multi_index
>
>> Hi Johan,
>>
>> On 5/6/25 12:39, Johan Adolfsson wrote:
>>> mc_subled used for multi_index needs well defined array indexes,
>>> to guarantee the desired result, optionally use reg for that.
>>>
>>> If devicetree child nodes is processed in random or reverse order
>>> you may end up with multi_index "blue green red" instead of the expected
>>> "red green blue".
>>> If user space apps uses multi_index to deduce how to control the leds
>>> they would most likely be broken without this patch if devicetree
>>> processing is reversed (which it appears to be).
>>
>> Are you trying to solve some real problem that occurred to you?
>
> Yes! Since the subled is indexed by the processing order, it gets reversed if devicetree processing is reversed
> (which I understand is a "feature"), so instead of "red green blue" I would get "blue green red" in the multi_index file without this patch.
> The mapping to the hardware does not match that, so writing "255 0 0" to multi_intensity will give me red and not blue.
You are expected to write intensities to the multi_intensity file
according to the order of colors listed in multi_index file.
>> The order of DT nodes parsing is not a problem here - we save
>> color index in subled_info to be able to figure out which color
>> is on which position. This information can be retrieved in sysfs
>> by reading multi_index file.
>
> Maybe the bug is somewhere else in the leds-lp50xx if that is supposed to work,
> but I still think it's a good thing to be able to get the expected order in the multi_index file.
Please make sure you read Documentation/leds/leds-class-multicolor.rst.
There is no such term as "expected order in the multi_index file".
The framework is called multicolor, not rgb. The order of colors does
not need to be RGB.
--
Best regards,
Jacek Anaszewski
next prev parent reply other threads:[~2025-05-12 18:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-06 10:39 [PATCH RFC] leds: leds-lp50xx: Handle reg to get correct multi_index Johan Adolfsson
2025-05-08 14:57 ` Lee Jones
2025-05-10 15:32 ` Jacek Anaszewski
2025-05-12 10:59 ` Johan Adolfsson
2025-05-12 18:10 ` Jacek Anaszewski [this message]
2025-05-13 13:04 ` Johan Adolfsson
2025-05-13 19:50 ` Jacek Anaszewski
2025-05-14 14:41 ` Johan Adolfsson
2025-05-13 19:52 ` Jacek Anaszewski
2025-05-14 14:34 ` Johan Adolfsson
2025-05-14 19:55 ` Jacek Anaszewski
2025-05-15 7:36 ` Johan Adolfsson
2025-05-18 15:16 ` Jacek Anaszewski
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=0bf10848-0fa2-438a-92dc-6d3b29760b64@gmail.com \
--to=jacek.anaszewski@gmail.com \
--cc=Johan.Adolfsson@axis.com \
--cc=Kernel@axis.com \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@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