Benjamin Cheng 566b657784 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: 30ebe41582 ("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>		2023-03-13 17:27:48 -04:00
..
amdgpu_dm	drm/amd/display: Write to correct dirty_rect	2023-03-13 17:27:48 -04:00
dc	drm/amd/display: remove unused variable available	2023-03-08 14:06:04 -05:00
dmub	drivers/gpu: fix typo in comment	2023-03-08 14:05:04 -05:00
include	drm/amd/display: Drop CONFIG_DRM_AMD_DC_HDCP	2023-03-07 14:22:39 -05:00
modules	drm/amd/display: Drop unnecessary DCN guards	2023-03-07 14:22:40 -05:00
Kconfig	drm/amd/display: Rename DCN config to FP	2023-03-07 14:22:40 -05:00
Makefile	drm/amd/display: Drop CONFIG_DRM_AMD_DC_HDCP	2023-03-07 14:22:39 -05:00
TODO