| Age | Commit message (Collapse) | Author |
|---|
|
Certain sensors like thermistor's, can read temperature higher than the
threshold even before a threshold violation uevent. This is because
certain thermistor's use comparator's to trigger threshold violation
independent of the ADC used to read the temperature. In those corner
case, thermal HAL can update the severity when a client is reading a
temperature and not notify them. So when an actual uevent occurs, client
notification will be skipped, because the severity wouldn't have
changed.
Update HAL to notify clients when the read temperature API see's the
threshold violation first before the uevent.
Change-Id: I30248b1364909a74b362fa732041c3f96917952c
|
|
Right now the thermal HAL will return a temperature, temperature
threshold and cooling device entry with a NAN value for a sensor that is
not supported. This will break the VTS test case, which expects an empty
vector in that case.
Change the thermal HAL to return empty vector in case the sensor is not
supported.
Also populate the thresholds value for CPU, GPU, Battery and skin
sensors for the V1.0 getTemperature API. Make sure that the threshold
values are also read in degree celsius.
Change-Id: I82ab1e9dd9672f1b93760e93b55e8943fc5acce0
|
|
Re-size cpu usage vector to cpu count size before filling in the data.
This will ensure that sufficient memory is allocated before populating
the data.
Change-Id: I7a1d109cf3ec8403ca61beed9a9eab4287a3d33c
|
|
Add support for thermal HAL 2.0 interfaces. Also add support for HAL 1.0
interfaces to be backward compatible.
Change-Id: Ib0be008605db2751bda21f537ea694b3f9849800
|
