diff options
| author | Nicholas Kazlauskas <[email protected]> | 2019-02-08 13:21:05 -0500 |
|---|---|---|
| committer | Alex Deucher <[email protected]> | 2019-03-19 15:04:02 -0500 |
| commit | b9952f93cd2cf5fca82b06a8179c0f5f7b769e83 (patch) | |
| tree | 6eb289eebe4c1ca5ea7f09b572637d9326c99878 /tools/perf/scripts/python/export-to-sqlite.py | |
| parent | 8ae5b1d78d4acbe9755570f26703962877f9108a (diff) | |
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 <[email protected]>
Reviewed-by: Sun peng Li <[email protected]>
Acked-by: Bhawanpreet Lakha <[email protected]>
Signed-off-by: Alex Deucher <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/export-to-sqlite.py')
0 files changed, 0 insertions, 0 deletions