find_cxl_port_by_uport(9)

💅 find_cxl_port_by_uport(9) 💅

okay so bestie, welcome to the Kernel API Manual — this is find_cxl_port_by_uport, and she's literally the friend who introduces you to the right port at the party 🎀

---

✨ NAME ✨

find_cxl_port_by_uport — finds you a CXL port device companion</> 🫶 (yes, companion. it's giving matchmaker.)

---

🌸 SYNOPSIS 🌸

struct cxl_port * find_cxl_port_by_uport (struct device *uport_dev );

that's it. one arg. she's low maintenance 💅

---

🦋 ARGUMENTS 🦋

• uport_dev — the device that acts as a switch</> or endpoint</> in the CXL hierarchy. like, that's her whole job description fr fr.

---

💖 DESCRIPTION 💖

so here's the tea 🍓: in the case of endpoint ports, recall that port->uport_dev points to a 'struct cxl_memdev' device. so the uport_dev argument is the parent device of the

(yeah bestie the original sentence just trails off like that at "of the" — not me, i'm just reporting what the page says 😭)

---

and the actual mechanic, no cap: the function takes a device reference on the port device. which means — and this is the important part, do NOT skip it — the caller should do a put_device when done. 🫶

⚠️ for real though: reference held → you owe a put_device. that's the contract. don't be that person who leaves a reference dangling, it's not cute 🙈

---

🌈 SEE ALSO 🌈

Kernel file ./drivers/cxl/core/port.c

then the whole squad, in order 👑

• cxl core(9)
• devm_cxl_add_port(9)
• devm_cxl_add_dport(9)
• devm_cxl_add_rch_dport(9)
• cxl_add_ep(9)
• find_cxl_port_by_dport(9)
• cxl_decoder_init(9)
• cxl_root_decoder_alloc(9)
• cxl_switch_decoder_alloc(9)
• cxl_endpoint_decoder_alloc(9)
• cxl_decoder_add_locked(9)
• cxl_decoder_add(9)
• __cxl_driver_register(9)
• cxl_endpoint_get_perf_coordinates(9)

---

and that's the whole page, bestie!! 🧚✨ this iconic little number lives in ./drivers/cxl/core, dated October 2026, and it's filed under find_cxl_port_by_uport(9) — go forth and put_device, ily, mwah 💜🎀