scp_ipi_unlock(9)

💅 scp_ipi_unlock(9) — like, the Kernel API Manual, section 9, bestie ✨

okay so picture this: you're deep in kernel land, section 9 of the manual, and you need to let go of an IPI ID after you've been doing stuff with it. that's literally this function. it unlocks. it's giving "the responsible friend who closes the door after everyone leaves" 🫶

---

✨ NAME ✨

scp_ipi_unlock — unlock after operations of an IPI ID 💖

like, the aftercare function. you did your IPI ID operations, and now you unlock. periodt.

---

🌸 SYNOPSIS 🌸

void scp_ipi_unlock (struct mtk_scp *scp , u32 id );

that's the whole vibe. no return value, no drama, just void — it gives nothing back and honestly? iconic. 👑

---

🎀 ARGUMENTS 🎀

• scp — the mtk_scp structure. that's your main character right there, the whole struct, no cap.
• id — the IPI ID. a u32, bestie, so keep it unsigned and keep it 32 bits.

---

⚠️ NOTE ⚠️

This should not be used by drivers other than mtk_scp. 🚫

fr fr, do not come in here with some other driver thinking you can just call this. it's not for you. it's mtk_scp's function and mtk_scp's only. iykyk 💀

---

👀 SEE ALSO 👀

• the kernel file ./drivers/remoteproc/mtk_scp_ipi.c — go read the source, it's right there 🦋
• scp_ipi_register(9)
• scp_ipi_unregister(9)
• scp_ipi_lock(9) — the other half of this whole situation, lowkey obsessed with the symmetry 💅
• scp_ipi_send(9)

---

and that's the whole page, bestie!! 🌈 this came to you from ./drivers/remoteproc — the source, the version, the whole package — dated October 2026, and it's scp_ipi_unlock(9) forever and always. go forth, unlock responsibly, and slay ✨🎀💜