drm_crtc_vbl...lank_timeout(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– drm_crtc_vbl...lank_timeout(9) πŸ’–

okay so welcome to the drm_crtc_vbl...lank_timeout(9) page, straight outta the Kernel API Manual β€” yes the title got truncated with the ... and no, we're not fixing it, it's ✨iconic✨ that way. this one's short and sweet and it's literally all about asking a CRTC "hey bestie, when's your next vblank?" πŸŽ€


✨ NAME ✨

drm_crtc_vblank_get_vblank_timeout β€” returns the vblank timeout πŸ’…

like, that's the whole job. it returns the vblank timeout. no cap.


🌸 SYNOPSIS 🌸

void drm_crtc_vblank_get_vblank_timeout (struct drm_crtc *crtc , ktime_t
*vblank_time );

copy it exactly, bestie, don't freestyle the signature πŸ™ˆ


πŸ¦‹ ARGUMENTS πŸ¦‹

  • crtc β€” the CRTC πŸ–₯️ like, the actual display controller we're talking about here.
  • vblank_time β€” returns the next vblank timestamp ⏰ yeah it's an out-param, it hands you back the timestamp, so don't come for it expecting it to be pre-filled.

🧚 DESCRIPTION 🧚

so the helper drm_crtc_vblank_get_vblank_timeout returns the next vblank timestamp of the CRTC's vblank timer, and it does that according to the timer's expiry time ✨

that's it. that's the whole vibe. it looks at when the timer's gonna expire and gives you the next vblank timestamp for that CRTC. short king behavior, honestly πŸ‘‘

fr fr read the signature before you call it β€” crtc goes in, vblank_time comes back filled with the next vblank timestamp. iykyk πŸ’œ

🌈 SEE ALSO 🌈

okay this list is long and i'm obsessed, every single one of these is a real reference and you're gonna read all of them, periodt πŸ’…

Kernel file ./drivers/gpu/drm/drm_vblank.c vblank handling(9), drm_crtc_accurate_vblank_count(9), drm_vblank_init(9), drm_dev_has_vblank(9), drm_crtc_vblank_waitqueue(9), drm_calc_timestamping_constants(9), drm_crtc_vblank_helper_get_vblank_timestamp_internal(9), drm_crtc_vblank_helper_get_vblank_timestamp(9), drm_crtc_get_last_vbltimestamp(9), drm_crtc_vblank_count(9), drm_vblank_count_and_time(9), drm_crtc_vblank_count_and_time(9), drm_crtc_next_vblank_start(9), drm_crtc_arm_vblank_event(9), drm_crtc_send_vblank_event(9), drm_crtc_vblank_get(9), drm_crtc_vblank_put(9), drm_crtc_wait_one_vblank(9), drm_crtc_vblank_off(9), drm_crtc_vblank_reset(9), drm_crtc_set_max_vblank_count(9), drm_crtc_vblank_on_config(9), drm_crtc_vblank_on(9), drm_crtc_vblank_restore(9), drm_handle_vblank(9), drm_crtc_handle_vblank(9), drm_crtc_vblank_start_timer(9), drm_crtc_vblank_cancel_timer(9)

like i said. a lot. but every one of them ate πŸ”₯


and that's the page!! πŸ’– this little drop came from ./drivers/gpu/drm and it's dated October 2026, so go forth and get those vblank timeouts, bestie β€” you're literally the main character of vblank handling now πŸ«Άβœ¨πŸŽ€

πŸ“¦ where this page comes from