devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexander Dahl <ada@thorsis.com>
To: Rob Herring <robh@kernel.org>
Cc: "Alexander Dahl" <post@lespocky.de>,
	linux-leds@vger.kernel.org, devicetree@vger.kernel.org,
	"Jacek Anaszewski" <jacek.anaszewski@gmail.com>,
	"Pavel Machek" <pavel@ucw.cz>, "Dan Murphy" <dmurphy@ti.com>,
	linux-kernel@vger.kernel.org,
	"Peter Ujfalusi" <peter.ujfalusi@ti.com>,
	"Marek Behún" <marek.behun@nic.cz>
Subject: Re: [PATCH v5 3/3] dt-bindings: leds: Convert pwm to yaml
Date: Tue, 29 Sep 2020 09:39:01 +0200	[thread overview]
Message-ID: <23920329.U7EUVLB22C@ada> (raw)
In-Reply-To: <20200922155747.GA2734659@bogus>

Hei hei,

Am Dienstag, 22. September 2020, 17:57:47 CEST schrieb Rob Herring:
> Use generic node names:
> 
> led-controller {
> 
> > +        compatible = "pwm-leds";
> > +
> > +        led-1 {
> > +            label = "omap4::keypad";
> > +            pwms = <&twl_pwm 0 7812500>;
> > +            max-brightness = <127>;
> > +        };
> > +
> > +        led-2 {
> > +            color = <LED_COLOR_ID_GREEN>;
> > +            function = LED_FUNCTION_CHARGING;
> > +            pwms = <&twl_pwmled 0 7812500>;
> > +            max-brightness = <255>;
> > +        };
> > +    };
> > +
> > +...

This is clear for the "one led-controller" case.  However, when trying to fix 
those node names in existing .dts files, I wondered how those should be named 
for multiple, different led-controllers, e.g. one using "pwm-leds" and another 
one using "gpio-leds"?  

See arch/arm/boot/dts/at91-kizbox3-hs.dts for example, the nodes are called 
"pwm_leds" and "leds" currently.  If both were part of a .dtsi and both named 
the same, you could not overwrite/complement those in a .dts file including 
that .dtsi due to a name conflict. 

Just append a numerical index like this?

  led-controller-1 {
    …
  };
  
  led-controller-2 {
    …
  };

Greets 
Alex




  reply	other threads:[~2020-09-29  7:39 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-19  5:31 [PATCH v5 0/3] leds: pwm: Make automatic labels work Alexander Dahl
2020-09-19  5:31 ` [PATCH v5 1/3] leds: pwm: Remove platform_data support Alexander Dahl
2020-09-19  9:44   ` Pavel Machek
2020-09-28 11:04     ` Alexander Dahl
2020-09-30 17:24       ` Pavel Machek
2020-09-30 22:57         ` Alexander Dahl
2020-09-19 18:05   ` Marek Behun
2020-09-19  5:31 ` [PATCH v5 2/3] leds: pwm: Allow automatic labels for DT based devices Alexander Dahl
2020-09-19  9:44   ` Pavel Machek
2020-09-19  5:31 ` [PATCH v5 3/3] dt-bindings: leds: Convert pwm to yaml Alexander Dahl
2020-09-22 15:42   ` Rob Herring
2020-09-28 11:19     ` Alexander Dahl
2020-09-28 16:11       ` Rob Herring
2020-09-22 15:57   ` Rob Herring
2020-09-29  7:39     ` Alexander Dahl [this message]
2020-09-29 13:58       ` 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=23920329.U7EUVLB22C@ada \
    --to=ada@thorsis.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dmurphy@ti.com \
    --cc=jacek.anaszewski@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=marek.behun@nic.cz \
    --cc=pavel@ucw.cz \
    --cc=peter.ujfalusi@ti.com \
    --cc=post@lespocky.de \
    --cc=robh@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).