drm_of_find_possible_crtcs(9)

💖 drm_of_find_possible_crtcs 💖

okay so bestie, welcome to the Kernel API Manual (section 9, yes we're in the kernel docs, we're fancy now 🎀). this one's a little function with a big job and honestly it's giving "quiet main character energy" — let's get into it 🦋

---

✨ NAME ✨

drm_of_find_possible_crtcs — find the possible CRTCs for an encoder port 💅

---

🌸 SYNOPSIS 🌸

uint32_t drm_of_find_possible_crtcs (struct drm_device *dev , struct
device_node *port );

---

🧚 ARGUMENTS 🧚

• dev — the DRM device, aka the whole vibe ✨
• port — the encoder port you wanna scan for endpoints 🔍

---

👑 DESCRIPTION 👑

so here's the tea ☕: this function scans, like, all the endpoints attached to a port — every single one, no skips 🫶 — locates the CRTCs those endpoints are attached to, and then generates the DRM mask of CRTCs that may be attached to this encoder. that's it, that's the whole flex 💅

it returns a uint32_t, which is your mask, bestie — the icon, the legend, the moment ⭐

ngl, if you wanna know what "port" and "endpoint" even mean in this context, go read the bindings, they're right here 👇

See https://github.com/devicetree-org/dt-schema/blob/main/dtschema/schemas/graph.yaml for the bindings 📎

---

🔥 SEE ALSO 🔥

• Kernel file ./drivers/gpu/drm/drm_of.c overview(9)
• drm_of_crtc_port_mask(9)
• drm_of_component_match_add(9)
• drm_of_component_probe(9)
• drm_of_get_panel_orientation(9)
• drm_of_find_panel_or_bridge(9)
• drm_of_lvds_get_dual_link_pixel_order(9)
• drm_of_lvds_get_dual_link_pixel_order_sink(9)
• drm_of_lvds_get_data_mapping(9)
• drm_of_get_data_lanes_count(9)
• drm_of_get_data_lanes_count_ep(9)
• drm_of_get_data_lanes_count_remote(9)
• drm_of_get_dsi_bus(9)

---

and that's the whole page, bestie, no cap 💀✨ this one lives over in ./drivers/gpu/drm and it's dated October 2026 — so yeah, mark your calendar, screenshot the page, tell your friends 🫶💖 see you in the next manpage, love u, bye! 🦋🌈🎀