From: Rob Herring <robh@kernel.org> To: Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com> Cc: mazziesaccount@gmail.com, Jacek Anaszewski <jacek.anaszewski@gmail.com>, Pavel Machek <pavel@ucw.cz>, Dan Murphy <dmurphy@ti.com>, Mark Rutland <mark.rutland@arm.com>, linux-leds@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [RFC PATCH 2/5] dt-bindings: an30259a: example for using fixed LED node names. Date: Tue, 5 Nov 2019 21:42:06 -0600 Message-ID: <20191106034206.GA6299@bogus> (raw) In-Reply-To: <5b9f9e7cd3dc959962fc43d27e471245e63f5f29.1572351774.git.matti.vaittinen@fi.rohmeurope.com> On Tue, Oct 29, 2019 at 02:47:26PM +0200, Matti Vaittinen wrote: > Use predefined LED node name to match the LED node in driver. > > It would be nice to offload common LED property parsing to > LED core driver. One of the key things to allow this is somehow > 'pair' the LED DT node with LED driver initialization data. > > This patch uses LED node name as a 'key' in a same fashion > as regulators do. The an30259a was selected as demonstration > example and this change may not be really feasible for an30259a > as I have no idea whether the existing DTs for devices out there > have specific node names (or can be changed). This servers just > as an example to initiate discussion as to how we could pair the > driver data and DT node. > > Signed-off-by: Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com> > --- > Documentation/devicetree/bindings/leds/leds-an30259a.txt | 9 +++++---- > 1 file changed, 5 insertions(+), 4 deletions(-) > > diff --git a/Documentation/devicetree/bindings/leds/leds-an30259a.txt b/Documentation/devicetree/bindings/leds/leds-an30259a.txt > index cbd833906b2b..bd1a2d11a0ad 100644 > --- a/Documentation/devicetree/bindings/leds/leds-an30259a.txt > +++ b/Documentation/devicetree/bindings/leds/leds-an30259a.txt > @@ -9,7 +9,8 @@ Required properties: > - #address-cells: Must be 1. > - #size-cells: Must be 0. > > -Each LED is represented as a sub-node of the panasonic,an30259a node. > +Each LED is represented as a sub-node of the panasonic,an30259a node. LED nodes > +must be named as led1 led2 and led3. > > Required sub-node properties: > - reg: Pin that the LED is connected to. Must be 1, 2, or 3. > @@ -34,20 +35,20 @@ led-controller@30 { > #address-cells = <1>; > #size-cells = <0>; > > - led@1 { > + led1 { > reg = <1>; This is wrong. reg requires a unit-address and vice-versa. > linux,default-trigger = "heartbeat"; > function = LED_FUNCTION_INDICATOR; > color = <LED_COLOR_ID_RED>; > }; > > - led@2 { > + led2 { > reg = <2>; > function = LED_FUNCTION_INDICATOR; > color = <LED_COLOR_ID_GREEN>; > }; > > - led@3 { > + led3 { > reg = <3>; > function = LED_FUNCTION_INDICATOR; > color = <LED_COLOR_ID_BLUE>; > -- > 2.21.0 > > > -- > Matti Vaittinen, Linux device drivers > ROHM Semiconductors, Finland SWDC > Kiviharjunlenkki 1E > 90220 OULU > FINLAND > > ~~~ "I don't think so," said Rene Descartes. Just then he vanished ~~~ > Simon says - in Latin please. > ~~~ "non cogito me" dixit Rene Descarte, deinde evanescavit ~~~ > Thanks to Simon Glass for the translation =]
next prev parent reply index Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-10-29 12:46 [RFC PATCH 0/5] leds: Add DT node finding and parsing to core Matti Vaittinen 2019-10-29 12:46 ` [RFC PATCH 1/5] leds: Add common LED binding parsing support to LED class/core Matti Vaittinen 2019-10-29 12:47 ` [RFC PATCH 2/5] dt-bindings: an30259a: example for using fixed LED node names Matti Vaittinen 2019-11-06 3:42 ` Rob Herring [this message] 2019-11-06 11:30 ` SPAM (R/EU IT) // " Vaittinen, Matti 2019-10-29 12:47 ` [RFC PATCH 3/5] leds: an30259a: Offload DT node locating and parsing to core Matti Vaittinen 2019-10-29 12:48 ` [RFC PATCH 4/5] dt-bindings: lm3692x: example for using fixed LED node names Matti Vaittinen 2019-10-29 12:48 ` [RFC PATCH 5/5] leds: lm3692x: Offload DT node locating and parsing to core Matti Vaittinen 2019-11-18 9:21 ` [RFC PATCH 0/5] leds: Add DT node finding " Enrico Weigelt, metux IT consult 2019-11-18 10:38 ` Vaittinen, Matti 2019-11-19 19:52 ` Enrico Weigelt, metux IT consult 2019-11-20 7:37 ` Vaittinen, Matti 2020-02-09 22:46 ` Pavel Machek
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=20191106034206.GA6299@bogus \ --to=robh@kernel.org \ --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=mark.rutland@arm.com \ --cc=matti.vaittinen@fi.rohmeurope.com \ --cc=mazziesaccount@gmail.com \ --cc=pavel@ucw.cz \ /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
Linux-LEDs Archive on lore.kernel.org Archives are clonable: git clone --mirror https://lore.kernel.org/linux-leds/0 linux-leds/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 linux-leds linux-leds/ https://lore.kernel.org/linux-leds \ linux-leds@vger.kernel.org public-inbox-index linux-leds Example config snippet for mirrors Newsgroup available over NNTP: nntp://nntp.lore.kernel.org/org.kernel.vger.linux-leds AGPL code for this site: git clone https://public-inbox.org/public-inbox.git