From: Jacek Anaszewski <jacek.anaszewski@gmail.com>
To: Pavel Machek <pavel@ucw.cz>, Dan Murphy <dmurphy@ti.com>
Cc: robh+dt@kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-leds@vger.kernel.org
Subject: Re: [PATCH v5 1/2] dt-bindings: leds: Add bindings for lm3697 driver
Date: Fri, 24 Aug 2018 21:32:31 +0200 [thread overview]
Message-ID: <e868002d-be40-4049-ab0f-16c4a7b47c89@gmail.com> (raw)
In-Reply-To: <20180824095515.GB4045@amd>
Hi Pavel,
On 08/24/2018 11:55 AM, Pavel Machek wrote:
> On Fri 2018-08-17 10:15:27, Dan Murphy wrote:
>> Add the device tree bindings for the lm3697
>> LED driver for backlighting and display.
>>
>> Signed-off-by: Dan Murphy <dmurphy@ti.com>
>
> Acked-by: Pavel Machek <pavel@ucw.cz>
>
> Some nits are below.
>
>> +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.
>
> LED core is 8-bit only...
That's not true since this commit:
commit 1bd465e6b0e2b559db47420fea686507a01cfab0
Author: Guennadi Liakhovetski <lg@denx.de>
Date: Sat Jan 10 18:54:39 2009 +0000
leds: allow led-drivers to use a variable range of brightness values
This patch allows drivers to override the default maximum brightness
value
of 255. We take care to preserve backwards-compatibility as much as
possible, so that user-space ABI doesn't change for existing drivers.
LED trigger code has also been updated to use the per-LED maximum.
Signed-off-by: Guennadi Liakhovetski <lg@denx.de>
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
but I missed that max_brightness is not initialized in the driver,
so the core will set it to LED_FULL (255) anyway.
> so full dynamic range can not be currently
> used in linux -- right? Is there any plan to change/fix that?
>
>> +This device is suitable for Display and Keypad Lighting
>
> "display and keypad lighting."
>
>> +Optional properties:
>> + - enable-gpios : gpio pin to enable/disable the device.
>
> Remove "." at end of sentence, for consistency. "GPIO"?
>
>> +All HVLED strings controlled by control bank A
>
> ":"?
>
>> +led-controller@36 {
>> + compatible = "ti,lm3967";
>> + reg = <0x36>;
>> + #address-cells = <1>;
>> + #size-cells = <0>;
>> +
>> + enable-gpios = <&gpio1 28 GPIO_ACTIVE_HIGH>;
>> + vled-supply = <&vbatt>;
>> +
>> + led@0 {
>> + reg = <0>;
>> + led-sources = <1 1 1>;
>> + label = "white:backlight_cluster";
>> + linux,default-trigger = "backlight";
>> + };
>> +}
>> +
>> +For more product information please see the link below:
>> +http://www.ti.com/lit/ds/symlink/lm3697.pdf
>
--
Best regards,
Jacek Anaszewski
next prev parent reply other threads:[~2018-08-24 19:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-17 15:15 [PATCH v5 1/2] dt-bindings: leds: Add bindings for lm3697 driver Dan Murphy
2018-08-17 15:15 ` [PATCH v5 2/2] leds: lm3697: Introduce the " Dan Murphy
2018-08-24 10:05 ` Pavel Machek
2018-08-24 11:58 ` Dan Murphy
2018-08-24 19:33 ` Jacek Anaszewski
2018-09-05 18:18 ` Dan Murphy
2018-08-20 17:57 ` [PATCH v5 1/2] dt-bindings: leds: Add bindings for " Rob Herring
2018-08-24 9:55 ` Pavel Machek
2018-08-24 19:32 ` Jacek Anaszewski [this message]
2018-09-05 18:21 ` Dan Murphy
2018-09-07 7:45 ` Pavel Machek
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=e868002d-be40-4049-ab0f-16c4a7b47c89@gmail.com \
--to=jacek.anaszewski@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=dmurphy@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@ucw.cz \
--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;
as well as URLs for NNTP newsgroup(s).