lkml.org 
[lkml]   [2019]   [Apr]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [GIT PULL v2] LM3532 backlight support improvements and relocation
* Dan Murphy <dmurphy@ti.com> [190408 20:04]:
> Tony
>
> On 4/8/19 2:30 PM, Tony Lindgren wrote:
> > * Dan Murphy <dmurphy@ti.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?
>
>
> No it can only report the current configured ALS zone not the LUX value.

Sounds like it should be just enable/disable or auto/manual
type toggle then in /sys somewhere for the users.

Not sure if ledtrig-backlight-auto vs ledtrig-backlight would
make sense?

Regards,

Tony

\
 
 \ /
  Last update: 2019-04-09 16:57    [W:0.047 / U:10.244 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site