aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/gpu/drm/amd/display/dc/dce80/dce80_resource.c
diff options
context:
space:
mode:
authorNicholas Kazlauskas <nicholas.kazlauskas@amd.com>2019-02-08 13:21:05 -0500
committerAlex Deucher <alexander.deucher@amd.com>2019-03-19 15:04:02 -0500
commitb9952f93cd2cf5fca82b06a8179c0f5f7b769e83 (patch)
tree6eb289eebe4c1ca5ea7f09b572637d9326c99878 /drivers/gpu/drm/amd/display/dc/dce80/dce80_resource.c
parentdrm/amd/display: Respect aux return values (diff)
downloadlinux-dev-b9952f93cd2cf5fca82b06a8179c0f5f7b769e83.tar.xz
linux-dev-b9952f93cd2cf5fca82b06a8179c0f5f7b769e83.zip
drm/amd/display: Set stream->mode_changed when connectors change
[Why] The kms_plane@plane-position-covered-pipe-*-planes subtests can produce a sequence of atomic commits such that neither active_changed nor mode_changed but connectors_changed. When this happens we remove the old stream from the context and add a new stream but the new stream doesn't have mode_changed=true set. This incorrect programming sequence causes CRC mismatches to occur in the test. The stream->mode_changed value should be set whenever a new stream is created. [How] A new stream is created whenever drm_atomic_crtc_needs_modeset is true. We previously covered the active_changed and mode_changed conditions for the CRTC but connectors_changed is also checked within drm_atomic_crtc_needs_modeset. So just use drm_atomic_crtc_needs_modeset directly to determine the mode_changed flag. Signed-off-by: Nicholas Kazlauskas <nicholas.kazlauskas@amd.com> Reviewed-by: Sun peng Li <Sunpeng.Li@amd.com> Acked-by: Bhawanpreet Lakha <Bhawanpreet.Lakha@amd.com> Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
Diffstat (limited to 'drivers/gpu/drm/amd/display/dc/dce80/dce80_resource.c')
0 files changed, 0 insertions, 0 deletions