drm_hdmi_av...content_type(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… drm_hdmi_avi_infoframe_content_type(9)

okay so bestie, welcome to the Kernel API Manual β€” this one's for drm_hdmi_av...content_type(9) and it's lowkey iconic πŸŽ€


✨ NAME ✨

drm_hdmi_avi_infoframe_content_type β€” she fills in the HDMI AVI infoframe content type information, based on the correspondent DRM property. no cap, that's literally her whole job πŸ’–


πŸ¦‹ SYNOPSIS πŸ¦‹

void drm_hdmi_avi_infoframe_content_type (struct hdmi_avi_infoframe
       *frame , const struct drm_connector_state *conn_state );

like, she takes two things and returns nothing (void) β€” main character energy of "i don't need to give anything back, the work speaks for itself" πŸ’…


🌸 ARGUMENTS 🌸

  • frame β€” the HDMI AVI infoframe. yeah, that frame. the one you're filling content type info into πŸ–ΌοΈ
  • conn_state β€” the DRM display connector state. this is your source of truth, the vibe check she reads from 🧚

🌈 SEE ALSO 🌈

so if you wanna go deeper (and ngl you should), the kernel file lives right here:

./drivers/gpu/drm/display/drm_hdmi_helper.c

and these are her besties β€” the whole friend group fr fr:


πŸ’€ real talk: these are the places to look when the AVI infoframe is giving nothing and you need to know why. go read them, i believe in you 🫢

and that's the whole page, bestie, you ate it up ✨ this came straight out of ./drivers/gpu/drm/display, dated October 2026, in the Kernel API Manual β€” mwah, go slay some infoframes πŸ”₯πŸ‘‘πŸ’œ

πŸ“¦ where this page comes from