output-management: Add more detailed vrr configuration #42
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
wlr-output-configuration simply differentiates between
enabled
anddisabled
for adaptive sync. Given the flickering issues of some displays, we want to opportunistically enable VRR for fullscreen applications, so we need more state variants to represent all our vrr "modes".Additionally wlr-output-configuration does not make an attempt to advertise if VRR is even available. This makes some sense as there really isn't any good feedback mechanism in the DRM api. The property used to enable VRR is simply a hint and may or may not be honored by the compositor: https://drmdb.emersion.fr/properties/3435973836/VRR_ENABLED
However we can at least check, that said variable is available and the connector advertises support https://drmdb.emersion.fr/properties/3233857728/vrr_capable. While the wlr-output-management allows the compositor to simply fail any configurations trying to enable VRR in these cases, we would like to hide the UI, so lets add an event to advertise availability.