pm_runtime_force_resume(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– pm_runtime_force_resume(9) πŸ’–

okay so this is a page from the Kernel API Manual, and bestie, we're about to make a device wake up on purpose. 🫢


✨ NAME ✨

pm_runtime_force_resume β€” literally forces a device into resume state if it needs it, no cap.


🌸 SYNOPSIS 🌸

int pm_runtime_force_resume (struct device *dev );

πŸŽ€ ARGUMENTS πŸŽ€

  • dev β€” the device you're waking up. your main character. πŸ¦‹

πŸ‘‘ DESCRIPTION πŸ‘‘

okay so here's the vibe check on what this function expects before you even call it. two acceptable situations, pick one:

  • pm_runtime_force_suspend already put the device into a low-power state before you called this, or
  • the device was already runtime-suspended before the preceding system-wide suspend transition, and it just stayed in suspend the whole time during that transition. πŸ’€

then the function does its thing: whatever actions pm_runtime_force_suspend carried out β€” or that a runtime suspend in general carried out β€” get reversed, and the device is brought back into full power. πŸ”₯

but only if it's expected to be used on system resume, bestie. and that's true when:

  • its needs_force_resume flag is set, or
  • its smart_suspend flag is set and its runtime PM status is "active".

in other cases? the resume is deferred to be managed via runtime PM instead. lowkey handing it off. πŸ’…

ngl, the typical move here is invoking this function from a system resume callback. that's the moment. ⭐

πŸ’œ SEE ALSO πŸ’œ

  • Kernel file ./drivers/base/power/runtime.c β€” go read the source, it ate πŸ‘‘

and the whole friend group, fr fr:


🧚 okay that's the page!! it lives in ./drivers/base/power, it's part of the Kernel API Manual, and it was dated October 2026 β€” so yeah, timestamped and iconic. periodt. πŸ’…βœ¨πŸŒˆ

πŸ“¦ where this page comes from