drm_bridge_get_prev_bridge(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ drm_bridge_get_prev_bridge(9) ✨

okay bestie, so this is a page from the Kernel API Manual β€” the drm_bridge_get_prev_bridge er, function? yeah. section 9. come sit with me, we're gonna get through this together πŸ’…


🌸 NAME 🌸

drm_bridge_get_prev_bridge β€” literally just get the previous bridge in the chain πŸŽ€


πŸ¦‹ SYNOPSIS πŸ¦‹

struct drm_bridge * drm_bridge_get_prev_bridge (struct drm_bridge
*bridge );

πŸ’– ARGUMENTS πŸ’–

  • bridge β€” the bridge object, your little guy, your main character 🫢

✨ DESCRIPTION ✨

okay so first thing's first, and this is on you, not on the function: the caller is responsible for having a reference to bridge via drm_bridge_get or equivalent. like, get your reference first, bestie, don't come in here empty-handed πŸ™ˆ

this function leaves the refcount of bridge unmodified. it does not touch it. it is not about that. it is minding its own business ✨

but the refcount of the returned bridge? that one IS incremented, okay. so use drm_bridge_put when you're done with it β€” and yes, you have to, that's the whole vibe. no cap, don't leak it πŸ’€


πŸ”₯ RETURN πŸ”₯

the previous bridge in the chain, or NULL if bridge is the first. like if it's the first, there's nothing before it, sweetie, that's just how it is 😭


πŸ‘‘ SEE ALSO πŸ‘‘

Kernel file ./include/drm/drm_bridge.h

like, go read about the next bridge too, and the first and last in the chain, and the whole for-each situation β€” she's thorough, she's giving main character energy 🌈


⭐ gentle reminder: reference in, refcount untouched; bridge out, refcount up. put it back. periodt πŸ’œ

mwah πŸ’‹ this page lives in ./include/drm, October 2026 era, and it's called drm_bridge_get_prev_bridge(9) β€” go forth and chain responsibly, bestie πŸ§šβ€β™€οΈ

πŸ“¦ where this page comes from