xf86-video-amdgpu integration for DRM variable refresh rate API
This patch is part of a proposed new interface for supporting variable refresh rate via DRM properties.
This adds support for setting CRTC variable refresh property when FreeSync suitable windows cover a CRTC and issue flips via the Present extension.
=== Changes from v1 ===
- The AMDGPU extension has been dropped in favor of the _VARIABLE_REFRESH window property
- FreeSync state is now tracked per CRTC instead of on the Screen
- The variable_refresh property is only enabled on amdgpu_present_flip
=== Adaptive sync and variable refresh rate ===
Adaptive sync is part of the DisplayPort spec and allows for graphics adapters to drive displays with varying frame timings.
Variable refresh rate (VRR) is essentially the same, but defined for HDMI.
=== Use cases for variable refresh rate ===
Variable frame (flip) timings don't align well with fixed refresh rate displays. This results in stuttering, tearing and/or input lag. By adjusting the display refresh rate dynamically these issues can be reduced or eliminated.
However, not all content is suitable for dynamic refresh adaptation. Content that is flipped infrequently or at random intervals tends to fair poorly. Multiple clients trying to flip under the same screen can similarly interfere with prediction.
Userland needs a way to let the driver know when the content on the screen is suitable for variable refresh rate and if the user wishes to have the feature enabled.
=== DRM API to support variable refresh rates ===
This patch introduces a new API via atomic properties on the DRM connector and CRTC.
The connector has two new optional properties:
bool variable_refresh_capable - set by the driver if the hardware is capable of supporting variable refresh tech
bool variable_refresh_enabled - set by the user to enable variable refresh adjustment over the connector
The CRTC has one additional default property:
- bool variable_refresh - a content hint to the driver specifying that the CRTC contents are suitable for variable refresh adjustment
== Overview for DRM driver developers ===
Driver developers can attach the optional connector properties via drm_connector_attach_variable_refresh_properties on connectors that support variable refresh (typically DP or HDMI).
The variable_refresh_capable property should be managed as the output on the connector changes. The property is read only from userspace.
The variable_refresh_enabled property is intended to be a property controlled by userland as a global on/off switch for variable refresh technology. It should be checked before enabling variable refresh rate.
=== Overview for Userland developers ==
The variable_refresh property on the CRTC should be set to true when the CRTCs are suitable for variable refresh rate. In practice this is probably an application like a game - a single window that covers the whole CRTC surface and is the only client issuing flips.
To demonstrate the suitability of the API for variable refresh and dynamic adaptation there are additional patches using this API that implement adaptive variable refresh across kernel and userland projects:
- DRM (dri-devel)
- amdgpu DRM kernel driver (amd-gfx)
- xf86-video-amdgpu (amd-gfx)
- mesa (mesa-dev)
These patches enable adaptive variable refresh on X for AMD hardware provided that the user sets the variable_refresh_enabled property to true on supported connectors (ie. using xrandr --set-prop).
The patches have been tested as working on upstream userland with the GNOME desktop environment under a single-monitor setup. They also work on KDE in single monitor setup if the compositor is disabled.
The patches require that the application window can issue screen flips via the Present extension to xf86-video-amdgpu. Due to Present extension limitations some desktop environments and multi-monitor setups are currently not compatible.
Full implementation details for these changes can be reviewed in their respective mailing lists.
=== Previous discussions ===
These patches are based upon feedback from patches and feedback from two previous threads on the subject which are linked below for reference:
https://lists.freedesktop.org/archives/amd-gfx/2018-April/021047.html https://lists.freedesktop.org/archives/dri-devel/2017-October/155207.html https://lists.freedesktop.org/archives/amd-gfx/2018-September/026519.html