From: Jacek Anaszewski <jacek.anaszewski@gmail.com>
To: Sven Schuchmann <schuchmann@schleissheimer.de>,
Pavel Machek <pavel@ucw.cz>
Cc: Dan Murphy <dmurphy@ti.com>, Rob Herring <robh+dt@kernel.org>,
"linux-leds@vger.kernel.org" <linux-leds@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: AW: [PATCH v2 1/4] leds: lp50xx: add setting of default intensity from DT
Date: Sat, 6 Feb 2021 21:58:39 +0100 [thread overview]
Message-ID: <d5631e35-cd62-106f-2ec4-de3163367bc0@gmail.com> (raw)
In-Reply-To: <DB8P190MB06344FAD6492E56D28A4E916D9B19@DB8P190MB0634.EURP190.PROD.OUTLOOK.COM>
Sven,
On 2/6/21 2:14 PM, Sven Schuchmann wrote:
> Hello Dan,
>
>> Von: Jacek Anaszewski <jacek.anaszewski@gmail.com>
>> Gesendet: Freitag, 5. Februar 2021 19:37
>> Hi Pavel,
>>
>> On 2/5/21 11:23 AM, Pavel Machek wrote:
>>> Hi!
>>>
>>>>>> patternProperties:
>>>>>> "(^led-[0-9a-f]$|led)":
>>>>>> @@ -99,6 +104,7 @@ examples:
>>>>>> reg = <0x1>;
>>>>>> color = <LED_COLOR_ID_RGB>;
>>>>>> function = LED_FUNCTION_CHARGING;
>>>>>> + default-intensity = <100 0 0>;
>>
>> How will you know which array position is for which child LED?
>> I presume DT child nodes are not guaranteed to be parsed in the order
>> of declaration?
>
> I tried to fiddle this out, but it seems Jacek is right over here.
> The multi-led definition looks like this (from the documentation leds-lp50xx.yaml)
>
> multi-led@1 {
> #address-cells = <1>;
> #size-cells = <0>;
> reg = <0x1>;
> color = <LED_COLOR_ID_RGB>;
> function = LED_FUNCTION_CHARGING;
>
> led-0 {
> color = <LED_COLOR_ID_RED>;
> };
>
> led-1 {
> color = <LED_COLOR_ID_GREEN>;
> };
>
> led-2 {
> color = <LED_COLOR_ID_BLUE>;
> };
> };
>
> But it seems that the color definition of each led is ignored.
> By ignored I mean the driver does not take care which color
> is at which position. So if I change led-0 to be LED_COLOR_ID_BLUE
> and led-2 to be LED_COLOR_ID_RED nothing will change if I write
> from userspace. Could you help to clarify?
> Then it is even hard to know which led to set with default-intensity.
See Documentation/ABI/testing/sysfs-class-led-multicolor and
documentation of multi_index and multi_intensity files.
It is the multi_index file that tells what is the order of colors
in the multi_intensity file.
And that depends on the order of enumeration of the nodes by DT parser.
> Also it seems that the enumeration of the multi-leds should
> start with multi-led@0 (and not 1 as in the documentation).
The @unit-address part of node name must match the first address
specified in the reg property of the node, so this is correct.
--
Best regards,
Jacek Anaszewski
prev parent reply other threads:[~2021-02-06 20:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-04 14:37 [PATCH v2 1/4] leds: lp50xx: add setting of default intensity from DT Sven Schuchmann
2021-02-04 14:52 ` Pavel Machek
2021-02-05 9:57 ` AW: " Sven Schuchmann
2021-02-05 10:23 ` Pavel Machek
2021-02-05 18:37 ` Jacek Anaszewski
2021-02-06 13:14 ` AW: " Sven Schuchmann
2021-02-06 20:58 ` Jacek Anaszewski [this message]
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=d5631e35-cd62-106f-2ec4-de3163367bc0@gmail.com \
--to=jacek.anaszewski@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=dmurphy@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=robh+dt@kernel.org \
--cc=schuchmann@schleissheimer.de \
/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).