summaryrefslogtreecommitdiff
path: root/mm/mempool.c
diff options
context:
space:
mode:
authorMiquel Raynal <miquel.raynal@bootlin.com>2018-12-12 12:36:40 +0300
committerEduardo Valentin <edubezval@gmail.com>2019-01-02 15:47:17 +0300
commit879d7362d1d01efd476a143c09048f5945936c32 (patch)
tree04264584b1ad14ed127ed2cc7823ef4b63b29fdd /mm/mempool.c
parent5a78ad6d9c1b2c3c3226528346e9794ed3504381 (diff)
downloadlinux-879d7362d1d01efd476a143c09048f5945936c32.tar.xz
thermal: armada: add overheat interrupt support
The IP can manage to trigger interrupts on overheat situation from all the sensors. However, the interrupt source changes along with the last selected source (ie. the last read sensor), which is an inconsistent behavior. Avoid possible glitches by always selecting back only one channel which will then be referenced as the "overheat_sensor" (arbitrarily: the first in the DT which has a critical trip point filled in). It is possible that the scan of all thermal zone nodes did not bring a critical trip point from which the overheat interrupt could be configured. In this case just complain but do not fail the probe. Also disable sensor switch during overheat situations because changing the channel while the system is too hot could clear the overheat state by changing the source while the temperature is still very high. Even if the overheat state is not declared, overheat interrupt must be cleared by reading the DFX interrupt cause _after_ the temperature has fallen down to the low threshold, otherwise future possible interrupts would not be served. A work polls the corresponding register until the overheat flag gets cleared in this case. Suggested-by: David Sniatkiwicz <davidsn@marvell.com> Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com> Signed-off-by: Eduardo Valentin <edubezval@gmail.com>
Diffstat (limited to 'mm/mempool.c')
0 files changed, 0 insertions, 0 deletions