drm_connecto...nd_by_fwnode(9)

📦 version 7.3.1, in nixpkgs unstable

🌈 drm_connector_find_by_fwnode — bestie edition 🌈

okay so this page lives in the Kernel API Manual (yes, the man page title legit renders as drm_connecto...nd_by_fwnode(9) because someone let the truncation run wild 😭 — the actual function is drm_connector_find_by_fwnode), and it's about finding a drm_connector by its fwnode. let's get into it 💅

✨ NAME ✨

drm_connector_find_by_fwnode — find a connector based on the associated fwnode 🦋

✨ SYNOPSIS ✨

struct drm_connector * drm_connector_find_by_fwnode (struct
fwnode_handle *fwnode );

like, that's the whole vibe. one arg in, one connector pointer out 💖

✨ ARGUMENTS ✨

  • fwnode — the fwnode you want the matching drm_connector for 🎀 that's it, that's the input.

✨ DESCRIPTION ✨

so this function literally looks up a drm_connector based on its associated fwnode. that's the whole job. no cap 💅

and here's the part you cannot skip, bestie: when a connector is found, a reference to the connector is returned. so the caller must call drm_connector_put to release that reference when it's done with the connector. 🫶 don't ghost the refcount, she will remember 😭

✨ RETURN ✨

a reference to the found connector, or an ERR_PTR. 🔥 (so like, vibe check the return value before you go dereferencing things, fr fr.)

✨ SEE ALSO ✨

okay bestie, this list is long — she ate and left no crumbs 👑. everything below is exactly what's referenced, in order, no skips:

💀 yes, standard connector properties(9) shows up twice in there. that's not me being messy, that's canon. don't come for me, come for the source. 🙈

✨ that's the whole page, bestie ✨

this one's served up from ./drivers/gpu/drm, stamped October 2026, in the Kernel API Manual — go forth and drm_connector_put responsibly 🎀💜🫶

📦 where this page comes from