scmi_protoco...vice_request(9)

💖 scmi_protoco...vice_request(9) 💖

okay so bestie, welcome to the kernel API manual for scmi_protoco...vice_request(9) — yes the title is literally truncated like that, that's just how it is, we don't question it ✨

---

🎀 NAME 🎀

scmi_protocol_device_request — a little helper that lets you request a device, and honestly? it's giving "personal assistant for SCMI drivers" 💅

---

✨ SYNOPSIS ✨

int scmi_protocol_device_request(const struct scmi_device_id *id_table);

that's the whole signature, no notes, she's simple and she serves 💖

---

🌸 ARGUMENTS 🌸

• id_table — a protocol/name pair descriptor for the device you want to be created. like a little name tag 🏷️ for the device you're asking for.

---

🦋 DESCRIPTION 🦋

okay so here's the vibe: this helper lets an SCMI driver request specific devices, identified by id_table, to be created for each active SCMI instance. one request, all your active instances, no cap 🫶

🚨 THE BIG RULE 🚨 the requested device name MUST NOT already exist for this protocol. like, do not come in here with a name that's already taken, bestie, that is not the move 😭

so what happens at first: the freshly requested id_table gets annotated in the IDR table scmi_requested_devices. then, the requested device is advertised to any registered party via the scmi_requested_devices_nh notification chain. iconic behavior honestly 👑

---

🔥 RETURN 🔥

0 on Success — that's it, that's the return value, zero equals slay 💀✨

---

🌈 SEE ALSO 🌈

• Kernel file ./drivers/firmware/arm_scmi/bus.c
• scmi_protocol_device_unrequest(9)
• scmi_device_create(9)

---

and that's the whole page bestie, you ate that 💅🌸

sign-off time: this was the kernel API manual for scmi_protoco...vice_request(9), coming at you from ./drivers/firmware/arm_scmi, dated October 2026 — periodt 🎀💜