pm_runtime_suspend(9)

📦 version 7.3.1, in nixpkgs unstable

🌸 NAME 🌸

okay so bestie, welcome to pm_runtime_suspend(9) from the Kernel API Manual — the synchronous device-suspend moment, and yes she’s iconic. This function suspends a device synchronously, meaning it doesn’t just send the vibe and bounce; the suspend happens and the call deals with it. 💅

✨ SYNOPSIS ✨

int pm_runtime_suspend (struct device *dev );

🎀 ARGUMENTS 🎀

  • dev — target device. The device you’re trying to suspend, periodt. 🎯

🔥 RETURN 🔥

like, the return value is basically the mood ring of this call, and here’s the full lineup:

  • 1 — success; the device was already suspended. she was already napping, iconic. 😴
  • 0 — success.
  • -EINVAL — Runtime PM error.
  • -EACCES — Runtime PM disabled.
  • -EAGAIN — Runtime PM usage counter non-zero or Runtime PM status change ongoing.
  • -EBUSY — Runtime PM child_count non-zero.
  • -EPERM — Device PM QoS resume latency 0.
  • -ENOSYS — CONFIG_PM not enabled.
also, “Other values and conditions for the above values are possible as returned by Runtime PM suspend callbacks.” so don’t come for me if a callback hands back a different number, okay? 😭

🦋 SEE ALSO 🦋

Kernel file ./include/linux/pm_runtime.h — and the whole bestie squad:

signed, sealed, delivered by the Kernel API Manual crew — source ./include/linux, dated October 2026, page pm_runtime_suspend(9) 💖✨

📦 where this page comes from