intel_fdi_ad...fected_crtcs(9)

💅 bestie, welcome to intel_fdi_ad...fected_crtcs(9) 💅

okay so this is the Kernel API Manual page for intel_fdi_add_affected_crtcs, and we’re gonna get you fluent in FDI CRTC business. no cap. ✨

🌸 NAME 🌸

intel_fdi_add_affected_crtcs — add CRTCs on FDI affected by other modeset CRTCs

✨ SYNOPSIS ✨

int intel_fdi_add_affected_crtcs (struct intel_atomic_state *state );

🎀 ARGUMENTS 🎀

• state — the intel atomic state. that’s the whole vibe. 💅

💅 DESCRIPTION 💅

So here’s the tea: this function adds a CRTC using FDI to state if changing another CRTC’s FDI BW usage is known to affect the available FDI BW for the former CRTC. In practice, this means adding CRTC B on IVYBRIDGE if its use of FDI lanes is limited (by CRTC C) and CRTC C is getting disabled. iconic behavior, honestly. 🦋

It returns 0 in case of success, or a negative error code otherwise. so if you see a negative, that’s the error-code girlie reporting in 😭

🦋 SEE ALSO 🦋

• Kernel file ./drivers/gpu/drm/i915/display/intel_fdi.c
• intel_fdi_atomic_check_link(9)

mwah 💋 that’s the whole page, bestie! it comes from the source/version line ./drivers/gpu/drm/i915/display, dated October 2026 — intel_fdi_ad...fected_crtcs(9) girlies stay winning. 🫶✨