drm_atomic_b...chain_enable(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… drm_atomic_b...chain_enable(9) ✨

okay so this is a page straight out of the Kernel API Manual, bestie β€” buckle up πŸŽ€

🌸 NAME 🌸

drm_atomic_bridge_chain_enable β€” literally turns on every single bridge in the encoder chain πŸ’–

✨ SYNOPSIS ✨

void drm_atomic_bridge_chain_enable (struct drm_bridge *first_bridge ,
struct drm_atomic_commit *state );

🫢 ARGUMENTS 🫢

  • first_bridge β€” the bridge control structure, aka your starting point, your main character πŸ¦‹
  • state β€” the atomic state that's being committed rn, no cap ✨

πŸ”₯ DESCRIPTION πŸ”₯

So what it does: it calls the drm_bridge_funcs.atomic_enable op for all the bridges in the encoder chain β€” starting from the first bridge and going all the way to the last, in order, periodt πŸ’…

And the timing? These get called after drm_encoder_helper_funcs.atomic_enable finishes. Like, sequence matters, iykyk ⭐

πŸ’€ NOTE πŸ’€

the bridge you pass in should be the one closest to the encoder β€” not me stressing about this, but like, actually do this πŸ™ˆ

πŸ‘‘ SEE ALSO πŸ‘‘

Kernel file ./drivers/gpu/drm/drm_bridge.c


and that's the whole vibe 🧚 from ./drivers/gpu/drm, dated October 2026, signed off by your girl drm_atomic_b...chain_enable(9) πŸ’œ mwah, slay, go enable some bridges πŸ“πŸŒˆ

πŸ“¦ where this page comes from