Re: [PATCH 1/3] backlight: Allow drivers to update the core, andgenerate events on changes

[Zhang Rui]

On Wed, 2009-07-15 at 16:22 +0800, Richard Purdie wrote:
> On Wed, 2009-07-15 at 15:55 +0800, Zhang Rui wrote:
> > > Also, are "userspace" and "kernel" as meaningful as they could be?
> > Would
> > > "sysfs" and "hwkeys" make more sense and allow for other future hardware
> > > differences? Perhaps someone will tie the backlight to an ambient light
> > > sensor for example...
> > > 
> > 
> > Hah, I just finished a patch to introduce the ACPI als driver.
> > 
> > I'm not quite familiar with the status of ALS support in Linux kernel.
> > and here is my questions,
> > I don't think we have a generic sysfs driver for ALS, i.e. ALS class
> > device, right?
> > do you guys think it's reasonable to have one?
> 
> We don't have one that I'm aware of.
> 
> The first question is what information and configuration options are we
> likely to have with ALS sensors? If its just a light level reading, the
> input subsystem is ideally suited for sharing that. Is there
> configuration we need to expose?
> 
For an ACPI ALS device, only these two are mandatory
1. the current ambient light illuminance.
2. A list of luminance mappings, including the "display luminance
adjustment" and "ambient light illuminance", which can be used by OS to
determine the ambient light policy.

IMO, the ALS driver should just export these info to user space, and we
can do the display backlight adjustment in user space,
via /sys/class/backlight.

thanks,
rui


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/