diff options
author | Leo Li <sunpeng.li@amd.com> | 2024-12-11 20:06:24 +0300 |
---|---|---|
committer | Alex Deucher <alexander.deucher@amd.com> | 2025-01-10 20:10:08 +0300 |
commit | 4caacd1671b7a013ad04cd8b6398f002540bdd4d (patch) | |
tree | b08aa6ce2cf66d3d0ce1b8330cc836e09f08897c /tools/perf/scripts/python/task-analyzer.py | |
parent | aa6713fa2046f4c09bf3013dd1420ae15603ca6f (diff) | |
download | linux-4caacd1671b7a013ad04cd8b6398f002540bdd4d.tar.xz |
drm/amd/display: Do not elevate mem_type change to full update
[Why]
There should not be any need to revalidate bandwidth on memory placement
change, since the fb is expected to be pinned to DCN-accessable memory
before scanout. For APU it's DRAM, and DGPU, it's VRAM. However, async
flips + memory type change needs to be rejected.
[How]
Do not set lock_and_validation_needed on mem_type change. Instead,
reject an async_flip request if the crtc's buffer(s) changed mem_type.
This may fix stuttering/corruption experienced with PSR SU and PSR1
panels, if the compositor allocates fbs in both VRAM carveout and GTT
and flips between them.
Fixes: a7c0cad0dc06 ("drm/amd/display: ensure async flips are only accepted for fast updates")
Reviewed-by: Tom Chung <chiahsuan.chung@amd.com>
Signed-off-by: Leo Li <sunpeng.li@amd.com>
Signed-off-by: Tom Chung <chiahsuan.chung@amd.com>
Tested-by: Daniel Wheeler <daniel.wheeler@amd.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
Diffstat (limited to 'tools/perf/scripts/python/task-analyzer.py')
0 files changed, 0 insertions, 0 deletions