v4l2_m2m_dst_buf_is_last(9)

📦 version 7.3.1, in nixpkgs unstable

💖 v4l2_m2m_dst_buf_is_last(9) 💖

okay so bestie, welcome to the Kernel API Manual — yes, that's the actual manual name, we're in the big leagues now ✨. This one's about a tiny little function that answers one very specific question about your mem2mem session, and honestly it's giving "quiet hero of the drain state machine" energy.

🌸 NAME 🌸

v4l2_m2m_dst_buf_is_last — returns the current encoding/decoding session draining management state of the next queued capture buffer. like, it tells you whether the buffer you're about to hand over is the final one in the whole session 🎀

✨ SYNOPSIS ✨

bool v4l2_m2m_dst_buf_is_last (struct v4l2_m2m_ctx *m2m_ctx );

she takes one pointer, she gives you a bool. lowkey iconic 💅

🦋 ARGUMENTS 🦋

  • m2m_ctx — the m2m context that's assigned to the instance, which was given to you by struct v4l2_m2m_ctx. that's the one and only thing she needs from you 🫶

🔥 DESCRIPTION 🔥

so here's the vibe: this last capture buffer should be tagged with V4L2_BUF_FLAG_LAST, and that tag is what notifies everyone that the capture session is ending. that's it, that's the whole point — no cap. mark the final buffer, signal the end, done 😭💖

fr fr though — the flag is doing the actual announcing here. this function exists to tell you whether your next queued capture buffer is the one that gets it. 🧚

👑 SEE ALSO 👑

Kernel file ./include/media/v4l2-mem2mem.h — go read it, she has lore 💜 — plus literally all of these:

that's the whole page, bestie — mwah 💋

came from ./include/media, dated October 2026, and the page itself is v4l2_m2m_dst_buf_is_last(9) — shoutout to the kernel docs squad for keeping the vibe alive 🎀✨🦋

📦 where this page comes from