diff options
| author | Piotr Maziarz <piotr.maziarz@amd.com> | 2026-09-03 13:31:05 +0200 |
|---|---|---|
| committer | Alex Deucher <alexander.deucher@amd.com> | 2026-09-23 13:19:46 -0400 |
| commit | 23c7a0a0ecd9a23aba3d61f65c8b4eacf5cd5908 (patch) | |
| tree | 18554c7293d6316d80ab45d7f0522ea9fbbe9a4a /tools/perf/scripts/python | |
| parent | 06421edfe74b5897dfcc37c00c8e0c40310cdc4f (diff) | |
| download | linux-23c7a0a0ecd9a23aba3d61f65c8b4eacf5cd5908.tar.gz linux-23c7a0a0ecd9a23aba3d61f65c8b4eacf5cd5908.zip | |
drm/amd/display: Remove phantom SW state ops from block sequence
[Why]
HWS_APPLY_UPDATE_FLAGS_FOR_PHANTOM and HWS_UPDATE_PHANTOM_VP_POSITION
program no hardware. They only mutate driver state: pipe update flags,
the phantom plane viewport and the phantom scaling params.
A block sequence is built first and executed later, so both ops ran only
after the builder had already inspected pipe_ctx->update_flags to decide
which steps to emit. The phantom pipe was therefore built from stale
flags.
[How]
Call apply_update_flags_for_phantom() and update_phantom_vp_position()
directly from hwss_build_post_unlock_full_sequence(), before
program_pipe_sequence(), matching the legacy
dcn401_post_unlock_program_front_end() ordering.
Reviewed-by: Alvin Lee <alvin.lee2@amd.com>
Signed-off-by: Piotr Maziarz <piotr.maziarz@amd.com>
Signed-off-by: George Zhang <george.zhang@amd.com>
Tested-by: Dan Wheeler <daniel.wheeler@amd.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions
