drm_mode_get_hv_timing(9)

📦 version 7.3.1, in nixpkgs unstable

💖 drm_mode_get_hv_timing 💖

okay bestie, so this is a page from the Kernel API Manual — it's drm_mode_get_hv_timing(9), and it's lowkey one of the most straightforward little helpers in the DRM mode family. it just fetches the hdisplay/vdisplay for a given mode. that's it. that's the whole vibe. 🎀

✨ NAME ✨

drm_mode_get_hv_timing — fetches hdisplay/vdisplay for given mode

🌸 SYNOPSIS 🌸

void drm_mode_get_hv_timing (const struct drm_display_mode *mode , int
*hdisplay , int *vdisplay );

so yeah, it returns void (nothing comes back to you, it fills in your pointers), takes a const struct drm_display_mode * and two int * out-params. periodt. 💅

🦋 ARGUMENTS 🦋

  • mode — mode to query 🌟
  • hdisplay — hdisplay value to fill in ✍️
  • vdisplay — vdisplay value to fill in ✍️

💜 DESCRIPTION 💜

okay so here's the one thing you actually gotta know, and it's giving plot twist: the vdisplay value will be doubled if the specified mode is a stereo mode of the appropriate layout. 👀 like, not every stereo mode, only the ones with the appropriate layout — fr fr, that's the condition, don't @ me.

so hdisplay just gets filled in like normal, but vdisplay might come back twice as tall depending on that stereo situation. main character behavior honestly. 🔥

🌈 SEE ALSO 🌈

the kernel file lives at ./drivers/gpu/drm/drm_modes.c — that's the home base, iykyk 🏠

and here's the whole friend group, no cap, all of them, not skipping a single one:

🎀🫶✨

ngl the "appropriate layout" bit is doing a lot of heavy lifting in that description — it's the exact wording from the page, so keep it in mind and don't go assuming it doubles for every stereo mode. k? ty bestie 💖

and that's the page!! mwah 💋 this was drm_mode_get_hv_timing(9) from the Kernel API Manual, source ./drivers/gpu/drm, dated October 2026 — iconic, no notes, go query some modes you absolute legend 👑🌸

📦 where this page comes from