cxl_add_ep(9)

✨ cxl_add_ep 💅

okay so bestie, welcome to the cxl_add_ep(9) page — this is a Kernel API Manual moment, and honestly it's a short one but it matters 🎀

---

🌸 NAME 🌸

cxl_add_ep — register an endpoint's interest in a port 👑

---

✨ SYNOPSIS ✨

int cxl_add_ep (struct cxl_dport *dport , struct device *ep_dev );

---

🦋 ARGUMENTS 🦋

• dport — the dport that routes to ep_dev 🛣️ like this is the port doing the routing, okurrr
• ep_dev — device representing the endpoint 📟 literally the endpoint in device form

---

💖 DESCRIPTION 💖

so here's the tea ☕ — intermediate CXL ports get scanned based on the arrival of endpoints. yes, arrival, like they're showing up to the function 🎀

and when those endpoints depart? the port can be destroyed once all the endpoints that care about that port have been removed 💀 it's giving "you can leave once everyone who loves you is gone" ngl. main character port energy fr fr 🫶

---

🌈 SEE ALSO 🌈

Kernel file ./drivers/cxl/core/port.c — plus the whole friend group, iykyk:

• cxl core(9)
• devm_cxl_add_port(9)
• devm_cxl_add_dport(9)
• devm_cxl_add_rch_dport(9)
• find_cxl_port_by_dport(9)
• find_cxl_port_by_uport(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)

---

💅 reminder: this page lives under ./drivers/cxl/core — that's the address, bestie, don't lose it

---

and that's the whole page, periodt 🧚✨ slay — this one came from the ./drivers/cxl/core source, dated October 2026, and it's the cxl_add_ep(9) page, mwah 💜🎀