From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dan Murphy Subject: Re: [PATCH 2/4] devicetree: Update led binding Date: Mon, 1 Jul 2019 10:20:57 -0500 Message-ID: <837afe49-18f3-722e-aa63-7d47d3a8bea0@ti.com> References: <20190701151423.30768-1-jjhiblot@ti.com> <20190701151423.30768-3-jjhiblot@ti.com> Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20190701151423.30768-3-jjhiblot@ti.com> Content-Language: en-US Sender: linux-kernel-owner@vger.kernel.org To: Jean-Jacques Hiblot , jacek.anaszewski@gmail.com, pavel@ucw.cz, robh+dt@kernel.org, mark.rutland@arm.com, lee.jones@linaro.org, daniel.thompson@linaro.org, jingoohan1@gmail.com Cc: linux-leds@vger.kernel.org, linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org, tomi.valkeinen@ti.com, devicetree@vger.kernel.org List-Id: devicetree@vger.kernel.org JJ On 7/1/19 10:14 AM, Jean-Jacques Hiblot wrote: > 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 > Cc: devicetree@vger.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. Can you update the example to show usage? Dan > - 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.