cxl_decoder_add(9)

cxl_decoder_add(9) 💖

okay bestie, welcome to the Kernel API Manual entry for cxl_decoder_add(9) — yes, the (9) stays, we don’t erase the lore 💅. This is the page about adding a decoder with targets, and it’s literally the unlocked sibling situation. 🎯

✨ NAME ✨

cxl_decoder_add — add a decoder with targets. 🎀

🌸 SYNOPSIS 🌸

int cxl_decoder_add (struct cxl_decoder *cxld );

🦋 ARGUMENTS 🦋

• cxld — the cxl decoder allocated by cxl_<type>_decoder_alloc. That’s the decoder you’re bringing to the function, bestie 🫶.

💅 DESCRIPTION 💅

So this is the unlocked variant of cxl_decoder_add_locked. That’s the whole tea ☕✨. For the actual details, see cxl_decoder_add_locked — this page is basically pointing you there with main-character energy 👑.

🔥 CONTEXT 🔥

Process context. It takes and releases the device lock of the port that owns cxld. So yes, locking is part of the vibe, and it’s specifically the port that owns cxld doing the lock thing 💅.

🌈 SEE ALSO 🌈

• Kernel file: ./drivers/cxl/core/port.c
• 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)
• 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_driver_register(9)
• cxl_endpoint_get_perf_coordinates(9)

source/version tea: ./drivers/cxl/core 🌟 date: October 2026 🎀 page name: cxl_decoder_add(9) — and that’s the sign-off, mwah 💋✨