drm_atomic_...hain_disable(9)

📦 version 7.3.1, in nixpkgs unstable

💅 drm_atomic_bridge_chain_disable — Kernel API Manual energy

okay so bestie, welcome to the glow-up doc for drm_atomic_bridge_chain_disable(9), straight out of the Kernel API Manual. she's a bridge-chain girlie and she's about to shut everything down, reverse-order style. ✨

🌸 NAME 🌸

drm_atomic_bridge_chain_disable — disables all the bridges in the encoder chain. yes, all of them. every single one. 💅

🎀 SYNOPSIS 🎀

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

like, she takes two args and returns literally nothing (void). no notes. 🫶

🦋 ARGUMENTS 🦋

  • bridge — the bridge control structure. your main character struct, if you will.
  • state — the atomic state that's currently being committed. the vibe being locked in, fr fr.

🔥 DESCRIPTION 🔥

so what does she do? she calls the drm_bridge_funcs.atomic_disable op for all the bridges in the encoder chain — and the way she does it is iconic: she starts from the last bridge and works her way back to the first. reverse order, no cap. 🧚

and the timing matters, bestie: these get called before calling drm_encoder_helper_funcs.atomic_disable. so bridge chain first, encoder helper after. periodt. ⭐

⚠️ NOTE ⚠️

the bridge you pass in should be the one closest to the encoder. don't just hand her any bridge and hope for the best, okay? the vibes have to be right. 🙈

💜 SEE ALSO 💜

the whole squad, in all her cross-referenced glory:

🌈 sign-off 🌈

this lil masterpiece lives in ./drivers/gpu/drm, and she was stamped October 2026. go forth and disable those bridges in reverse order, bestie — you're gonna slay. 💖✨🎀

📦 where this page comes from