drm_atomic_..._chain_check(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ drm_atomic_..._chain_check(9) ✨

okay so this is a page straight out of the Kernel API Manual, and it's giving "bridge chain atomic check" realness, bestie. buckle up πŸ’…


πŸŽ€ NAME πŸŽ€

drm_atomic_bridge_chain_check β€” literally do an atomic check on the bridge chain, that's the whole vibe πŸ¦‹


🌸 SYNOPSIS 🌸

int drm_atomic_bridge_chain_check (struct drm_bridge *bridge , struct
drm_crtc_state *crtc_state , struct drm_connector_state *conn_state );

πŸ’– ARGUMENTS πŸ’–

  • bridge β€” the bridge control structure, our main character 🫢
  • crtc_state β€” the new CRTC state, fresh out of the box ✨
  • conn_state β€” the new connector state, also new, also iconic πŸ‘‘

πŸ”₯ DESCRIPTION πŸ”₯

okay so the order here is so important, listen. first you trigger a bus format negotiation, right? and then for all the bridges in the encoder chain you call the drm_bridge_funcs.atomic_check op β€” and if that's not there it just falls back on drm_bridge_funcs.mode_fixup, no big deal, she's flexible πŸ’β€β™€οΈ

and the direction?? you go from the last bridge to the first. yes, backwards, that's just how she rolls πŸ’€

all of that happens before drm_encoder_helper_funcs.atomic_check gets called. so this is the pre-game, the warm-up, the little prelude before the main event πŸŽ€ no cap.


⭐ RETURN ⭐

  • 0 when everything slays βœ…
  • a negative error code when it doesn't 😭 (failure era, we hate to see it)
ngl bestie, if you get a negative number back, that's your sign to go fix something.

πŸ‘‘ SEE ALSO πŸ‘‘

kernel file ./drivers/gpu/drm/drm_bridge.c, plus the whole friend group β€” go read these too fr fr:


🌈 that's the whole page, you ate that. periodt. πŸ’…

and that's a wrap bestie!! this one lives down in ./drivers/gpu/drm and it's dated October 2026 β€” go off, you're now officially fluent in bridge chain behavior πŸ§šβ€β™€οΈπŸ’œπŸ“

πŸ“¦ where this page comes from