From: "Kim, Milo" <milo.kim@ti.com>
To: Rob Herring <robh@kernel.org>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Lee Jones <lee.jones@linaro.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Jacek Anaszewski <j.anaszewski@samsung.com>,
Linux LED Subsystem <linux-leds@vger.kernel.org>
Subject: Re: [PATCH 04/16] Documentation: dt-bindings: leds: add LM3633 LED binding information
Date: Tue, 3 Nov 2015 16:05:01 +0900 [thread overview]
Message-ID: <56385C9D.8080400@ti.com> (raw)
In-Reply-To: <CAL_Jsq+rsScGf3L0Qx+NreMpSPDNoxkYL4qeC+QCwe1F8KoRPA@mail.gmail.com>
Hi Rob,
On 11/2/2015 11:53 PM, Rob Herring wrote:
> On Sun, Nov 1, 2015 at 11:01 PM, Milo Kim <milo.kim@ti.com> wrote:
>> LM3633 LED device is one of TI LMU device list.
>>
>> Cc: devicetree@vger.kernel.org
>> Cc: Jacek Anaszewski <j.anaszewski@samsung.com>
>> Cc: Lee Jones <lee.jones@linaro.org>
>> Cc: linux-kernel@vger.kernel.org
>> Cc: linux-leds@vger.kernel.org
>> Signed-off-by: Milo Kim <milo.kim@ti.com>
>> ---
>> .../devicetree/bindings/leds/leds-lm3633.txt | 28 ++++++++++++++++++++++
>> 1 file changed, 28 insertions(+)
>> create mode 100644 Documentation/devicetree/bindings/leds/leds-lm3633.txt
>>
>> diff --git a/Documentation/devicetree/bindings/leds/leds-lm3633.txt b/Documentation/devicetree/bindings/leds/leds-lm3633.txt
>> new file mode 100644
>> index 0000000..bb7f213
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/leds/leds-lm3633.txt
>> @@ -0,0 +1,28 @@
>> +TI LMU LM3633 LED device tree bindings
>> +
>> +Required properties:
>> + - compatible: "ti,lm3633-leds"
>> +
>> +Child nodes:
>> + Each node matches with LED control bank.
>> + Please refer to the datasheet [1].
>> +
>> + Required properties of a child node:
>> + - lvled1-used, lvled2-used, lvled3-used,
>> + lvled4-used, lvled5-used, lvled6-used:
>> + Low voltage LED string configuration. Type is <boolean>.
>> + Please describe which output LED string is used.
>
> What is "LED string"?
Let me replace these properties with 'led-sources'.
>
> We have properties for which LED driver/channel of the parent to use
> and "status" can be used to disable child nodes.
>
>> +
>> + Optional properties of a child node:
>> + - channel-name: Name string for LED channel identification
>> + It is used for creating LED sysfs,
>> + /sys/class/leds/<channel-name>/.
>> + If this property is empty, then default name is set to
>> + "indicator:<id>" by the driver.
>
> I believe "label" already provides this function.
>
Yep, got it. Thanks!
Best regards,
Milo
next prev parent reply other threads:[~2015-11-03 7:05 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-02 5:01 [PATCH 00/16] Support TI LMU devices Milo Kim
2015-11-02 5:01 ` Milo Kim
2015-11-02 5:01 ` [PATCH 01/16] Documentation: dt-bindings: mfd: add TI LMU device binding information Milo Kim
2015-11-02 5:01 ` Milo Kim
2015-11-02 5:01 ` [PATCH 02/16] Documentation: dt-bindings: backlight: add TI LMU backlight " Milo Kim
2015-11-02 5:01 ` Milo Kim
2015-11-02 5:01 ` [PATCH 03/16] Documentation: dt-bindings: hwmon: add TI LMU HWMON " Milo Kim
2015-11-02 5:01 ` Milo Kim
2015-11-02 5:01 ` [PATCH 04/16] Documentation: dt-bindings: leds: add LM3633 LED " Milo Kim
2015-11-02 5:01 ` Milo Kim
2015-11-02 5:01 ` [PATCH 05/16] Documentation: dt-bindings: regulator: add LM363x regulator " Milo Kim
2015-11-02 5:01 ` Milo Kim
2015-11-02 5:01 ` [PATCH 06/16] mfd: add TI LMU driver Milo Kim
2015-11-02 5:01 ` Milo Kim
2015-11-02 5:01 ` [PATCH 07/16] backlight: add TI LMU backlight common driver Milo Kim
2015-11-02 5:01 ` Milo Kim
2015-11-02 5:01 ` [PATCH 08/16] backlight: ti-lmu-backlight: add LM3532 driver Milo Kim
2015-11-02 5:01 ` Milo Kim
2015-11-02 5:01 ` [PATCH 09/16] backlight: ti-lmu-backlight: add LM3631 driver Milo Kim
2015-11-02 5:01 ` Milo Kim
2015-11-02 5:01 ` [PATCH 10/16] backlight: ti-lmu-backlight: add LM3632 driver Milo Kim
2015-11-02 5:01 ` Milo Kim
[not found] ` <1446440483-6948-11-git-send-email-milo.kim-l0cyMroinI0@public.gmane.org>
2015-11-02 5:01 ` [PATCH 11/16] backlight: ti-lmu-backlight: add LM3633 driver Milo Kim
2015-11-02 5:01 ` Milo Kim
2015-11-02 5:01 ` [PATCH 12/16] backlight: ti-lmu-backlight: add LM3695 driver Milo Kim
2015-11-02 5:01 ` Milo Kim
2015-11-02 5:01 ` [PATCH 13/16] backlight: ti-lmu-backlight: add LM3697 driver Milo Kim
2015-11-02 5:01 ` Milo Kim
2015-11-02 5:01 ` [PATCH 14/16] hwmon: add TI LMU hardware fault monitoring driver Milo Kim
2015-11-02 5:01 ` Milo Kim
2015-11-02 5:01 ` [PATCH 15/16] leds: add LM3633 driver Milo Kim
2015-11-02 5:01 ` Milo Kim
2015-11-02 5:01 ` [PATCH 16/16] regulator: add LM363X driver Milo Kim
2015-11-02 5:01 ` Milo Kim
[not found] ` <1446440483-6948-5-git-send-email-milo.kim-l0cyMroinI0@public.gmane.org>
2015-11-02 14:53 ` [PATCH 04/16] Documentation: dt-bindings: leds: add LM3633 LED binding information Rob Herring
2015-11-02 14:53 ` Rob Herring
2015-11-03 7:05 ` Kim, Milo [this message]
[not found] ` <1446440483-6948-1-git-send-email-milo.kim-l0cyMroinI0@public.gmane.org>
2015-11-02 5:32 ` [PATCH 00/16] Support TI LMU devices Kim, Milo
2015-11-02 5:32 ` Kim, Milo
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=56385C9D.8080400@ti.com \
--to=milo.kim@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=j.anaszewski@samsung.com \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.