v4l2_m2m_try_run(9)

🎀 v4l2_m2m_try_run(9) 🎀

Okay bestie, welcome to the Kernel API Manual page for v4l2_m2m_try_run 💖. It’s giving “pick the next job and let it cook if possible” energy, fr fr.

---

🌸 NAME 🌸

v4l2_m2m_try_run — select next job to perform and run it if possible ✨

---

🦋 SYNOPSIS 🦋

void v4l2_m2m_try_run (struct v4l2_m2m_dev *m2m_dev );

---

💅 ARGUMENTS 💅

• m2m_dev — per-device context 🫶

---

🔥 DESCRIPTION 🔥

It grabs the next transaction — if present, bestie — from the waiting jobs list and runs it 🏃‍♀️💨.

Note that this function can run on a given v4l2_m2m_ctx context, but call .device_run for another context 👀. Like yes, it’s standing in one context’s group chat but can still ring up another context’s .device_run — that’s the vibe, iykyk.

---

👑 SEE ALSO 👑

Kernel file ./drivers/media/v4l2-core/v4l2-mem2mem.c:

• struct v4l2_m2m_dev(9)
• v4l2_m2m_try_schedule(9)
• v4l2_m2m_device_run_work(9)
• v4l2_m2m_cancel_job(9)

---

💖 source/version: ./drivers/media/v4l2-core — dated October 2026. bye bestie, go slay some jobs! 💅