drm_crtc_get...vbltimestamp(9)

📦 version 7.3.1, in nixpkgs unstable

💖 drm_crtc_get...vbltimestamp(9) 💖

okay so bestie, welcome to the Kernel API Manual for drm_crtc_get...vbltimestamp(9) — yes the double-dot name is a whole thing, we don't question it, we just vibe 🫶

✨ NAME ✨

drm_crtc_get_last_vbltimestamp — bestie this function retrieves the raw timestamp for the most recent vblank interval and it's lowkey iconic for it 💅

🌈 SYNOPSIS 🌈

bool drm_crtc_get_last_vbltimestamp (struct drm_crtc *crtc , ktime_t
*tvblank , bool in_vblank_irq );

🎀 ARGUMENTS 🎀

  • crtc — the CRTC whose vblank timestamp you're trying to get, like it's the main character here fr
  • tvblank — pointer to the target time that should receive the timestamp. it's giving "hand me the receipt, I'll fill it in" energy 🧾
  • in_vblank_irq — set this to true when you're calling from drm_crtc_handle_vblank. some drivers gotta apply some workarounds for gpu-specific vblank irq quirks if this flag is set, so like… respect the flag ok 😭

🦋 DESCRIPTION 🦋

So what it does: it fetches the system timestamp corresponding to the time of the most recent vblank interval on the specified CRTC. May call into the kms-driver to compute the timestamp with a high-precision GPU-specific method — fancy, we love a high-precision era ✨

Heads up bestie: it returns zero if the timestamp originates from an uncorrected do_gettimeofday call, i.e., it isn't very precisely locked to the true vblank. No cap, that one's lowkey mid precision 🙈

💜 RETURN 💜

True if the timestamp is considered to be very precise, false otherwise. A simple girlie. A yes-or-no queen 👑

🌸 SEE ALSO 🌸

Kernel file ./drivers/gpu/drm/drm_vblank.c and honestly the whole vblank friend group came through:

okay that's the whole page bestie, you ate that reading session 💅✨ this one lives in ./drivers/gpu/drm, dated October 2026, and it's page drm_crtc_get...vbltimestamp(9) of the Kernel API Manual — go forth and timestamp accurately, mwah 🫶💖

📦 where this page comes from