drm_hdmi_avi...display_mode(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– NAME πŸ’–

okay bestie, so drm_hdmi_avi_infoframe_from_display_mode β€” yes that's the whole name, it's giving "my parents let me pick my own name and I chose chaos" β€” literally does one iconic job: it fills an HDMI AVI infoframe with data from a DRM display mode. that's the vibe. no cap. ✨

(this whole page is from the Kernel API Manual, and the function tag is drm_hdmi_avi...display_mode(9) β€” shortened for the header because the full name would not fit, and honestly same. πŸ’…)


🌈 SYNOPSIS 🌈

int drm_hdmi_avi_infoframe_from_display_mode (struct hdmi_avi_infoframe
*frame , const struct drm_connector *connector , const struct
drm_display_mode *mode );

so it takes three pointers and returns an int. that's it. that's the whole signature. she's simple, she's clean, she's serving. πŸŽ€


πŸ¦‹ ARGUMENTS πŸ¦‹

  • frame β€” the HDMI AVI infoframe. this is the thing getting filled up with data, she's the main character here fr fr πŸ‘‘
  • connector β€” the connector. yes, that's genuinely the whole description and honestly? valid. it's the connector. πŸ’€
  • mode β€” the DRM display mode. this is where the data comes from β€” it's the source material, the inspo, the blueprint 🫢

⭐ RETURN ⭐

0 on success, or a negative error code on failure. lowkey the classic Unix contract β€” zero means we ate, negative means something went sideways 😭

bestie pls always check the return value, a negative number is your code telling you it did not slay.

🌸 SEE ALSO 🌸

the kernel file to go peek at is ./drivers/gpu/drm/drm_edid.c β€” that's where the whole EDID/DRM friend group lives. and here is the entire squad, every single one, no cap, nobody gets left out of the group chat πŸ’œ:

like, forty of them. she's popular. iykyk πŸ’…


✨ that's the whole page babes ✨ this one's out of ./drivers/gpu/drm, dated October 2026, and it's still filed under drm_hdmi_avi...display_mode(9) β€” go read the source, mwah πŸŽ€πŸ’–πŸ¦‹

πŸ“¦ where this page comes from