pm_suspend_no_platform(9)

💤 pm_suspend_no_platform(9) — kernel API manual, bestie edition ✨

okay so real talk, this page is from the Kernel API Manual and it's about one tiny lil function that answers one giant question: is the kernel actually the boss of your devices' power states rn, or is the platform out here doing its own thing? 👑

---

🌸 NAME 🌸

pm_suspend_no_platform — check if the platform may change device power states. that's it. that's the whole job. 💅

---

✨ SYNOPSIS ✨

bool pm_suspend_no_platform (void );

it returns a bool, it takes void, it's giving very demure, very minimal. 🎀

---

🦋 ARGUMENTS 🦋

• void — no arguments. none. zero. it wants nothing from you, bestie, and honestly? iconic. 🫶

---

💖 DESCRIPTION 💖

so here's when you call it: during system-wide power management transitions to sleep states, or during the subsequent system-wide transitions back to the working state. like, it's a during-the-transition kinda function, iykyk. 😴➡️🖥️

it returns 'true' if the power states of devices remain under full control of the kernel throughout the system-wide suspend and resume cycle that's in progress. no cap, that's the whole vibe check.

and to spell it out (the original does, so I will too 🫡): "that is, if a device is put into a certain power state during suspend, it can be expected to remain in that state during resume."

so basically: did the kernel lock it in, and will it stay locked in? true = yes bestie, we're in control the whole ride. 🎢✨

---

🔥 SEE ALSO 🔥

the whole friend group, fr fr — check out the kernel file ./include/linux/suspend.h, plus:

• struct platform_suspend_ops(9)
• suspend_set_ops(9)
• pm_suspend_via_firmware(9)
• pm_resume_via_firmware(9)
• arch_suspend_disable_irqs(9)
• arch_suspend_enable_irqs(9)
• struct platform_hibernation_ops(9)
• pm_pr_dbg(9)

---

💀 heads up: this page lives in ./include/linux, dated October 2026, and it's the pm_suspend_no_platform(9) page from the Kernel API Manual. now go forth and vibe-check those power states, bestie 🌈🧚💜