drm_crtc_handle_vblank(9)

📦 version 7.3.1, in nixpkgs unstable

Hiii bestie 💖 this is drm_crtc_handle_vblank(9), from the Kernel API Manual, and it's literally all about handling a vblank event — interrupt-handler main character energy, no cap ✨.

💖 NAME 💖

drm_crtc_handle_vblank — handle a vblank event 🎀

🌸 SYNOPSIS 🌸

bool drm_crtc_handle_vblank (struct drm_crtc *crtc );

🎀 ARGUMENTS 🎀

  • crtc — where this event occurred 📍

✨ DESCRIPTION ✨

Okay so bestie, drivers should call this routine in their vblank interrupt handlers to update the vblank counter and send any signals that may be pending. That's the whole assignment, and it ate 💅

This is the native KMS version of drm_handle_vblank. Periodt.

Now the barrier bit — don't skip this, it's important 🫶 For a given vblank counter value, drm_crtc_handle_vblank and drm_crtc_vblank_count or drm_crtc_vblank_count_and_time provide a barrier: any writes done before calling drm_crtc_handle_vblank will be visible to callers of the later functions, if the vblank count is the same or a later one. That's the guarantee, and it's highkey crucial.

See also drm_vblank_crtc.count. iykyk 😌

💫 RETURN 💫

True if the event was successfully handled, false on failure. Short and iconic.

🔥 SEE ALSO 🔥

Go read these too, bestie — they're all linked and they all matter:

Okay that's the page, bestie! source/version: ./drivers/gpu/drm, date: October 2026, and the manual page is drm_crtc_handle_vblank(9) — mwah 💋🫶

📦 where this page comes from