mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dan Murphy <dmurphy@ti.com>
To: <robh+dt@kernel.org>, <mark.rutland@arm.com>, <rpurdie@rpsys.net>,
	<jacek.anaszewski@gmail.com>, <pavel@ucw.cz>
Cc: <devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<linux-leds@vger.kernel.org>, Dan Murphy <dmurphy@ti.com>
Subject: [PATCH v2 2/6] dt: bindings: lp8860: Update DT label binding
Date: Tue, 5 Dec 2017 14:43:23 -0600	[thread overview]
Message-ID: <20171205204327.12111-3-dmurphy@ti.com> (raw)
In-Reply-To: <20171205204327.12111-1-dmurphy@ti.com>

Update the lp8860 label binding to the LED
standard as documented in

Documentation/devicetree/bindings/leds/common.txt

Signed-off-by: Dan Murphy <dmurphy@ti.com>
---

v2 - Added reg to child node and made it required

 Documentation/devicetree/bindings/leds/leds-lp8860.txt | 12 ++++++++++--
 1 file changed, 10 insertions(+), 2 deletions(-)

diff --git a/Documentation/devicetree/bindings/leds/leds-lp8860.txt b/Documentation/devicetree/bindings/leds/leds-lp8860.txt
index 1b2fab05ec6a..22b594d95162 100644
--- a/Documentation/devicetree/bindings/leds/leds-lp8860.txt
+++ b/Documentation/devicetree/bindings/leds/leds-lp8860.txt
@@ -9,7 +9,6 @@ Required properties:
 	- compatible :
 		"ti,lp8860"
 	- reg : I2C slave address
-	- label : Used for naming LEDs
 	- #address-cells : 1
 	- #size-cells : 0
 
@@ -17,6 +16,12 @@ Optional properties:
 	- enable-gpios : gpio pin to enable/disable the device.
 	- supply : "vled" - LED supply
 
+Required child properties:
+	- reg : 0
+
+Optional child properties:
+	- label : see Documentation/devicetree/bindings/leds/common.txt
+
 Example:
 
 	lp8860@2d {
@@ -24,9 +29,12 @@ Example:
 		#address-cells: 1
 		#size-cells: 0
 		reg = <0x2d>;
-		label = "display_cluster";
 		enable-gpios = <&gpio1 28 GPIO_ACTIVE_HIGH>;
 		vled-supply = <&vbatt>;
+		display_cluster: display_cluster@0 {
+			reg=<0>;
+			label = "display_cluster";
+		};
 	}
 
 For more product information please see the link below:
-- 
2.15.0.124.g7668cbc60

  parent reply	other threads:[~2017-12-05 20:44 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-05 20:43 [PATCH v2 0/6] Updated lp8860 led driver Dan Murphy
2017-12-05 20:43 ` [PATCH v2 1/6] dt: bindings: lp8860: Update bindings for lp8860 Dan Murphy
2017-12-07 22:42   ` Rob Herring
2017-12-07 23:07     ` Dan Murphy
2017-12-07 22:43   ` Rob Herring
2017-12-07 23:08     ` Dan Murphy
2017-12-05 20:43 ` Dan Murphy [this message]
2017-12-07 22:45   ` [PATCH v2 2/6] dt: bindings: lp8860: Update DT label binding Rob Herring
2017-12-07 23:09     ` Dan Murphy
2017-12-05 20:43 ` [PATCH v2 3/6] leds: lp8860: Update the dt parsing for LED labeling Dan Murphy
2017-12-05 20:43 ` [PATCH v2 4/6] dt: bindings: lp8860: Add trigger binding to the lp8860 Dan Murphy
2017-12-07 22:46   ` Rob Herring
2017-12-05 20:43 ` [PATCH v2 5/6] leds: lp8860: Add DT parsing to retrieve the trigger node Dan Murphy
2017-12-05 20:43 ` [PATCH v2 6/6] leds: lp8860: Various fixes to align with LED framework Dan Murphy

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=20171205204327.12111-3-dmurphy@ti.com \
    --to=dmurphy@ti.com \
    --cc=devicetree@vger.kernel.org \
    --cc=jacek.anaszewski@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=pavel@ucw.cz \
    --cc=robh+dt@kernel.org \
    --cc=rpurdie@rpsys.net \
    /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

Powered by JetHome