Re: [GIT PULL] Ambient Light Sensors subsystem

[Dmitry Torokhov <dmitry.torokhov@gmail.com>]

On Wed, Mar 03, 2010 at 09:03:16AM -0800, Linus Torvalds wrote:
> 
> 
> On Tue, 2 Mar 2010, Dima Zavin wrote:
> > 
> > I definitely see the need for what you guys are trying to accomplish.
> > For example, currently, we use an input device for reporting events,
> > and a separate misc device node for control
> > (enable/disable/configure). It's definitely suboptimal, but there
> > currently isn't anything there would let us do things cleanly.
> 
> I have to say, I personally don't see why something like an ambient light 
> sensor _isn't_ just an input device. 
> 
> What's the difference between a physical "increase screen brightness" key, 
> and a "ambient light sensor"? Absolutely none as far as I can tell.

Because in general ambient light sensor may have nothing to do with the
screen brightness. The fact that all current uses are tied to
controlling screen brightness is coincidential. You could use it as well
to turn on the lights in the kitchen if it is getting too dark...

> 
> And for something like an X server, it sounds a lot more natural to just 
> have another input device than to have yet abother event reporting 
> interface.
> 

Yes, it is easier, but it is not necessarily the right interface. I
still believe in using input layer for human iteraction events, and not
as generic transport a-la netlink or uevent. Voltage measurements,
network cable presence notifications, ambient light/temperature sensors,
and so forth do not belong here.

-- 
Dmitry