drm-tests: atomictest: fix CRTC enable/disable
Previously, we disabled unused CRTCs by setting the "ACTIVE"
and "MODE_ID" to 0, while activating another CRTC.
This leads to issues, since atomic_set_prop puts the disabled
CRTC in the next CRTC state. The atomic checks are structured
in a such a way that they assume every CRTC in the next CRTC
state should be completely active or completely inactive,
leading to commit failures. This CL changes CRTC enable/disable
to have the semantics that atomic expects.
Additionally, use bs_drm_pipe_plumber to determine which connectors
match to which CRTCs.
BUG=b:62204308
TEST./atomictest primary_pageflip
passes on Kevin.
Change-Id: Ib32a0fd385e71fc049780ec2464b3071b9821b66
Reviewed-on: https://chromium-review.googlesource.com/523452
Commit-Ready: Gurchetan Singh <gurchetansingh@chromium.org>
Tested-by: Gurchetan Singh <gurchetansingh@chromium.org>
Reviewed-by: Zach Reizner <zachr@chromium.org>
1 file changed
