vpfe_schedule_next_buffer(9)

📦 version 7.3.1, in nixpkgs unstable

okay so bestie, welcome to the Kernel API Manual ✨ this page is literally all about vpfe_schedule_next_buffer(9) and it's giving "tiny function, important job" energy 🎀

🌸 NAME 🌸

vpfe_schedule_next_buffer — set next buffer address for capture 💖

✨ SYNOPSIS ✨

void vpfe_schedule_next_buffer (struct vpfe_device *vpfe );

it's a void function, no return value, just vibes and buffer scheduling 🫶

🎀 ARGUMENTS 🎀

  • vpfe — ptr to vpfe device (literally a pointer to the vpfe device, bestie 💅)

🦋 DESCRIPTION 🦋

okay so here's the tea ☕ this function will get the next buffer from the dma queue and set the buffer address in the vpfe register for capture. then the buffer is marked active — periodt 💯

no cap, that's the whole flow: next buffer from the dma queue ➡️ buffer address goes into the vpfe register for capture ➡️ buffer marked active. iconic behavior honestly 👑

💜 SEE ALSO 💜

Kernel file ./drivers/media/platform/ti/am437x/am437x-vpfe.c — go read the source, iykyk 🔥

🫶 cute little sign-off bestie: this page is vpfe_schedule_next_buffer(9) from the Kernel API Manual, source file ./drivers/media/platform/ti/am437x/am437x-vpfe.c, dated October 2026 — slay and goodbye 💅✨

📦 where this page comes from