thermald: fix incorrect target state settting by thermald

[Colin Ian King]

We should be including this latest upstream fix:

It was observed that in the case of cooling device with min_state > max_state,
thermald doesn't set the cooling device to the intended target state per the
configuration in XML. This is because of sorting the zone_trip_limits list in
ascending order based on target value is not suitable for the case of cooling
device with min_state > max_state. Thus this issue is fixed by:

1. sorting the zone_trip_limits list in descending order based on target value
for the case of cooling device with min_state > max_state.

2. sorting the zone_trip_limits list in ascending order based on target value
for the case of cooling device with max_state > min_state.

Example cooling device configuration which caused this issue:
<CoolingDevice>
        <Type>gpu_cooling</Type>
        <Path>/sys/class/mali/pm/max_freq_level</Path>
        <MinState>4</MinState>
        <MaxState>1</MaxState>
</CoolingDevice>.

Fix commit fd0671beba14586eb3e0b0fa2247a00100e6d418

[Launchpad Janitor (janitor)]

This bug was fixed in the package thermald - 1.5.3-4

---------------
thermald (1.5.3-4) unstable; urgency=medium

  * fix incorrect target state settting by thermald (LP: #1627400)
    - It was observed that in the case of cooling device with
      min_state > max_state, thermald doesn't set the cooling device to
      the intended target state per the configuration in XML. This is
      because of sorting the zone_trip_limits list in ascending order
      based on target value is not suitable for the case of cooling
      device with min_state > max_state. Upstream commit
      fd0671beba14586eb3e0b0fa2247a00100e6d418

 -- Colin King <email address hidden> Sun, 25 Sep 2016 01:33:11 +0100