devm_drm_of_get_bridge(9)

📦 version 7.3.1, in nixpkgs unstable

✨ devm_drm_of_get_bridge(9) ✨

okay so bestie, welcome to the Kernel API Manual 💖 — this one's a little function with main character energy: devm_drm_of_get_bridge, and it's literally here to hand you the next bridge in the chain 🎀

🌸 NAME 🌸

devm_drm_of_get_bridge — return next bridge in the chain 🦋

✨ SYNOPSIS ✨

struct drm_bridge * devm_drm_of_get_bridge (struct device *dev , struct
       device_node *np , u32 port , u32 endpoint );

no cap, that's the whole signature — copy it exactly, she's particular about her types 💅

🎀 ARGUMENTS 🎀

  • dev — the device you're tying the bridge's lifetime to 🫶 (yes, devm = managed, she cleans up after herself, iconic)
  • np — the device tree node that's holding the encoder output ports 🌈
  • port — which port in that device tree node, fr fr
  • endpoint — which endpoint in that device tree node, iykyk ⭐

💜 DESCRIPTION 💜

so here's the vibe check: given a DT node's port and endpoint number, she finds the connected node and returns the associated bridge if there is one 😌 — or, plot twist, she creates and returns a drm panel bridge instance if a panel is connected instead 🍓 literally so flexible of her.

Returns a pointer to the bridge if successful, or an error pointer otherwise 💀 (so like, always check, bestie, please 🙈).

ok but the way that lifetime is tied to dev because of the devm_ prefix — that's the whole point, don't @ me 🔥

👑 SEE ALSO 👑

Kernel file ./drivers/gpu/drm/bridge/panel.c — and her whole friend group:

go read them, they ate 💅✨

and that's the page 🧚 shoutout to the source ./drivers/gpu/drm/bridge, Kernel API Manual edition, dated October 2026 — periodt, you're welcome, mwah 💖🎀🦋

📦 where this page comes from