intel_fdi_atomic_check_link(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

okay so bestie, welcome to the kernel API manual for intel_fdi_atomic_check_link(9) β€” yes it's a mouthful, no we're not renaming it, and honestly it's kind of iconic that a function this long-named is out here doing the most important vibe check on your FDI links πŸ¦‹


✨ NAME ✨

intel_fdi_atomic_check_link β€” the one that checks all your modeset FDI link configuration. like, all of it. every single one. no cap πŸ’…


🌸 SYNOPSIS 🌸

int intel_fdi_atomic_check_link (struct intel_atomic_state *state ,
       struct intel_link_bw_limits *limits );

that's the whole signature, bestie, copy it exactly, don't get creative πŸ“


πŸŽ€ ARGUMENTS πŸŽ€

  • state β€” the intel atomic state. yes. that one. the main character of this whole operation πŸ‘‘
  • limits β€” the link BW limits. bandwidth boundaries. the rules of engagement 🫢

πŸ’– DESCRIPTION πŸ’–

so here's the tea: this function checks the link configuration for all modeset FDI outputs. every single one, no skipping, no picking favourites 🌈

and if the configuration is invalid? don't panic β€” limits will get updated if possible to reduce the total BW. the way it tries to make things work out is honestly so generous of it 😭

but here's the catch, and it's a real one: after that happens, the configuration for all CRTCs in state must be recomputed with the updated limits. not some of them. not the ones you feel like. all of them. periodt πŸ’€


πŸ”₯ RETURN πŸ”₯

  • 0 β€” slay, the configuration is valid βœ…
  • -EAGAIN β€” the configuration is invalid and limits got updated with fallback values, with which the configuration of all CRTCs in state must be recomputed. so like, it's not over, you just gotta run it back πŸ”
  • Other negative error β€” the configuration is invalid without a fallback possibility, or the check failed for another reason. yeah. that one hurts πŸ™ˆ

⭐ SEE ALSO ⭐

  • Kernel file ./drivers/gpu/drm/i915/display/intel_fdi.c β€” go read the source, it's giving lore πŸ‘€
  • intel_fdi_add_affected_crtcs(9) β€” its friend, also worth a look 🧚

fr fr bestie, if you get -EAGAIN do not just ignore it β€” that's a "recompute all the CRTCs in state" situation, and the manpage said it twice so you know it's serious πŸ’œ

and that's the whole page! written from ./drivers/gpu/drm/i915/display, dated October 2026, and yes the page name is still intel_fdi_atomic_check_link(9) because we don't do rebrands here πŸ’…βœ¨ bye bestie, go check those links πŸ¦‹

πŸ“¦ where this page comes from