drm_connecto...ble_property(9)

📦 version 7.3.1, in nixpkgs unstable

💅 drm_connecto...ble_property(9) 💅

okay so bestie, welcome to the Kernel API Manual, section 9 — yes we're in the kernel docs, yes it's giving main character energy, and yes I'm gonna walk you through this one tiny function like it's the most iconic thing in drivers/gpu/drm. 🎀

✨ NAME ✨

drm_connector_set_vrr_capable_property — sets the variable refresh rate capable property for a connector. that's it, that's the whole vibe. 🦋

🌸 SYNOPSIS 🌸

void drm_connector_set_vrr_capable_property (struct drm_connector
*connector , bool capable );

literally just two args, no cap. 💜

🫶 ARGUMENTS 🫶

  • connector — a drm connector. your lil display buddy. the one we're talking about. 🖥️
  • capable — True if the connector is variable refresh rate capable. like, is it VRR girlie or not. true/false, that's the whole story. ✨

💖 DESCRIPTION 💖

okay so listen — this one should be used by atomic drivers to update the indicated support for variable refresh rate over a connector. that's the entire description and honestly? it ate. no extra lore, no hidden twist, just: atomic drivers, update the VRR-capable indication on a connector. periodt. 🔥

ngl bestie, "should be used by atomic drivers" is doing a lot of work in that sentence — it's the intended audience, so don't come at it from a non-atomic direction and expect a slay. 🙈

🧚 SEE ALSO 🧚

the friend group. the whole group chat. every single one of them, no skipping, we don't leave anyone on read 💀:

(and yes, standard connector properties(9) really does show up twice in there — I didn't do that, the kernel did, and we respect her choices 💅)

that's the whole page bestie, go forth and set those properties ✨

source: ./drivers/gpu/drm — dated October 2026 🎀 ily, drink water, and don't forget to unregister your connectors 💖

📦 where this page comes from