linux-kernel - Re: [GIT PULL v2] LM3532 backlight support improvements and relocation

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: <20190408193055.GN49658@atomide.com>
Date:   Mon, 8 Apr 2019 12:30:55 -0700
From:   Tony Lindgren <tony@...mide.com>
To:     Dan Murphy <dmurphy@...com>
Cc:     Pavel Machek <pavel@....cz>,
        Jacek Anaszewski <jacek.anaszewski@...il.com>, robh@...nel.org,
        lee.jones@...aro.org, linux-leds@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [GIT PULL v2] LM3532 backlight support improvements and
 relocation

* Dan Murphy <dmurphy@...com> [190408 15:54]:
> On 4/7/19 5:17 PM, Pavel Machek wrote:
> > Plus, I'd kind of expect ALS enabled/disabled to be runtime controled,
> > not from the device tree.
> 
> We can always add runtime override control to the driver.

Yeah that sounds good to me :) Sounds like this can be done
with follow up patches though.

> Just need to see if there is a common interface from input or IIO we can adopt.

Hmm can the lm3532 registers actually show the value
for the ALS sensors?

Regards,

Tony