drm_atomic_h..._flip_target(9)

📦 version 7.3.1, in nixpkgs unstable

✨ drm_atomic_h..._flip_target(9) ✨

okay bestie so this is a page from the Kernel API Manual, section 9 — yes, the real-deal kernel one. buckle up, it's a short one but it's important 💅

🌸 NAME 🌸

drm_atomic_helper_page_flip_target — literally does a page flip on a target vblank period. that's it, that's the whole thing. it's giving "small function, big job" energy 🎀

✨ SYNOPSIS ✨

int drm_atomic_helper_page_flip_target (struct drm_crtc *crtc , struct
       drm_framebuffer *fb , struct drm_pending_vblank_event *event , uint32_t
       flags , uint32_t target , struct drm_modeset_acquire_ctx *ctx );

six params, returns an int, no cap. let's go through them one by one 🫶

💖 ARGUMENTS 💖

  • crtc — the DRM CRTC. the main character of this whole operation, honestly 👑
  • fb — the DRM framebuffer. this is the actual pixels that are gonna show up on screen 🖼️
  • event — an optional DRM event to signal when the flip is done. optional! so you can pass nothing and nobody's mad at you 🙈
  • flags — flip flags for non-vblank sync'ed updates 🔥
  • target — tells the function which target vblank period the flip should take effect on. very "be there at exactly this time" of it ⏰
  • ctx — the lock acquisition context 🔒

🦋 DESCRIPTION 🦋

so what does this actually do? it provides a default drm_crtc_funcs.page_flip_target implementation. like, the out-of-the-box one. no cap 📦

it's similar to drm_atomic_helper_page_flip, except it has that extra target parameter so you can specify the target vblank period you want the flip to land on. so it's the same vibe, just with ✨ precision ✨

⭐ RETURN ⭐

returns 0 on success, and negative errno numbers on failure. so if you get a negative number back, that's your sign something went sideways 😭

🌈 SEE ALSO 🌈

bestie. this list is long and i'm not skipping a single one, because every single one of these is a real reference and we don't gatekeep here 💜

like i said. the whole friend group 🫶

okay that's the page!! this one came from ./drivers/gpu/drm, dated October 2026, and it lives in the Kernel API Manual — go forth and flip those targets bestie, you're so valid for reading the docs 💖🎀✨

📦 where this page comes from