summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/bin/stackcollapse-record
diff options
context:
space:
mode:
authorLyude Paul <lyude@redhat.com>2026-08-14 15:43:50 -0400
committerLyude Paul <lyude@redhat.com>2026-09-11 13:26:03 -0400
commit24fbd6d4bcf3363ef13ebe0d36dea93f30396c6d (patch)
treebf15494a783cebab179d7e8df13e54322336ceea /tools/perf/scripts/python/bin/stackcollapse-record
parent12f6eff11ccf9cad3b2dfcdd94184fdb9ffface2 (diff)
downloadlinux-next-24fbd6d4bcf3363ef13ebe0d36dea93f30396c6d.tar.gz
linux-next-24fbd6d4bcf3363ef13ebe0d36dea93f30396c6d.zip
drm/nouveau/gsp/r570: Enable S/R Display workaround in GSP
There's two flags that we've never been setting when asking GSP to suspend the GPU, which OpenRM does set: GPU_STATE_FLAGS_PRESERVING GPU_STATE_FLAGS_PM_TRANSITION These flags aren't -supposed- to do much in GSP, they're mostly used by OpenRM itself for state tracking. The only thing they do from GSP's side is control whether or not a single display related workaround is applied during suspend. But as it turns out, that single workaround is actually quite crucial for getting runtime PM working with nouveau - and without it set we end up seeing a lot more failures with runtime PM resume. So, let's start setting it. Signed-off-by: Lyude Paul <lyude@redhat.com> Fixes: 53dac0623853 ("drm/nouveau/gsp: add support for 570.144") Cc: <stable@vger.kernel.org> # v6.16+ Reviewed-by: Dave Airlie <airlied@redhat.com> Link: https://patch.msgid.link/20260814194542.781955-4-lyude@redhat.com (cherry picked from commit ca57629b3eb912c77bc4357178a2130ea6c2d6df) Signed-off-by: Lyude Paul <lyude@redhat.com>
Diffstat (limited to 'tools/perf/scripts/python/bin/stackcollapse-record')
0 files changed, 0 insertions, 0 deletions