cxl_dev_state_identify(9)

okay so bestie, welcome to the cxl_dev_state_identify(9) page from the Kernel API Manual 💖 this one is short, sweet, and very “send the command, get the data, slay.”

🌸 NAME 🌸

cxl_dev_state_identify — sends the IDENTIFY command to the device. no cap, that’s the whole name vibe ✨

🎀 SYNOPSIS 🎀

int cxl_dev_state_identify (struct cxl_memdev_state *mds );

🦋 ARGUMENTS 🦋

• mds — the driver data for the operation. that’s literally what it is, bestie 💅

🔥 RETURN 🔥

It gives you 0 if identify was executed successfully or media not ready. iconic zero behavior, fr fr.

✨ DESCRIPTION ✨

This will dispatch the identify command to the device, and on success it populates structures to be exported to sysfs. so like: send the thing, and if it works, fill in the structures that get exported to sysfs 🫶

💜 SEE ALSO 💜

• Kernel file ./drivers/cxl/core/mbox.c
• cxl mbox(9)
• cxl_internal_send_cmd(9)
• cxl_payload_from_user_allowed(9)
• cxl_validate_cmd_from_user(9)
• handle_mailbox_cmd_from_user(9)
• cxl_walk_cel(9)
• cxl_enumerate_cmds(9)
• cxl_mem_get_event_records(9)
• cxl_mem_get_partition_info(9)
• cxl_mem_sanitize(9)

mwah 💋 this little page lives in ./drivers/cxl/core, dated October 2026, and it’s the cxl_dev_state_identify(9) manual page — periodt 🌈