scmi_protoco...ce_unrequest(9)

💅 scmi_protocol_device_unrequest(9) — like, the Kernel API Manual, bestie 🎀

okay so this is a page from the Kernel API Manual (scmi_protoco...ce_unrequest(9), yes the title got cut off, she's mysterious like that ✨) and it's literally all about politely telling a device to gtfo. let's get into it 🫶

---

✨ NAME ✨

scmi_protocol_device_unrequest — the helper that unrequests a device 💫 (yes that's the whole name, she's a "helper", she helps, that's her job)

---

🌸 SYNOPSIS 🌸

void scmi_protocol_device_unrequest (const struct scmi_device_id
*id_table );

no return value, no drama, just vibes and a pointer 💅

---

🦋 ARGUMENTS 🦋

• id_table — a protocol/name pair descriptor for the device that's about to get unrequested 👋 like, this is the lil ID card you hand over so the kernel knows exactly which device you're breaking up with.

---

🔥 DESCRIPTION 🔥

okay so here's the tea ☕ — the unrequested device, the one described by the id_table you passed in, gets handled in two very iconic steps:

1. first she gets removed from the IDR scmi_requested_devices 🗑️ like, gone from the list, no cap
2. then that removal gets advertised to any registered party via the scmi_requested_devices_nh notification chain 📣✨

so basically: remove, then announce. she doesn't just leave, she leaves loudly. main character energy fr fr 👑

ngl this is the "the way that she removes herself from the IDR and tells everyone" of kernel functions 💀 iconic behaviour only

---

🌈 SEE ALSO 🌈

• Kernel file ./drivers/firmware/arm_scmi/bus.c — go read the source bestie 📖
• scmi_protocol_device_request(9) — the opposite vibe, the requesting one 💖
• scmi_device_create(9) — device creation, the origin story 🐣

---

and that's the whole page!! mwah 💋 this came to you from ./drivers/firmware/arm_scmi, dated October 2026, still signing off as scmi_protoco...ce_unrequest(9) because she refuses to spell out her full name 🎀✨ love that for her 🫶