summaryrefslogtreecommitdiff
path: root/drivers/gpu/drm/amd/amdgpu/amdgpu_mca.c
diff options
context:
space:
mode:
authorHarry Wentland <harry.wentland@amd.com>2024-03-15 13:02:00 -0400
committerAlex Deucher <alexander.deucher@amd.com>2024-04-30 09:51:30 -0400
commit66eba12a5482b79ed8cc45ae6f370b117b8e0507 (patch)
tree5fc7015055ce6e1dcdc2341e3446bb51d9aaf123 /drivers/gpu/drm/amd/amdgpu/amdgpu_mca.c
parent3a99045c56d0b98f91d092044b04a2321b5e2f8f (diff)
downloadlinux-66eba12a5482b79ed8cc45ae6f370b117b8e0507.tar.gz
linux-66eba12a5482b79ed8cc45ae6f370b117b8e0507.tar.bz2
linux-66eba12a5482b79ed8cc45ae6f370b117b8e0507.zip
drm/amd/display: Do cursor programming with rest of pipe
Cursors are always programmed independently of updates on other planes. When atomic commits program cursor and surface updates together the cursor update might be locked out by the surface update and not take effect. To combat this program cursor and surface updates together via dc_update_planes_and_stream to ensure they can be applied atomically. When cursor updates come on their own use the old method to program the cursor as dc_update_planes_and_stream isn't handling this case correctly (yet), leading to a flickering screen. Closes: https://gitlab.freedesktop.org/drm/amd/-/issues/2186 Reviewed-by: Agustin Gutierrez <agustin.gutierrez@amd.com> Acked-by: Wayne Lin <wayne.lin@amd.com> Signed-off-by: Harry Wentland <harry.wentland@amd.com> Tested-by: Daniel Wheeler <daniel.wheeler@amd.com> Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
Diffstat (limited to 'drivers/gpu/drm/amd/amdgpu/amdgpu_mca.c')
0 files changed, 0 insertions, 0 deletions