AMD Updates HDMI 2.1 VRR & ALLM Patches But Will Miss Out On Linux 7.3

AMD previously contributed HDMI 2.1 Fixed Rate Link (FRL) support to the mainline Linux kernel, establishing a baseline for high-bandwidth video over HDMI. The current effort extends that baseline by addressing variable-rate refresh and auto-low-latency mode, which are essential for adaptive sync and reduced input lag on compatible displays. These patches target the open-source AMDGPU driver, the primary graphics stack for AMD hardware on Linux.

The new patches introduce driver logic to negotiate VRR and ALLM capabilities during HDMI link setup, allowing the GPU to dynamically adjust refresh rates and signal low-latency mode to the display. This expands the HDMI 2.1 feature set beyond the already-upstreamed FRL support, bringing a more complete implementation to Linux users. The changes are confined to the driver layer and do not require firmware updates.

Because the patches miss the cut-off for the Linux 7.3 release, they will not be available in that kernel series. Engineers who need VRR or ALLM now must either stay on an earlier kernel with back-ported patches or compile a newer kernel once the patches land in a subsequent release. The cost is the additional effort of building or maintaining a custom kernel and ensuring compatibility with the rest of the system stack.

On systems running Linux 7.3, HDMI 2.1 connections will continue to operate with FRL only, lacking the adaptive refresh and low-latency benefits. Applications that rely on smooth frame pacing or minimal input delay will not see the expected improvements until the driver updates are present. This limitation is especially relevant for gaming, video playback, and professional graphics workflows that depend on precise timing.

When the patches are eventually merged into a later kernel, the AMDGPU driver will automatically expose VRR and ALLM to user-space, requiring only standard driver updates to activate the features. Until then, developers should monitor kernel release notes for the inclusion of these patches and plan testing accordingly. The interim period may involve using custom builds for any projects that cannot tolerate the missing functionality.