[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190701151423.30768-3-jjhiblot@ti.com>
Date: Mon, 1 Jul 2019 17:14:21 +0200
From: Jean-Jacques Hiblot <jjhiblot@...com>
To: <jacek.anaszewski@...il.com>, <pavel@....cz>, <robh+dt@...nel.org>,
<mark.rutland@....com>, <lee.jones@...aro.org>,
<daniel.thompson@...aro.org>, <jingoohan1@...il.com>
CC: <dmurphy@...com>, <linux-leds@...r.kernel.org>,
<linux-kernel@...r.kernel.org>, <dri-devel@...ts.freedesktop.org>,
<tomi.valkeinen@...com>, Jean-Jacques Hiblot <jjhiblot@...com>,
<devicetree@...r.kernel.org>
Subject: [PATCH 2/4] devicetree: Update led binding
Update the led binding to describe the possibility to add a "compatible"
option to create a child-device, user of the LED.
Signed-off-by: Jean-Jacques Hiblot <jjhiblot@...com>
Cc: devicetree@...r.kernel.org
---
Documentation/devicetree/bindings/leds/common.txt | 3 +++
1 file changed, 3 insertions(+)
diff --git a/Documentation/devicetree/bindings/leds/common.txt b/Documentation/devicetree/bindings/leds/common.txt
index 70876ac11367..2f7882528d97 100644
--- a/Documentation/devicetree/bindings/leds/common.txt
+++ b/Documentation/devicetree/bindings/leds/common.txt
@@ -11,6 +11,9 @@ have to be tightly coupled with the LED device binding. They are represented
by child nodes of the parent LED device binding.
Optional properties for child nodes:
+- compatible : driver name for a child-device. This child-device is the user
+ of the LED. It is created when the LED is registered and
+ destroyed when the LED is unregistered.
- led-sources : List of device current outputs the LED is connected to. The
outputs are identified by the numbers that must be defined
in the LED device binding documentation.
--
2.17.1
Powered by blists - more mailing lists