Il 04/06/2011 22:22, Alan Cox ha scritto:
The longer term plan is to stick all kinds of device sensors (as distinct
from input devices) into the IIO layer but that is still in staging and
seems to have no clear plan of date for migration yet. However Jonathan
(the maintainer) also doesn't seem too keen on owning them either
http://lkml.org/lkml/2010/3/3/378
All in all ALS is a bit of a disaster area.
So, what to do now? I'm not sure that the IIO layer is always fine when
dealing with notbooks. For example, on every ALS equipped Vaio notebook,
setting the notebook to generate ALS events will also result in _BCM no
longer applying any further backlight change, it will instead generate
another ACPI event when calling (this allows to have, in userspace, a
single piece of software mixing and applying coherently both ALS driven
and user driven backlight corrections).
On newer Vaios, the ALS sensor is totally controlled by the EC, so we
just have the illuminance reading and talking about "device driver"
don't make much sense (we'd better have an ALS device class). I don't
know how other vendors introduced this functionality, but I can imagine
that many different implementation are present across different models
or brands. We need a solution, now, because there are lots of notebooks
with these tiny but useful sensors, and people do want to use them.
--
To unsubscribe from this list: send the line "unsubscribe platform-driver-x86"
in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
