devm_drm_bridge_alloc(9)

✨ devm_drm_bridge_alloc(9) ✨

okay bestie, so we're in the Kernel API Manual today and the vibe is very "managed device resources, but make it fashion" 💅 this is devm_drm_bridge_alloc, and she's literally here to allocate and initialize a bridge for you 🎀

---

🦋 NAME 🦋

devm_drm_bridge_alloc — allocate and initialize a bridge 💖

---

🌸 SYNOPSIS 🌸

devm_drm_bridge_alloc (dev , type , member , funcs );

like, four args, no drama, moving on 🫶

---

🧚 ARGUMENTS 🧚

• dev — the struct device of the bridge device 👑 that's your device, that's who she belongs to
• type — the type of the struct which contains struct drm_bridge 🍓 yes, the container struct, the one hiding the drm_bridge inside it
• member — the name of the drm_bridge within type 🔥 literally just the member name, so she can find it in there
• funcs — callbacks for this bridge ⭐ this is where you hand over the behavior, no cap

---

💜 DESCRIPTION 💜

so here's the tea ☕ the reference count of the returned bridge is initialized to 1. one. that's it, that's the starting number 🔢

and the iconic part? that reference will be automatically dropped via devm (by calling drm_bridge_put) when dev is removed 🌈 like, you don't gotta do a thing, she cleans up after herself, main character energy fr fr 💅

ngl this is the whole reason you use the devm_ version — the cleanup is handled for you when dev goes away, so don't go manually dropping what devm is gonna drop 🙈

---

🔥 RETURN 🔥

Pointer to new bridge, or ERR_PTR on failure 💀 yes, ERR_PTR — so check that thing, bestie, don't just raw-dog the pointer 😭

---

🎀 SEE ALSO 🎀

Kernel file ./include/drm/drm_bridge.h, plus the whole squad 👑:

• 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)
• 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)
• drm_for_each_bridge_in_chain_from(9)

iykyk 🦋 go read the header, it's giving essential context ✨

---

and that's the whole page, bestie 🫶 this lil gem lives in ./include/drm, dated October 2026, and it's part of the Kernel API Manual — mwah, slay, periodt 💖🎀🌟