drm_bridge_...first_bridge(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… drm_bridge_chain_get_first_bridge β€” ok bestie, let's talk bridges

So this page lives in the Kernel API Manual (yes, the kernel has a whole manual, she's that girl) and it's literally called drm_bridge_chain_get_first_bridge, which, iykyk, is a whole mouthful but also kind of iconic. Title's truncated up top as drm_bridge_...first_bridge(9) because even manpage headers have to keep it cute and short sometimes ✨


πŸŽ€ NAME πŸŽ€

drm_bridge_chain_get_first_bridge β€” get the first bridge in the chain 🫢


✨ SYNOPSIS ✨

struct drm_bridge * drm_bridge_chain_get_first_bridge (struct
drm_encoder *encoder );

Okay so like, one function, one argument, returns a bridge pointer. Slay.


🌸 ARGUMENTS 🌸

  • encoder β€” an encoder object. That's it. That's the whole vibe. πŸ’…

πŸ”₯ DESCRIPTION πŸ”₯

So here's the thing you actually need to remember, bestie: the refcount of the returned bridge is incremented. Like, it comes back with a lil extra hold on it, and you are personally responsible for that.

When you're done with it, call drm_bridge_put. Periodt. Don't just ghost it, that's how you leak things and we don't do that here πŸ™ˆ


⭐ RETURN ⭐

You get the first bridge in the chain πŸ’– … or NULL if encoder has no bridge attached to it. No bridge, no vibe check, you just get NULL. 😭


πŸ¦‹ SEE ALSO πŸ¦‹

This is the part where the kernel says "now go read these twelve other pages," and honestly? Respect. Main character energy all around:


🧚 Also hi, friendly reminder from the group chat: that refcount you got handed? That's yours now. drm_bridge_put it when you're done. No cap.

🌈 That's the whole page, bestie β€” brought to you straight out of ./include/drm, from the Kernel API Manual, dated October 2026. Go get that first bridge. πŸ‘‘πŸ’œ

πŸ“¦ where this page comes from