diff options
| author | Benjamin Cheng <ben@bcheng.me> | 2023-03-12 20:47:39 -0400 |
|---|---|---|
| committer | Alex Deucher <alexander.deucher@amd.com> | 2023-03-13 17:27:48 -0400 |
| commit | 566b6577849fcca743aa63d43793062aba62166c (patch) | |
| tree | 5e7b9ce9ca493b21d612a3e628b12d64622aed49 /drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_helpers.c | |
| parent | 474e2d491efe8ce516e743dbce6a6e75bac3b3db (diff) | |
| download | linux-566b6577849fcca743aa63d43793062aba62166c.tar.gz linux-566b6577849fcca743aa63d43793062aba62166c.tar.bz2 linux-566b6577849fcca743aa63d43793062aba62166c.zip | |
drm/amd/display: Write to correct dirty_rect
When FB_DAMAGE_CLIPS are provided in a non-MPO scenario, the loop does
not use the counter i. This causes the fill_dc_dity_rect() to always
fill dirty_rects[0], causing graphical artifacts when a damage clip
aware DRM client sends more than 1 damage clip.
Instead, use the flip_addrs->dirty_rect_count which is incremented by
fill_dc_dirty_rect() on a successful fill.
Fixes: 30ebe41582d1 ("drm/amd/display: add FB_DAMAGE_CLIPS support")
Bug: https://gitlab.freedesktop.org/drm/amd/-/issues/2453
Signed-off-by: Benjamin Cheng <ben@bcheng.me>
Signed-off-by: Hamza Mahfooz <hamza.mahfooz@amd.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
Diffstat (limited to 'drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_helpers.c')
0 files changed, 0 insertions, 0 deletions