summaryrefslogtreecommitdiff
path: root/scripts/git.orderFile
diff options
context:
space:
mode:
authorAngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>2026-07-21 12:52:30 +0200
committerDaniel Lezcano <daniel.lezcano@kernel.org>2026-08-07 17:18:48 +0200
commit6b73e78462ad420a61ef0bede534c0fecb0d7ba6 (patch)
treeae07b70aa450fa54139f88a395d1b4df226957c6 /scripts/git.orderFile
parent5f0d4a79439120650a858b9ccb345d08929df990 (diff)
downloadlinux-6b73e78462ad420a61ef0bede534c0fecb0d7ba6.tar.gz
linux-6b73e78462ad420a61ef0bede534c0fecb0d7ba6.zip
thermal/drivers/mediatek/lvts_thermal: Make reset optional for MT8196
Depending on the SoC+Firmware combination, the LVTS hardware may be may be actively used by one or even multiple concurrent MCUs! In this case, resetting it may produce either a severe slowdown of the entire system, or even a thermal protection AP reset, as some MCU(s) may be reading a very high or very low temperature while the LVTS is being reset. On those, don't fail if no reset is found as that may be omitted on purpose, but still check if there's one, because some board(s) may be running on a different bootchain with reduced firmwares or using firmwares with reduced functionality. So, use devm_reset_control_get_optional_exclusive() instead, as the LVTS controller always had only one reset and retrieving that by index, specifically, always made little sense anyway. Signed-off-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com> Signed-off-by: Daniel Lezcano <daniel.lezcano@kernel.org> Reviewed-by: Philipp Zabel <p.zabel@pengutronix.de> Reviewed-by: Chen-Yu Tsai <wenst@chromium.org> Link: https://patch.msgid.link/20260721105230.101906-3-angelogioacchino.delregno@collabora.com
Diffstat (limited to 'scripts/git.orderFile')
0 files changed, 0 insertions, 0 deletions