drm_bridge_detect(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… drm_bridge_detect(9) β€” no like literally the Kernel API Manual bestie

okay so welcome to drm_bridge_detect(9), which is a page from the Kernel API Manual and it's basically asking one iconic little question: is anything actually plugged into this bridge's output or nah? πŸ¦‹


✨ NAME ✨

drm_bridge_detect β€” check if anything is attached to the bridge output


πŸŽ€ SYNOPSIS πŸŽ€

enum drm_connector_status drm_bridge_detect (struct drm_bridge *bridge ,
struct drm_connector *connector );

🌸 ARGUMENTS 🌸

  • bridge β€” the bridge control structure, she's the main character here πŸ‘‘
  • connector β€” the attached connector, tagging along for the ride

πŸ’– DESCRIPTION πŸ’–

So here's the vibe check πŸ”: if the bridge supports output detection β€” like, as reported by the DRM_BRIDGE_OP_DETECT bridge ops flag β€” then it calls drm_bridge_funcs.detect for the bridge and hands you back the connection status. Slay. ✨

Otherwise it just returns connector_status_unknown. That's it, that's the whole tea. 🫢


⭐ RETURN ⭐

The detection status on success πŸ’« β€” or connector_status_unknown if the bridge doesn't support output detection at all (ngl, sometimes that's just how it is 😭).


🌈 SEE ALSO 🌈

okay bestie, buckle up, this list is long and honestly kind of iconic πŸ”₯ β€” go read all of these:

fr fr, that's a lot of cross-references. drink some water before you click through them all πŸ’§

and that's the page babes πŸ’… this little gem lives over in ./drivers/gpu/drm, it's dated October 2026, and it's literally called drm_bridge_detect(9) β€” go off, king πŸ‘‘βœ¨πŸ’œ

πŸ“¦ where this page comes from