From: Dan Murphy <dmurphy@ti.com>
To: Jacek Anaszewski <jacek.anaszewski@gmail.com>, robh+dt@kernel.org
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-leds@vger.kernel.org
Subject: Re: [PATCH 1/2] di: bindings: lm3697: Introduce the lm3697 driver
Date: Mon, 6 Aug 2018 10:32:21 -0500 [thread overview]
Message-ID: <044e6bb0-cdd0-a87f-05e8-4f56965c5fad@ti.com> (raw)
In-Reply-To: <b22bf013-f83c-12c1-90e5-8b0dc4145834@gmail.com>
Jacek
Thanks for the review
On 08/04/2018 07:22 AM, Jacek Anaszewski wrote:
> Hi Dan,
>
> Thank you for the patch.
>
> Typo in the patch title:
>
> s/di: /dt-/
>
> And maybe let's change the following text to:
>
> "Add bindings for lm3697 LED driver"
Ack to the above.
>
> Best regards,
> Jacek Anaszewski
>
> On 08/03/2018 05:02 PM, Dan Murphy wrote:
>> Introduce the device tree bindings for the lm3697
>> led driver for backlighting and display.
>>
>> Signed-off-by: Dan Murphy <dmurphy@ti.com>
>> ---
>> .../devicetree/bindings/leds/leds-lm3697.txt | 64 +++++++++++++++++++
>> 1 file changed, 64 insertions(+)
>> create mode 100644 Documentation/devicetree/bindings/leds/leds-lm3697.txt
>>
>> diff --git a/Documentation/devicetree/bindings/leds/leds-lm3697.txt b/Documentation/devicetree/bindings/leds/leds-lm3697.txt
>> new file mode 100644
>> index 000000000000..7b8e490f1ea1
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/leds/leds-lm3697.txt
>> @@ -0,0 +1,64 @@
>> +* Texas Instruments - LM3697 Highly Efficient White LED Driver
>> +
>> +The LM3697 11-bit LED driver provides high-
>> +performance backlight dimming for 1, 2, or 3 series
>> +LED strings while delivering up to 90% efficiency.
>> +
>> +This device is suitable for Display and Keypad Lighting
>> +
>> +Required properties:
>> + - compatible:
>> + "ti,lm3967"
>> + - reg : I2C slave address
>> + - #address-cells : 1
>> + - #size-cells : 0
>> + - control-bank-cfg - : Indicates which sink is connected to which control bank
>> + 0 - All HVLED outputs are controlled by bank A
>> + 1 - HVLED1 is controlled bank B, HVLED2/3 are controlled by bank A
>> + 2 - HVLED2 is controlled bank B, HVLED1/3 are controlled by bank A
>> + 3 - HVLED1/2 are controlled by bank B, HVLED3 is controlled by bank A
>> + 4 - HVLED3 is controlled by bank B, HVLED1/2 are controlled by bank A
>> + 5 - HVLED1/3 is controlled by bank B, HVLED2 is controlled by bank A
>> + 6 - (default) HVLED1 is controlled by bank A, HVLED2/3 are controlled by bank B
>> + 7 - All HVLED outputs are controlled by bank B
>> +
>> +Optional properties:
>> + - enable-gpios : gpio pin to enable/disable the device.
>> + - vled-supply : LED supply
>> +
>> +Required child properties:
>> + - reg : 0 - LED is Controlled by bank A
>> + 1 - LED is Controlled by bank B
>> +
>> +Optional child properties:
>> + - label : see Documentation/devicetree/bindings/leds/common.txt
>> + - linux,default-trigger :
>> + see Documentation/devicetree/bindings/leds/common.txt
>> +
>> +Example:
>> +
>> +led-controller@36 {
>> + compatible = "ti,lm3967";
>> + reg = <0x36>;
>> + #address-cells = <1>;
>> + #size-cells = <0>;
>> +
>> + enable-gpios = <&gpio1 28 GPIO_ACTIVE_HIGH>;
>> + vled-supply = <&vbatt>;
>> + control-bank-cfg = <0>;
>> +
>> + led@0 {
>> + reg = <0>;
>> + label = "white:first_backlight_cluster";
>> + linux,default-trigger = "backlight";
>> + };
>> +
>> + led@1 {
>> + reg = <1>;
>> + label = "white:second_backlight_cluster";
>> + linux,default-trigger = "frontlight";
>> + };
>> +}
>> +
>> +For more product information please see the link below:
>> +http://www.ti.com/lit/ds/symlink/lm3697.pdf
>>
--
------------------
Dan Murphy
prev parent reply other threads:[~2018-08-06 15:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-03 15:02 [PATCH 1/2] di: bindings: lm3697: Introduce the lm3697 driver Dan Murphy
2018-08-03 15:02 ` [PATCH 2/2] leds: " Dan Murphy
2018-08-04 12:14 ` Jacek Anaszewski
2018-08-06 15:31 ` Dan Murphy
2018-08-04 12:18 ` [PATCH 1/2] di: bindings: " Jacek Anaszewski
2018-08-04 12:22 ` Jacek Anaszewski
2018-08-06 15:32 ` Dan Murphy [this message]
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=044e6bb0-cdd0-a87f-05e8-4f56965c5fad@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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox