Bhawanpreet Lakha fa2a3786c4 drm/amd/display: reuse current context instead of recreating one ... [Why] Currently we discard the current context and recreate it. The current context is what is applied to the HW so we should be re-using this rather than creating a new context. Recreating the context can lead to mismatch between new context and the current context For example: gsl groups get changed when we create a new context this can cause issues in a multi display config (with flip immediate) because we don't align the existing gsl groups in the new and current context. If we reuse the current context the gsl group assignment stays the same. [How] Instead of discarding the current context, we instead just copy the current state and add/remove planes and streams. Signed-off-by: Bhawanpreet Lakha <Bhawanpreet.Lakha@amd.com> Reviewed-by: Nicholas Kazlauskas <Nicholas.Kazlauskas@amd.com> Acked-by: Anson Jacob <Anson.Jacob@amd.com> Tested-by: Daniel Wheeler <daniel.wheeler@amd.com> Signed-off-by: Alex Deucher <alexander.deucher@amd.com>		2021-02-02 12:08:50 -05:00
..
amdgpu_dm	drm/amd/display: reuse current context instead of recreating one	2021-02-02 12:08:50 -05:00
dc	drm/amd/display: reuse current context instead of recreating one	2021-02-02 12:08:50 -05:00
dmub	drm/amd/display: Update dcn30_apply_idle_power_optimizations() code	2021-01-21 09:54:34 -05:00
include	drm/amd/display: Add internal display info	2020-11-24 12:08:15 -05:00
modules	drm/amd/display: change license of color_table.c	2021-01-25 17:47:57 -05:00
Kconfig	drm/amdgpu/display: drop DCN support for aarch64	2021-01-05 11:35:53 -05:00
Makefile	drm/amd/display: Drop CONFIG_DRM_AMD_DC_DMUB guards	2019-11-13 15:29:42 -05:00
TODO