This repository has been archived by the owner on Nov 1, 2021. It is now read-only.
Do a NULL modeset on connector unplug #1706
Labels
Comments
Emantor
added a commit
to Emantor/wlroots
that referenced
this issue
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 swaywm#1706
Emantor
added a commit
to Emantor/wlroots
that referenced
this issue
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 swaywm#1706
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I've learned today that if userspace doesn't do a NULL modeset when a connector changes its state from connected to disconnected, the pipe on the kernel side will remain active and will continue to send pixels (to /dev/null, wasting energy). This is apparently a "feature" for userspace that doesn't support hotplug events (so that after unplugging-replugging the screen receives again an image).
tl;dr we need to do a NULL modeset.
The text was updated successfully, but these errors were encountered: