drm_for_eac...n_chain_from(9)

💖 drm_for_each_bridge_in_chain_from(9) 💖

okay bestie, welcome to the Kernel API Manual — this page is literally all about drm_for_each_bridge_in_chain_from, and it’s giving “walk the bridge chain starting from one specific bridge” energy. The vibe check: start at first_bridge, iterate through the encoder chain, and let this iterator handle the bridge-reference gets/puts plus the encoder chain mutex lock so nobody edits the chain mid-loop. Iconic behavior, no cap. 💅

🌸 NAME 🌸

drm_for_each_bridge_in_chain_from — iterate over all bridges starting from the given bridge. Periodt. 💖

✨ SYNOPSIS ✨

drm_for_each_bridge_in_chain_from (first_bridge , bridge );

🎀 ARGUMENTS 🎀

• first_bridge — the bridge to start from. This is your main character starting point, bestie. ✨
• bridge — a bridge pointer updated to point to the current bridge at each iteration. That’s the one that changes as you loop, lowkey the moving part of the whole situation. 🦋

🦋 DESCRIPTION 🦋

Okay so here’s the tea: iterate over all bridges in the encoder chain starting from first_bridge, included. No cap, first_bridge is part of the iteration too. 💅

While it’s iterating, it automatically gets/puts the bridge reference, and it locks the encoder chain mutex to prevent chain modifications while iterating. So yes, it’s handling the bridge-reference gets/puts choreography and the chain-lock situation for you. Obsessed. 😭

💜 SEE ALSO 💜

Kernel file: ./include/drm/drm_bridge.h — the source-file link-up. 🌈

• enum drm_bridge_attach_flags(9)
• struct drm_bridge_funcs(9)
• struct drm_bridge_timings(9)
• enum drm_bridge_ops(9)
• struct drm_bridge(9)
• devm_drm_bridge_alloc(9)
• drm_bridge_get_current_state(9)
• drm_bridge_get_next_bridge(9)
• drm_bridge_get_prev_bridge(9)
• drm_bridge_chain_get_first_bridge(9)
• drm_bridge_chain_get_last_bridge(9)
• drm_for_each_bridge_in_chain(9)

xoxo, from the ./include/drm source corner of the Kernel API Manual, dated October 2026, section (9) — slay and happy iterating, bestie 💖🎀🦋