drm_hdmi_av...content_type(9)
π 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:
drm_hdmi_infoframe_set_hdr_metadata(9)drm_hdmi_avi_infoframe_colorimetry(9)drm_hdmi_avi_infoframe_bars(9)drm_hdmi_compute_mode_clock(9)drm_hdmi_acr_get_n_cts(9)
π 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
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms