path: root/init/Makefile
diff options
authorVille Syrjälä <>2019-09-03 18:40:18 +0300
committerRodrigo Vivi <>2019-10-03 12:23:07 -0700
commit485f682be9fc8d41376936a3b01423edd07b9a75 (patch)
tree2ee009ad7afc27651c5d8e5ec0c48b1a7f2cee5c /init/Makefile
parenteb0192fed016db1c5a9701cd6ca47233ff4a43e5 (diff)
Revert "drm/i915: Fix DP-MST crtc_mask"
This reverts commit 4eaceea3a00f8e936a7f48dcd0c975a57f88930f. Several userspace clients (modesetting ddx and mutter+wayland at least) handle encoder.possible_crtcs incorrectly. What they essentially do is the following: possible_crtcs = ~0; for_each_possible_encoder(connector) possible_crtcs &= encoder->possible_crtcs; Ie. they calculate the intersection of the possible_crtcs for the connector when they really should be calculating the union instead. In our case each MST encoder now has just one unique bit set, and so the intersection is always zero. The end result is that MST connectors can't be lit up because no crtc can be found to drive them. I've submitted a fix for the modesetting ddx [1], and complained on #wayland about mutter, so hopefully the situation will improve in the future. In the meantime we have regression, and so must go back to the old way of misconfiguring possible_crtcs in the kernel. [1] Cc: Jonas Ådahl <> Cc: Stanislav Lisovskiy <> Cc: Lionel Landwerlin <> Cc: Dhinakaran Pandiyan <> Cc: Lucas De Marchi <> Bugzilla: Signed-off-by: Ville Syrjälä <> Link: Reviewed-by: José Roberto de Souza <> (cherry picked from commit e838bfa8e170415fa3cc8e83ecb171e809c0c422) Signed-off-by: Rodrigo Vivi <>
Diffstat (limited to 'init/Makefile')
0 files changed, 0 insertions, 0 deletions