drm_calc_ti...ng_constants(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… drm_calc_timestamping_constants β€” Kernel API Manual (section 9)

okay so bestie, buckle up, we're in the Kernel API Manual today and the star of the show is drm_calc_timestamping_constants ✨


🌸 NAME 🌸

drm_calc_timestamping_constants β€” literally just calculating vblank timestamp constants, no biggie πŸ’…


πŸŽ€ SYNOPSIS πŸŽ€

void drm_calc_timestamping_constants (struct drm_crtc *crtc , const
       struct drm_display_mode *mode );

she takes two args and returns void, iykyk 🫢


πŸ¦‹ ARGUMENTS πŸ¦‹

  • crtc β€” the drm_crtc whose timestamp constants should be updated. yes, that one, the one you're pointing at πŸ‘‘
  • mode β€” the display mode containing the scanout timings. it's giving "where do I get the numbers from" energy πŸ“

✨ DESCRIPTION ✨

so what she does is calculate and store various constants which are later needed by vblank and swap-completion timestamping β€” e.g., by drm_crtc_vblank_helper_get_vblank_timestamp πŸ”₯

and the slay part? these constants are derived from the CRTC's true scanout timing, so they take things like panel scaling or other adjustments into account 😭 no cap, she's thorough.


🌈 SEE ALSO 🌈

like, that's the whole vblank friend group right there πŸ’€πŸ«Ά go read them, they all ate πŸ’–


this page lives in ./drivers/gpu/drm, dated October 2026, and yes the header up top and the footer at the bottom are the same drm_calc_timestamping_constants(9) β€” iconic, consistent, periodt 🌟

πŸ“¦ where this page comes from