From: Jacek Anaszewski <j.anaszewski@samsung.com>
To: "Kim, Milo" <milo.kim@ti.com>
Cc: robh+dt@kernel.org, lee.jones@linaro.org, broonie@kernel.org,
devicetree@vger.kernel.org, linux-leds@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 3/9] Documentation: dt-bindings: leds: add LM3633 LED binding information
Date: Mon, 07 Dec 2015 11:50:16 +0100 [thread overview]
Message-ID: <56656468.8020300@samsung.com> (raw)
In-Reply-To: <56654756.5050601@ti.com>
Hi Milo,
On 12/07/2015 09:46 AM, Kim, Milo wrote:
> Hi Jacek,
>
> On 11/30/2015 9:26 PM, Jacek Anaszewski wrote:
>> In case of LM3633 the real current outputs are banks and multiplexing
>> that occurs between banks and LVLEDn pins can be conveniently expressed
>> with the bindings I proposed above.
>>
>>> >If three output channels are controlled by one control bank, then it
>>> >should be represented as below.
>>> >
>>> >lvled-group-A {
>>> > led-sources = <0>, <1>, <2>;
>>> > led-max-microamp = <some value>;
>>> >}
>>> >
>>> >Please let me know if I misunderstand.
>> You silently assumed some definition of a "channel". led-sources means
>> in fact current sources, and when device is configured so that three
>> output pins are routed to the same current source, then in fact
>> they share common current source.
>
> Thanks for comments. I've modified 'led-sources' based on your feedback.
> Could you check updated dt-bindings below?
>
> * Updates
> - led-sources: List of current sources from 0 to 5.
> - ti,led-outputs: Output channel specifier
>
> The 'ti,led-outputs' property is exactly matched with datasheet
> description, so it's easy to understand which current source is used for
> output channels.
> ---
> 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:
> - led-sources: List of current sources from 0 to 5.
> 0: control bank C for output LED 1
> control bank C for output LED 1 and 2
> control bank C for output LED 1, 2 and 3
> 1: control bank D for output LED 2
> 2: control bank E for output LED 3
> 3: control bank F for output LED 4
> control bank F for output LED 4 and 5
> control bank F for output LED 4, 5 and 6
> 4: control bank G for output LED 5
> 5: control bank H for output LED 6
> Please refer to LED binding [2].
>
> - ti,led-outputs: Output channel specifier from 0 to 5.
> 0: LED 1
> 1: LED 2
> 2: LED 3
> 3: LED 4
> 4: LED 5
> 5: LED 6
This property is redundant. LED class driver can infer this
information by analyzing the led-sources property from each
child node.
Below arrangement:
led1 {
led-sources = <0>;
};
led2 {
led-sources = <0>;
};
led3 {
led-sources = <2>;
};
led4 {
led-sources = <3>;
};
led5 {
led-sources = <3>;
};
led6 {
led-sources = <3>;
};
suffices to discover the following:
BANKC controls LVLED1, LVLED2
BANKE controls LVLED3
BANKF controls LVLED4, LVLED5, LVLED6
> Optional properties of a child node:
> - label: LED channel identification. Please refer to LED binding [2].
> - led-max-microamp: Max current setting. Type is <u32>.
> Unit is microampere. Range is from 5000 to 29800.
> Step is 800. Please refer to LED binding [2].
>
> Examples:
>
> LED 1 is assigned for status LED. LED 4,5 and 6 are used for RGB
> indicator. RGB channels are controlled by bank F internally.
>
> leds {
> compatible = "ti,lm3633-leds";
>
> status {
> led-sources = <0>;
> led-max-microamp = <5000>;
> ti,led-outputs = <0>;
> };
>
> rgb {
> led-sources = <3>;
> led-max-microamp = <6600>;
> ti,led-outputs = <3 4 5>;
> };
> };
>
> LED 2 is power LED. LED 5 is notification LED.
>
> leds {
> compatible = "ti,lm3633-leds";
>
> lvled2 {
> label = "power";
> led-sources = <1>;
> led-max-microamp = <29000>;
> ti,led-outputs = <1>;
> };
>
> lvled5 {
> label = "noti";
> led-sources = <4>;
> led-max-microamp = <6600>;
> ti,led-outputs = <4>;
> };
> };
>
>
> [1] http://www.ti.com/product/LM3633/datasheet
> [2] ../leds/common.txt
>
> Best regards,
> Milo
>
>
--
Best Regards,
Jacek Anaszewski
next prev parent reply other threads:[~2015-12-07 10:50 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-26 6:56 [PATCH v2 0/9] Support TI LMU devices Milo Kim
2015-11-26 6:56 ` Milo Kim
2015-11-26 6:56 ` [PATCH v2 1/9] Documentation: dt-bindings: mfd: add TI LMU device binding information Milo Kim
2015-11-26 6:56 ` Milo Kim
2015-11-27 20:55 ` Rob Herring
2016-01-11 9:46 ` Lee Jones
2015-11-26 6:56 ` [PATCH v2 2/9] Documentation: dt-bindings: leds: backlight: add TI LMU backlight " Milo Kim
2015-11-26 6:56 ` Milo Kim
2016-01-11 9:53 ` Lee Jones
2015-11-26 6:56 ` [PATCH v2 3/9] Documentation: dt-bindings: leds: add LM3633 LED " Milo Kim
2015-11-26 6:56 ` Milo Kim
2015-11-27 11:19 ` Jacek Anaszewski
2015-11-30 8:19 ` Kim, Milo
2015-11-30 8:19 ` Kim, Milo
2015-11-30 12:26 ` Jacek Anaszewski
[not found] ` <565C408B.9070703-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2015-12-07 8:46 ` Kim, Milo
2015-12-07 8:46 ` Kim, Milo
2015-12-07 10:50 ` Jacek Anaszewski [this message]
2015-11-26 6:57 ` [PATCH v2 4/9] Documentation: dt-bindings: regulator: add LM363x regulator " Milo Kim
2015-11-26 6:57 ` Milo Kim
2015-11-27 12:37 ` Mark Brown
2015-11-27 20:44 ` Rob Herring
2015-11-27 22:07 ` Mark Brown
2015-11-27 12:55 ` Applied "regulator: lm363x: add LM363x regulator binding information" to the regulator tree Mark Brown
2015-11-27 20:57 ` [PATCH v2 4/9] Documentation: dt-bindings: regulator: add LM363x regulator binding information Rob Herring
2015-11-26 6:57 ` [PATCH v2 5/9] mfd: add TI LMU driver Milo Kim
2015-11-26 6:57 ` Milo Kim
2016-01-11 10:17 ` Lee Jones
2015-11-26 6:57 ` [PATCH v2 6/9] mfd: add TI LMU hardware fault monitoring driver Milo Kim
2015-11-26 6:57 ` Milo Kim
2016-01-11 10:21 ` Lee Jones
2016-01-12 3:36 ` Milo Kim
2016-01-12 3:36 ` Milo Kim
2016-01-12 7:37 ` Lee Jones
2015-11-26 6:57 ` [PATCH v2 7/9] backlight: add TI LMU backlight driver Milo Kim
2015-11-26 6:57 ` Milo Kim
2016-01-11 9:57 ` Lee Jones
2016-01-11 23:32 ` Milo Kim
2016-01-11 23:32 ` Milo Kim
2015-11-26 6:57 ` [PATCH v2 8/9] leds: add LM3633 driver Milo Kim
2015-11-26 6:57 ` Milo Kim
2015-11-27 11:19 ` Jacek Anaszewski
[not found] ` <56583C37.1050307-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2015-11-28 8:28 ` Jacek Anaszewski
2015-11-28 8:28 ` Jacek Anaszewski
2015-11-30 8:48 ` Kim, Milo
2015-11-30 8:48 ` Kim, Milo
2015-11-30 12:26 ` Jacek Anaszewski
2015-11-26 6:57 ` [PATCH v2 9/9] regulator: add LM363X driver Milo Kim
2015-11-26 6:57 ` Milo Kim
2015-11-27 12:55 ` Applied "regulator: add LM363X driver" to the regulator tree Mark Brown
2016-01-14 7:56 ` [PATCH v2 9/9] regulator: add LM363X driver Milo Kim
2016-01-14 7:56 ` Milo Kim
[not found] ` <56975493.7050900-l0cyMroinI0@public.gmane.org>
2016-01-14 10:27 ` Mark Brown
2016-01-14 10:27 ` Mark Brown
2016-01-14 23:41 ` Kim, Milo
2016-01-14 23:41 ` Kim, Milo
2016-01-06 7:20 ` [PATCH v2 0/9] Support TI LMU devices Milo Kim
2016-01-06 7:20 ` Milo Kim
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=56656468.8020300@samsung.com \
--to=j.anaszewski@samsung.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=milo.kim@ti.com \
--cc=robh+dt@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.