[PATCH RFC 13/25] drm: Add VRR target frame rate properties
Michel Dänzer
michel.daenzer at mailbox.org
Wed Sep 23 02:51:45 PDT 2026
On 9/21/26 17:51, Nicolas Frattaroli wrote:
>
> + * .. _VRR-MIN-NUMERATOR:
> + *
> + * "VRR_MIN_NUMERATOR":
> + * Default &drm_crtc integer property forming the numerator of a
> + * numerator/denominator pair of a frame rate to set as the minimum VRR
> + * target rate. Set to 0 to disable.
> + *
> + * "VRR_MIN_DENOMINATOR":
> + * Default &drm_crtc integer property forming the denominator of a
> + * numerator/denominator pair of a frame rate to set as the minimum VRR
> + * target rate. If :ref:`VRR_MIN_NUMERATOR <VRR-MIN-NUMERATOR>` is not
> + * zero, it must be non-zero.
> + * Otherwise, must also be zero.
> + *
> + * .. _VRR-MAX-NUMERATOR:
> + *
> + * "VRR_MAX_NUMERATOR":
> + * Default &drm_crtc integer property forming the numerator of a
> + * numerator/denominator pair of a frame rate to set as the maximum VRR
> + * target rate. Set to 0 to disable.
> + *
> + * "VRR_MAX_DENOMINATOR":
> + * Default &drm_crtc integer property forming the denominator of a
> + * numerator/denominator pair of a frame rate to set as the maximum VRR
> + * target rate. If :ref:`VRR_MAX_NUMERATOR <VRR-MAX-NUMERATOR>` is not
> + * zero, it must be non-zero. Otherwise, must also be zero.
> */
Is there a reason that DENOMINATOR must be 0 when the corresponding NUMERATOR is? 0 divided by any number is still 0.
Either way, should these rules be enforced in drm_atomic_crtc_set_property?
--
Earthling Michel Dänzer \ GNOME / Xwayland / Mesa developer
https://redhat.com \ Libre software enthusiast
More information about the linux-arm-kernel
mailing list