lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1a1482f7-a683-49d5-69a3-aa73a641288e@gmail.com>
Date:   Fri, 12 Apr 2019 21:34:33 +0200
From:   Jacek Anaszewski <jacek.anaszewski@...il.com>
To:     robh+dt@...nel.org
Cc:     Dan Murphy <dmurphy@...com>, pavel@....cz, lee.jones@...aro.org,
        devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
        linux-leds@...r.kernel.org
Subject: Re: [PATCH v2 4/6] dt-bindings: ti-lmu: Modify dt bindings for the
 LM3697

And one more:

[5] - LED naming patch set v3

On 4/11/19 9:48 PM, Jacek Anaszewski wrote:
> Hi Rob,
> 
> I've collected references to the DT patches we're waiting
> to be reviewed. This is just to make sure that none of them
> will be missed - recent traffic on the linux-leds list
> is a bit heavier.
> 
> [0] - draft of LED multi color class - we would especially like
>        to get a feedback on the proposed brightness-model DT design
> [1][2] - LM3697 backlight driver rework
> [3][4] - LM36274 backlight driver with regulator support
> 
> On 4/5/19 4:28 PM, Dan Murphy wrote:
>> The LM3697 is a single function LED driver. The single function LED
>> driver needs to reside in the LED directory as a dedicated LED driver
>> and not as a MFD device.  The device does have common brightness and ramp
>> features and those can be accomodated by a TI LMU framework.
>>
>> The LM3697 dt binding needs to be moved from the ti-lmu.txt and a 
>> dedicated
>> LED dt binding needs to be added.  The new LM3697 LED dt binding will 
>> then
>> reside in the Documentation/devicetree/bindings/leds directory and 
>> follow the
>> current LED and general bindings guidelines.
>>
>> Signed-off-by: Dan Murphy <dmurphy@...com>
[...]
> [0] https://marc.info/?l=linux-kernel&m=155414072611538&w=2
> [1] https://marc.info/?l=devicetree&m=155447454524411&w=2
> [2] https://lore.kernel.org/patchwork/patch/1058762/
> [3] https://marc.info/?l=devicetree&m=155447624324995&w=2
> [4] https://lore.kernel.org/patchwork/patch/1058779/
> 

[5] - https://marc.info/?l=linux-kernel&m=155405492231039&w=2

-- 
Best regards,
Jacek Anaszewski

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ