Skip to content
This repository has been archived by the owner on Nov 1, 2021. It is now read-only.

drm: legacy: issue a NULL modeset on disable #1713

Merged
merged 1 commit into from
Jun 2, 2019

Conversation

Emantor
Copy link
Contributor

@Emantor Emantor commented Jun 2, 2019

The DRM subsystem needs a NULL modeset for connectors which disappear
from the system to disable the hardware pipes, otherwise the pixels get
rendered but are sent nowhere.

The atomic backend does the equivalent by removing the properties and
issuing a commit.

Fixes #1706

Tested by using WLR_DRM_NO_ATOMIC=1 sway and toggling my laptops internal eDP-1 display.

The DRM subsystem needs a NULL modeset for connectors which disappear
from the system to disable the hardware pipes, otherwise the pixels get
rendered but are sent nowhere.

The atomic backend does the equivalent by removing the properties and
issuing a commit.

Fixes swaywm#1706
@ascent12 ascent12 merged commit abddd7b into swaywm:master Jun 2, 2019
@ascent12
Copy link
Member

ascent12 commented Jun 2, 2019

Thanks

@Emantor Emantor deleted the fix/legacy_null_modeset branch June 2, 2019 12:14
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Development

Successfully merging this pull request may close these issues.

Do a NULL modeset on connector unplug
2 participants