drm_vblank_work_schedule(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… drm_vblank_work_schedule(9)

okay so bestie, welcome to the drm_vblank_work_schedule page β€” it lives in the Kernel API Manual, and honestly it's giving "tiny function, very important job" energy ✨


πŸŽ€ NAME πŸŽ€

drm_vblank_work_schedule β€” schedule a vblank work. that's it. that's the whole job. she schedules, she slays πŸ’…


✨ SYNOPSIS ✨

int drm_vblank_work_schedule (struct drm_vblank_work *work , u64 count ,
bool nextonmiss );

literally just three args and an int coming back at you 🫢


🌸 ARGUMENTS 🌸

  • work β€” the vblank work you wanna schedule. this is your main character πŸŽ€
  • count β€” the target vblank count. like, the finish line you're aiming for ⭐
  • nextonmiss β€” defer until the next vblank if the target vblank was missed. the "oops, missed it, try again" switch πŸ”

πŸ¦‹ DESCRIPTION πŸ¦‹

so what does it actually do? you schedule work for execution once the crtc vblank count reaches count. simple as that, no cap ✨

now here's where it gets spicy 🌢️ there are two "you're already late" situations:

  • if the crtc vblank count has already reached count and nextonmiss is false, the work starts to execute immediately. no waiting, no queue, she's up πŸ”₯
  • if the crtc vblank count has already reached count and nextonmiss is true, the work is deferred until the next vblank β€” as if count had been specified as the crtc vblank count + 1. iykyk 😌

and the rearm tech, miss thing is self-rearming ready: if work is already scheduled, this function will reschedule said work using the new count. iconic behaviour honestly πŸ‘‘


πŸ’– RETURN πŸ’–

  • 1 β€” if work was successfully (re)scheduled. we love a win πŸŽ‰
  • 0 β€” if it was either already scheduled or cancelled. respectfully, nothing happened πŸ™ˆ
  • a negative error code β€” on failure. sad girl hours 😭

🌈 SEE ALSO 🌈

go read these too, bestie, they're the whole friend group:


🌸 reminder: nextonmiss genuinely changes when your work fires, so don't just pick one at random and hope for the best. vibe check your timing first πŸ’…

and that's the page!! mwah πŸ’‹ this one came from ./drivers/gpu/drm, dated October 2026, in the Kernel API Manual β€” go forth and schedule responsibly, bestie πŸ«Άβœ¨πŸŽ€

πŸ“¦ where this page comes from