tickerguy/WX_435_Kernel-Tickerguy — comment on commit 0b64a6d9b00cfbce6f2b135108057019b55ec5f5
File: drivers/i2c/chips/ltr502als.c line 94
By tickerguy:

It shouldn't. I ran several traces with the debugging level cranked up
and the sensor is NOT enabled unless it's in use in the first place
(e.g. it is not turned on unless you're making a call!) so I do not see
the logic FIH was using here.

The only thing I can come up with is that Froyo was doing something very
different (e.g. it was turning them all on at boot or similar) where
Gingerbread does not. In any event the light sensor is combined with
this in the hardware (it's one chip and one i2c interface point) and as
such since the chip has to be powered up when the screen is on for light
sensor use anyway I don't see where the power budget harm could be come
from. If it has a notable impact I'll look at it further, but for now
this roach is SQUASHED.

On 10/22/2011 10:19 AM, Isaac wrote:
> Do you think this will negatively impact battery life? What was FIH's reasoning behind doing this here at the kernel level/driver?
>