drm_atomic_b...n_pre_enable(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

drm_atomic_b...n_pre_enable(9) πŸ’…βœ¨

okay so bestie, we’re in the Kernel API Manual and this page is literally called drm_atomic_b...n_pre_enable(9) β€” the full function name is giving main-character energy right below. 🫢


🌸 NAME 🌸

drm_atomic_bridge_chain_pre_enable β€” prepares for enabling all bridges in the encoder chain. πŸ’–

✨ SYNOPSIS ✨

void drm_atomic_bridge_chain_pre_enable (struct drm_bridge *bridge ,
       struct drm_atomic_commit *state );

πŸŽ€ ARGUMENTS πŸŽ€

  • bridge β€” bridge control structure 🫢
  • state β€” atomic state being committed ✨

πŸ’… DESCRIPTION πŸ’…

So this one calls the drm_bridge_funcs.atomic_pre_enable op for all the bridges in the encoder chain, starting from the last bridge to the first. It’s giving reverse-order slay. πŸ”₯ These are called before calling drm_encoder_helper_funcs.atomic_enable.

If a bridge sets pre_enable_prev_first, then the pre_enable for the prev bridge will be called before pre_enable of this bridge. That’s the whole vibe check. πŸ¦‹

🌈 EXAMPLE 🌈

Picture it:

Bridge A ---> Bridge B ---> Bridge C ---> Bridge D ---> Bridge E

With pre_enable_prev_first flag enable in Bridge B, D, E then the resulting pre_enable order would be, Bridge C, Bridge D, Bridge E, Bridge A, Bridge B. πŸ‘‘

⭐ NOTE ⭐

tiny note, huge consequences: the bridge passed should be the one closest to the encoder. no cap. πŸ’€

πŸ’œ SEE ALSO πŸ’œ

go read these next, bestie:


mwah πŸ’‹ that’s the whole page! this one comes from the Kernel API Manual, source ./drivers/gpu/drm, date October 2026, and its page name is drm_atomic_b...n_pre_enable(9). byeee 🫢✨

πŸ“¦ where this page comes from