v4l2_mc_create_media_graph(9)

💖 v4l2_mc_create_media_graph(9) — Kernel API Manual 💖

okay bestie, welcome to the glow-up of the kernel API manual ✨ this one lives in the Kernel API Manual (that's the manual name, we're not copying that header line, we're folding it in like a lil note 🎀), and it's all about building Media Controller links so your graph isn't a hot mess. let's get into it 💅

---

✨ NAME ✨

v4l2_mc_create_media_graph — literally here to create Media Controller links at the graph 🦋

---

🌸 SYNOPSIS 🌸

int v4l2_mc_create_media_graph (struct media_device *mdev );

---

💜 ARGUMENTS 💜

• mdev — a pointer to the media_device struct. that's it, that's the whole argument, she's low maintenance 🫶

---

👑 DESCRIPTION 👑

ok so what this does is add links between the entities that you'd normally find on PC customer's hardware on the V4L2 side 🔥 and the guest list is iconic:

• camera sensors
• audio and video PLL-IF decoders
• tuners
• analog TV decoder
• I/O entities — that's video, VBI and Software Defined Radio, iykyk 🌈

⚠️ NOTE: webcams are modelled on a very simple way: the sensor is connected directly to the I/O entity. all the dirty details, like scaler and crop HW, are hidden 🙈 and like, while such mapping is enough for v4l2 interface centric PC-consumer's hardware, V4L2 subdev centric camera hardware should not use this routine, because it will not build the right graph 😭 fr fr, don't do it, that graph will be a whole mess 💀

---

🦋 SEE ALSO 🦋

• Kernel file ./include/media/v4l2-mc.h
• v4l_enable_media_source(9)
• v4l_disable_media_source(9)
• v4l2_create_fwnode_links_to_pad(9)
• v4l2_create_fwnode_links(9)
• v4l2_pipeline_pm_get(9)
• v4l2_pipeline_pm_put(9)
• v4l2_pipeline_link_notify(9)

go read those next bestie, they're giving main character energy 👑

---

and that's the page!! source path is ./include/media and the date on this baby is October 2026 — mwah, slay, periodt 💅💖✨