__vc4_crtc_init(9)

✨ __vc4_crtc_init(9) ✨

okay so bestie, welcome to the Kernel API Manual 💅 this is the page for __vc4_crtc_init, and yes it's the one with the double underscore, we do NOT drop the underscores, they're load-bearing 🫶

---

🌸 NAME 🌸

__vc4_crtc_init — Initializes a CRTC 💖

---

🦋 SYNOPSIS 🦋

int __vc4_crtc_init (struct drm_device *drm , struct platform_device
*pdev , struct vc4_crtc *vc4_crtc , const struct vc4_crtc_data *data ,
struct drm_plane *primary_plane , const struct drm_crtc_funcs
*crtc_funcs , const struct drm_crtc_helper_funcs *crtc_helper_funcs ,
bool feeds_txp );

like, that's a LOT of arguments and every single one is doing the most, but we respect it 👑

---

🎀 ARGUMENTS 🎀

• drm — DRM Device. the whole big picture energy ✨
• pdev — CRTC Platform Device 🧚
• vc4_crtc — CRTC Object to Initialize. the main character being born fr 💫
• data — Configuration data associated with this CRTC 🌸
• primary_plane — Primary plane for CRTC 🦋
• crtc_funcs — Callbacks for the new CRTC 💜
• crtc_helper_funcs — Helper Callbacks for the new CRTC 🫶
• feeds_txp — Is this CRTC connected to the TXP? like an actual bool, yes or no, iconic question 🎀

---

🔥 DESCRIPTION 🔥

So what it does is: it initializes our private CRTC structure 💅

⚠️ and this is the part you NEED to hear: this function is mostly relevant for KUnit testing, and all other users should use vc4_crtc_init instead. not __vc4_crtc_init. the regular one. no underscores. write it down bestie 😭

---

⭐ RETURN ⭐

0 on success 🎉, and a negative error code on failure 💀

---

🌈 SEE ALSO 🌈

• Kernel file ./drivers/gpu/drm/vc4/vc4_crtc.c 📁
• VC4 CRTC module(9) 👑

---

and that's the whole page, no cap ✨ big love to the ./drivers/gpu/drm/vc4 source, this little October 2026 edition of the Kernel API Manual — slay, ate, periodt 💅🎀🦋