All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jacek Anaszewski <jacek.anaszewski@gmail.com>
To: Sven Schwermer <sven@svenschwermer.de>,
	Sven Schuchmann <schuchmann@schleissheimer.de>,
	"linux-leds@vger.kernel.org" <linux-leds@vger.kernel.org>
Cc: "pavel@ucw.cz" <pavel@ucw.cz>
Subject: Re: AW: AW: [PATCH v2 1/2] dt-bindings: leds: Add multi-color default-intensities property
Date: Wed, 11 May 2022 00:00:30 +0200	[thread overview]
Message-ID: <9209a2da-a201-d58a-3cb2-9d2ef7ae9a2b@gmail.com> (raw)
In-Reply-To: <3a016b38-57d2-e8d0-0162-734829aa0419@svenschwermer.de>

On 5/10/22 20:31, Sven Schwermer wrote:
> Hi Jacek,
> 
> On 5/8/22 21:55, Jacek Anaszewski wrote:
>> Hi Sven and Sven,
>>
>> On 5/4/22 11:24, Sven Schwermer wrote:
>>> Hi Sven,
>>>
>>> I did consider placing the property into the multicolor's sub nodes. 
>>> However, multicolor LEDs are not required to have firmware sub nodes. 
>>> At least the multicolor class API does not make any assumptions about 
>>> this.
>>
>> So this is something to be clarified. The whole idea relies on having
>> sub-nodes in the multi-led node.
> 
> As far as I understand, multi-color LEDs don't require actual OF 
> sub-nodes. The Turris Omnia LED driver doesn't have sub-nodes, see 
> Documentation/devicetree/bindings/leds/cznic,turris-omnia-leds.yaml

Ah, I forgot about that one and the related discussion.
In this case, yes, global array will do.

-- 
Best regards,
Jacek Anaszewski

  reply	other threads:[~2022-05-10 22:00 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-02 14:09 Initial multicolor LED intensities Sven Schwermer
2022-05-02 20:46 ` Pavel Machek
2022-05-03 11:04   ` [PATCH v1 1/2] dt-bindings: leds: Add multi-color default-intensities property Sven Schwermer
2022-05-03 11:04     ` [PATCH v1 2/2] leds: multicolor: Read " Sven Schwermer
2022-05-03 11:27   ` [PATCH v2 1/2] dt-bindings: leds: Add multi-color " Sven Schwermer
2022-05-03 11:27     ` [PATCH v2 2/2] leds: multicolor: Read " Sven Schwermer
2022-05-03 13:50     ` AW: [PATCH v2 1/2] dt-bindings: leds: Add multi-color " Sven Schuchmann
2022-05-03 18:58       ` Sven Schwermer
2022-05-04  7:17         ` AW: " Sven Schuchmann
2022-05-04  9:24           ` Sven Schwermer
2022-05-08 19:55             ` Jacek Anaszewski
2022-05-10 18:31               ` Sven Schwermer
2022-05-10 22:00                 ` Jacek Anaszewski [this message]
2022-05-05  9:50   ` [PATCH v3 " Sven Schwermer
2022-05-05  9:50     ` [PATCH v3 2/2] leds: multicolor: Read " Sven Schwermer
2022-05-17  0:08     ` [PATCH v3 1/2] dt-bindings: leds: Add multi-color " Rob Herring

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=9209a2da-a201-d58a-3cb2-9d2ef7ae9a2b@gmail.com \
    --to=jacek.anaszewski@gmail.com \
    --cc=linux-leds@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=schuchmann@schleissheimer.de \
    --cc=sven@svenschwermer.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.