drm_bridge_get_next_bridge(9)

💅 drm_bridge_get_next_bridge(9) — Kernel API Manual, bestie edition ✨

okay so this is <pink>drm_bridge_get_next_bridge</pink> from the Kernel API Manual, and it's literally the glow-up you need when you're stuck in a bridge chain and gotta find out who's next. no cap, it's giving "linked list but make it ✨graphics✨". let's get into it 🎀

---

🌸 NAME 🌸

drm_bridge_get_next_bridge — get the next bridge in the chain 🦋

like, the next one. the one after this one. you get it. 💜

---

✨ SYNOPSIS ✨

struct drm_bridge * drm_bridge_get_next_bridge (struct drm_bridge
*bridge );

yep that's the whole thing, she's compact and iconic 💅

---

🎀 ARGUMENTS 🎀

• bridge — bridge object 🫶 (that's your starting point, bestie — the bridge whose neighbor you're tryna find)

---

💖 DESCRIPTION 💖

okay so first things first, and this part is on you, not on the function: the caller is responsible of having a reference to bridge via drm_bridge_get or equivalent. like, you gotta come correct. have your ref, don't be out here raw-dogging pointers 😭

now the cute part: this function leaves the refcount of bridge unmodified. she does not touch it. she does not bump it. she does not drop it. she's a respectful queen 👑 and she minds her business.

BUT — and this is the plot twist — the refcount of the returned bridge is incremented 🔥. so the bridge she hands you back? that one's now your problem. you own a ref. slay, but like, responsibly.

so use drm_bridge_put when you're done with it. periodt. don't leave it hanging, that's a leak and leaks are not the vibe 💀

---

⭐ RETURN ⭐

the next bridge in the chain after bridge 🌈 — or NULL if bridge is the last one. that's it, that's the end of the line, no more bridges, go home 🧚

---

🦋 SEE ALSO 🦋

bestie you are not gonna believe how much lore there is. the kernel file is ./include/drm/drm_bridge.h and here's the whole friend group 💖

• 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_prev_bridge(9) — yes there's a prev one, she's the main character's sister 🙈
• drm_bridge_chain_get_first_bridge(9)
• drm_bridge_chain_get_last_bridge(9)
• drm_for_each_bridge_in_chain(9)
• drm_for_each_bridge_in_chain_from(9)

lowkey an entire friend group, iykyk 🌸

---

ngl there's nothing dangerous here — just don't forget the drm_bridge_put or the refcount will haunt you forever 😭

---

and that's the page, bestie!! 🫶 this one lives under ./include/drm in the Kernel API Manual, dated October 2026, and the header/footer both just say drm_bridge_get_next_bridge(9) again because the kernel likes repeating itself 💀 mwah, go touch some struct drm_bridge 💜✨