STANDARD CRTC PROPERTIES(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

standard CRTC properties πŸ’…

okay so bestie, this is the Kernel API Manual, section 9 β€” standard CRTC properties(9) β€” and we're about to make DRM CRTC properties make sense. DRM CRTCs have a few standardized properties, and yes, they're all getting the group-chat treatment. πŸŽ€

✨ the standardized properties ✨

  • ACTIVE β€” Atomic property for setting the power state of the CRTC. When set to 1 the CRTC will actively display content. When set to 0 the CRTC will be powered off. There is no expectation that user-space will reset CRTC resources like the mode and planes when setting ACTIVE to 0. User-space can rely on an ACTIVE change to 1 to never fail an atomic test as long as no other property has changed. If a change to ACTIVE fails an atomic test, this is a driver bug. For this reason setting ACTIVE to 0 must not release internal resources (like reserved memory bandwidth or clock generators). Note that the legacy DPMS property on connectors is internally routed to control this property for atomic drivers. periodt.
  • MODE_ID β€” Atomic property for setting the CRTC display timings. The value is the ID of a blob containing the DRM mode info. To disable the CRTC, user-space must set this property to 0. Setting MODE_ID to 0 will release reserved resources for the CRTC. πŸ¦‹
  • SCALING_FILTER β€” Atomic property for setting the scaling filter for CRTC scaler. The value of this property can be one of the following:
    • Default β€” Driver's default scaling filter.
    • Nearest Neighbor β€” Nearest Neighbor scaling filter.
  • SHARPNESS_STRENGTH β€” Atomic property for setting the sharpness strength/intensity by userspace. The value of this property is set as an integer value ranging from 0 - 255 where:
    • 0 β€” Sharpness feature is disabled(default value).
    • 1 β€” Minimum sharpness.
    • 255 β€” Maximum sharpness.

User can gradually increase or decrease the sharpness level and can set the optimum value depending on content. This value will be passed to kernel through the UAPI. The setting of this property does not require modeset. The sharpness effect takes place post blending on the final composed output. If the feature is disabled, the content remains same without any sharpening effect and when this feature is applied, it enhances the clarity of the content. ✨


πŸ‘€ SEE ALSO πŸ‘€

okay that's the whole page, bestie! 🫢 source/version: ./drivers/gpu/drm; date: October 2026; footer title: standard CRTC properties(9). mwah πŸ’‹πŸŒΈ

πŸ“¦ where this page comes from