scmi_request...l_transition(9)

💅 scmi_request_forceful_transition(9) 💅

okay so bestie, we're in the Kernel API Manual today and this one is spicy — welcome to the page for scmi_request_forceful_transition, no cap.

---

✨ NAME ✨

scmi_request_forceful_transition — request a forceful SystemPower transition 🫶

Like, not the polite one. The forceful one. iykyk.

---

🌸 SYNOPSIS 🌸

void scmi_request_forceful_transition(struct scmi_syspower_conf *sc);

the way that it returns void and takes exactly one pointer… she's lowkey minimal and I respect it 💅

---

🎀 ARGUMENTS 🎀

• sc — a reference to the configuration data 💖 (this is the struct that tells the call what it's working with, periodt)

---

🦋 DESCRIPTION 🦋

so what does she do? she initiates the required SystemPower transition without involving userspace at all. no notifier round-trip, no asking permission, no "hey bestie can you handle this" — she just triggers the action right there at the kernel level, after issuing an emergency sync.

key deets, fr fr:

• the transition happens without involving userspace — kernel-side only, main character energy 👑
• an emergency sync gets issued first 🔥
• the sync happens if possible at all — that's the actual caveat, so don't come for me, I'm just the messenger 😭

heads up: this is the forceful flavour. if you were looking for the gentle one, that's a whole different function (see below 👀).

---

🌈 SEE ALSO 🌈

• the kernel file ./drivers/firmware/arm_scmi/scmi_power_control.c — go read the source, it's giving ✨
• struct scmi_syspower_conf(9) — the struct that sc points at 💜
• scmi_reboot_notifier(9)
• scmi_request_graceful_transition(9) — the polite sibling 🎀
• scmi_userspace_notifier(9) — the one that actually talks to userspace 🙈

---

⭐ sign-off ⭐

that's the whole page, bestie! 🧚 this little beauty lives in ./drivers/firmware/arm_scmi and the version we're repping is dated October 2026 — go forth, trigger your transitions, and stay iconic 💖✨🍓