drm/amd/display: Clear stream->mode_changed after commit
authorNicholas Kazlauskas <nicholas.kazlauskas@amd.com>
Fri, 25 Jan 2019 20:23:09 +0000 (15:23 -0500)
committerAlex Deucher <alexander.deucher@amd.com>
Tue, 19 Feb 2019 20:58:26 +0000 (15:58 -0500)
[Why]
The stream->mode_changed flag can persist in the following sequence
of atomic commits:

Commit 1:
Enable CRTC0 (mode_changed = true), Enable CRTC1 (mode_changed = true)

Commit 2:
Disable CRTC1 (mode_changed = false)

In this sequence we want to keep the exiting CRTC0 but it's not in the
atomic state for the commit since it hasn't been modified. In this case
the stream->mode_changed flag persists as true and we don't re-program
the planes for the existing stream.

[How]
The flag needs to be cleared and it makes the most sense to do it within
DC after the state has been committed. Nothing following dc_commit_state
should think that the stream's mode has changed.

Signed-off-by: Nicholas Kazlauskas <nicholas.kazlauskas@amd.com>
Reviewed-by: Leo Li <sunpeng.li@amd.com>
Acked-by: Tony Cheng <Tony.Cheng@amd.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
drivers/gpu/drm/amd/display/dc/core/dc.c

index 52f838442e21082ae1d0fa20beed15905b7414c9..8879cd4bb70cb729f397b817e5fa05b6596edf5d 100644 (file)
@@ -1138,6 +1138,9 @@ static enum dc_status dc_commit_state_no_check(struct dc *dc, struct dc_state *c
        /* pplib is notified if disp_num changed */
        dc->hwss.optimize_bandwidth(dc, context);
 
+       for (i = 0; i < context->stream_count; i++)
+               context->streams[i]->mode_changed = false;
+
        dc_release_state(dc->current_state);
 
        dc->current_state = context;