diff options
| author | Oleksij Rempel <o.rempel@pengutronix.de> | 2021-11-17 13:34:26 +0300 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2022-01-27 13:03:21 +0300 |
| commit | 94821ce188c2b37551ee9bdcfa282801e736207f (patch) | |
| tree | 0226cdfdd7c10f2a7c996e2ef9aef97b433099a2 /drivers/thermal/thermal_sysfs.c | |
| parent | b588858c09a5c4a894cbbf974e7ae1d6c72469df (diff) | |
| download | linux-94821ce188c2b37551ee9bdcfa282801e736207f.tar.xz | |
thermal/drivers/imx: Implement runtime PM support
[ Upstream commit 4cf2ddf16e175ee18c5c29865c32da7d6269cf44 ]
Starting with commit d92ed2c9d3ff ("thermal: imx: Use driver's local
data to decide whether to run a measurement") this driver stared using
irq_enabled flag to make decision to power on/off the thermal
core. This triggered a regression, where after reaching critical
temperature, alarm IRQ handler set irq_enabled to false, disabled
thermal core and was not able read temperature and disable cooling
sequence.
In case the cooling device is "CPU/GPU freq", the system will run with
reduce performance until next reboot.
To solve this issue, we need to move all parts implementing hand made
runtime power management and let it handle actual runtime PM framework.
Fixes: d92ed2c9d3ff ("thermal: imx: Use driver's local data to decide whether to run a measurement")
Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de>
Tested-by: Petr Beneš <petr.benes@ysoft.com>
Link: https://lore.kernel.org/r/20211117103426.81813-1-o.rempel@pengutronix.de
Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'drivers/thermal/thermal_sysfs.c')
0 files changed, 0 insertions, 0 deletions