On 15.09.25 12:01, Michel Dänzer wrote: > On 12.09.25 15:45, Derek Foreman wrote: >> On 9/12/25 2:33 AM, Chuanyu Tseng wrote: >>> >>> This is done through 2 new CRTC properties, along with a client >>> cap. See the docstrings in patch for details. > > Not sure why a client cap would be needed for this.
According to https://hwentland.github.io/work/2025hackfest-notes.html#vrr-for-desktop-use-cases the client cap was intended for disabling LFC & ramping in the kernel driver. It's not really needed for that though: If the min/max property values differ, the kernel driver can vary the effective refresh range between the limits and perform ramping, otherwise it can't. If the effective maximum value is at least twice the effective minimum value, the kernel driver can perform LFC, otherwise it can't. -- Earthling Michel Dänzer \ GNOME / Xwayland / Mesa developer https://redhat.com \ Libre software enthusiast
