drm_connect...ble_property(9)

📦 version 7.3.1, in nixpkgs unstable

💖 drm_connect...ble_property(9) 💖

okay so bestie, we are in the Kernel API Manual today and this page is lowkey a tiny little icon — it's literally one function and it's giving "short but slays" energy ✨

🌸 NAME 🌸

drm_connector_attach_vrr_capable_property — she creates the vrr_capable property 🎀

Like, that's the whole job. She makes the property. That's her moment. Periodt.

🦋 SYNOPSIS 🦋

int drm_connector_attach_vrr_capable_property (struct drm_connector *connector );

✨ ARGUMENTS ✨

  • connector — the connector you wanna create the vrr_capable property on 🫶 that's it, that's the whole argument, no cap.

💅 DESCRIPTION 💅

so here's the tea — this one is used by atomic drivers to add support for querying the variable refresh rate capability for a connector 🔥

translation: your connector gets a lil property that lets peeps ask "hey, can you do VRR or not?" and the driver gets to answer. main character behaviour, honestly 💜

⭐ RETURN ⭐

  • Zero on success 💖 (slay)
  • a negative errno on failure 😭 (it happens to the best of us)

🌈 SEE ALSO 🌈

bestie the cross-reference list here is long — like she knows everybody at the function party. grab a snack 🍓:

🫶 yes, standard connector properties(9) really does show up twice in there. we do not gatekeep, we do not editorialise, we list it exactly how she came. iykyk 💀

and that's the whole page, bestie — short, sweet, and fully iconic 👑

this lil masterpiece lives over in ./drivers/gpu/drm and the version fairy stamped it October 2026 🧚‍♀️ so go forth, attach your vrr_capable property, and slay 💖✨🎀

📦 where this page comes from