xvip_pipeline_start_stop(9)

💅 xvip_pipeline_start_stop — from the Kernel API Manual

okay bestie, buckle up, because we're talking about xvip_pipeline_start_stop(9) today and honestly? she's a tiny function with main character energy. 💖

---

✨ NAME ✨

xvip_pipeline_start_stop — start ot stop streaming on a pipeline

(no bc the original NAME line literally says "ot" instead of "or" and I refuse to edit her, she's iconic, we stan a typo 💀)

---

🌸 SYNOPSIS 🌸

int xvip_pipeline_start_stop (struct xvip_pipeline *pipe , bool start );

---

🎀 ARGUMENTS 🎀

• pipe — the pipeline. your girl. the whole point.
• start — a bool that tells us what to do: start when it's true, stop when it's false. no in-between, no maybe, pick a lane bestie 🦋

---

🫶 DESCRIPTION 🫶

So here's the vibe check: the function walks the entities chain — starting at the pipeline output video node — and then starts or stops all of them. Every single one. No entity left behind. it's giving "we go together or we don't go at all" 😭✨

---

🔥 RETURN 🔥

• 0 if it's successful 🎉
• otherwise? you get the return value of the failed video::s_stream operation. like, whatever that call handed back, that's what you're getting. no cap.

ngl bestie, always check your return value. 0 is the slay, anything else means something in the chain did not pass the vibe check and you gotta deal with it 💅

---

👑 SEE ALSO 👑

• Kernel file ./drivers/media/platform/xilinx/xilinx-dma.c
• xvip_pipeline_set_stream(9)
• xvip_pipeline_cleanup(9)
• xvip_pipeline_prepare(9)
• struct xvip_dma_buffer(9)

---

and that's the whole page, periodt 💜 this lil gem lives in ./drivers/media/platform/xilinx, dated October 2026, straight out of the Kernel API Manual. go forth and stream responsibly, bestie 🧚🌸