summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python
diff options
context:
space:
mode:
authorFrancesco Magazzu <postadelmaga@gmail.com>2026-09-18 15:16:20 +0200
committerLyude Paul <lyude@redhat.com>2026-09-18 14:09:01 -0400
commite5cccdafc855cd5f96f4b51d38114a0360b075d7 (patch)
treee035517bab28b278c2be5c9d7538bf4b0581eca2 /tools/perf/scripts/python
parent7ca7b8b5f2cc89ee843c2eab3272aac5aafb7b73 (diff)
downloadlinux-next-e5cccdafc855cd5f96f4b51d38114a0360b075d7.tar.gz
linux-next-e5cccdafc855cd5f96f4b51d38114a0360b075d7.zip
drm/nouveau/clk: don't clobber reclock status when restoring volt/fan
nvkm_cstate_prog() reuses 'ret' for the voltage and fan-speed restore calls it makes after reprogramming the clocks. Those calls almost always succeed, so the status of the reclock itself is overwritten and the function reports success even when clk->func->calc() or clk->func->prog() failed. The converse is also true: a successful reclock is reported as an error if the final restore call fails, even though that failure is only logged and otherwise ignored. The only consumer of the return value is the error message in nvkm_pstate_work(), so in practice a failing reclock is simply never reported. Nothing else changes, but a function that returns success on failure is a trap for the next caller. Keep the calc/prog status in 'ret' and use a separate local for the restore calls. Fixes: 3eca809b3c05 ("drm/nouveau/clk: cosmetic changes") Signed-off-by: Francesco Magazzu <postadelmaga@gmail.com> Reviewed-by: Lyude Paul <lyude@redhat.com> Signed-off-by: Lyude Paul <lyude@redhat.com> Link: https://patch.msgid.link/20260918131620.405133-5-postadelmaga@gmail.com
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions