drm_crtc_init_with_planes(9)

💖 drm_crtc_init_with_planes(9) 💖

okay so bestie, this is a page from the Kernel API Manual and it's literally about making a brand-new CRTC object and handing it its planes. pull up a chair 🎀

---

✨ NAME ✨

drm_crtc_init_with_planes — initialise a new CRTC object with specified primary and cursor planes. that's it, that's the whole vibe 💅

---

🌸 SYNOPSIS 🌸

int drm_crtc_init_with_planes (struct drm_device *dev , struct drm_crtc
*crtc , struct drm_plane *primary , struct drm_plane *cursor , const
struct drm_crtc_funcs *funcs , const char *name , ... );

like, yes, that's a lot of arguments. we'll get through it together 🫶

---

🦋 ARGUMENTS 🦋

• dev — the DRM device, the whole main character of this story 👑
• crtc — the CRTC object you're initialising. the one getting the glow-up ✨
• primary — the primary plane for this CRTC 🌟
• cursor — the cursor plane for this CRTC 🖱️
• funcs — the callbacks for your new CRTC. the behaviour handbook, iykyk 💜
• name — a printf style format string for the CRTC name, or NULL for the default name 🏷️
• ... — variable arguments, for feeding that printf format string 🍓

---

💀 DESCRIPTION 💀

So what this does is init a new object created as the base part of a driver crtc object. fr fr, that's the job 💅

Drivers should use this function instead of drm_crtc_init — and not me being dramatic, that one is only provided for backwards compatibility with drivers which do not yet support universal planes. so like, legacy energy 🙈

The drm_crtc_funcs.destroy hook should call drm_crtc_cleanup and kfree the crtc structure. and listen — the crtc structure should not be allocated with devm_kzalloc. no cap, don't do it 😭

The primary and cursor planes are only relevant for legacy uAPI — see drm_crtc.primary and drm_crtc.cursor if you wanna go deeper 👀

---

🧚 NOTE 🧚

consider using drmm_crtc_alloc_with_planes or drmm_crtc_init_with_planes instead of drm_crtc_init_with_planes to let the DRM managed resource infrastructure take care of cleanup and deallocation. lowkey the move, honestly — let the infrastructure handle the boring parts so you don't have to 🌈

---

⭐ RETURN ⭐

Zero on success, error code on failure. slay when it's zero, and uh. bestie when it's not 💀

---

🔥 SEE ALSO 🔥

• Kernel file ./drivers/gpu/drm/drm_crtc.c overview(9)
• drm_crtc_from_index(9)
• standard CRTC properties(9)
• drmm_crtc_init_with_planes(9)
• drm_crtc_cleanup(9)
• drm_mode_getcrtc(9)
• drm_mode_set_config_internal(9)
• drm_crtc_check_viewport(9)
• drm_mode_setcrtc(9)
• drm_crtc_create_scaling_filter_property(9)
• drm_crtc_in_clone_mode(9)

go read them all, they're giving study group 📚✨

---

mwah 💋 this page lives in ./drivers/gpu/drm and it was stamped October 2026 — thanks for reading the whole thing bestie, you ate and left no crumbs 🎀💖🦋