v4l2_m2m_init(9)

📦 version 7.3.1, in nixpkgs unstable

💖 v4l2_m2m_init(9) — the Kernel API Manual, but make it cute 💖

okay so bestie, you found it: v4l2_m2m_init from the Kernel API Manual. this is the one that gets your mem-to-mem driver's whole vibe started. buckle up 🎀

✨ NAME ✨

v4l2_m2m_init — initialize per-driver m2m data

like, per-driver. not per-context, not per-whatever-else. per driver. noted. 💅

🌸 SYNOPSIS 🌸

struct v4l2_m2m_dev * v4l2_m2m_init (const struct v4l2_m2m_ops *m2m_ops
);

yes the line break is real, that's just how the page wraps it, we don't judge 🫶

🦋 ARGUMENTS 🦋

  • m2m_ops — pointer to struct v4l2_m2m_ops. that's it. that's the whole argument list. one (1) pointer, and it's to your ops struct 💜

🔥 DESCRIPTION 🔥

so like… usually you call this from your driver's probe function. that's the vibe. that's the whole description. it's giving "short and iconic" 👑

if you're sitting there like "wait, when do i call it then??" — usually probe. the manpage said usually. we're respecting the usually. ✨

⭐ RETURN ⭐

it returns an opaque pointer to the internal data you need to handle an M2M context 🎀

opaque means don't peek inside, bestie. it's not for you. it's for the framework. hands off 🙈

🌈 SEE ALSO 🌈

this section is lowkey a whole group chat, so let's break it down 💬 first up, the header file itself:

  • Kernel file ./include/media/v4l2-mem2mem.h

then the structs (the main characters 👑):

  • struct v4l2_m2m_ops(9)
  • struct v4l2_m2m_queue_ctx(9)
  • struct v4l2_m2m_ctx(9)
  • struct v4l2_m2m_buffer(9)

then the function fam, and there are so many of them, we love a big family 🫶:

that's the whole roster, no cuts, no skips, we ate and left no crumbs 🍓

mwah that's the page. it lives in ./include/media and it's dated October 2026 — so yeah, it's giving future icon, we stan 👑✨💅

📦 where this page comes from