summaryrefslogtreecommitdiffstats
path: root/proprietary-files.txt
diff options
context:
space:
mode:
authorDheeraj CVR <cvr.dheeraj@gmail.com>2015-01-21 19:04:31 +0530
committerDheeraj CVR <cvr.dheeraj@gmail.com>2015-01-22 18:12:53 +0530
commite2e299a94a967a2acd2ff8afe966c290e0a59549 (patch)
treeb18f4c77198faebdc2836fee69836772865472b4 /proprietary-files.txt
parentaf243d9b52f0c6bb70002b374f86a1d2321948ef (diff)
downloaddevice_samsung_t0lte-e2e299a94a967a2acd2ff8afe966c290e0a59549.tar.gz
device_samsung_t0lte-e2e299a94a967a2acd2ff8afe966c290e0a59549.tar.bz2
device_samsung_t0lte-e2e299a94a967a2acd2ff8afe966c290e0a59549.zip
libsensors: fix sensors enable and disable
* "//Accel sensor is first on and last off" This is totally wrong. The since we are using a single sysfs path to enable and disable all of the sensors, the kernel driver uses bitwise operations on the input value to know which sensors should be enabled. The current logic wrongly assumes that the sensors are enabled and disabled in a specific order and if accelerometer was disabled, all of the other sensors were being disabled too. This caused inconsistent sensor states between the sensor HAL and the kernel driver and most of the time, the sensors failed to work properly and drained battery. Simplify the code to use bitwise operations instead of arithematic operations to keep things clean. Additionally, since two or more sensors can be enabled or disabled at the same time, we use a lock to prevent race conditions. Change-Id: Ifc3fab1456d4061f58d52f2ecda822c6157aae6e
Diffstat (limited to 'proprietary-files.txt')
0 files changed, 0 insertions, 0 deletions