__pm_runtime_resume(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… __pm_runtime_resume β€” Kernel API Manual ✨

okay so bestie, welcome to the Kernel API Manual, and today's main character is __pm_runtime_resume(9) β€” literally the entry point for runtime resume operations. yes. THE entry point. πŸŽ€


✨ SYNOPSIS ✨

int __pm_runtime_resume (struct device *dev , int rpmflags );

🫢 ARGUMENTS 🫢

  • dev β€” the device you wanna resume. that's your girl. that's who we're waking up πŸ’–
  • rpmflags β€” the flag bits. lil switches that change how the whole thing goes down ✨

πŸ”₯ DESCRIPTION πŸ”₯

okay so here's the tea β˜• β€” if the RPM_GET_PUT flag is set, you increment the device's usage count first. then you carry out a resume, and it can be synchronous or asynchronous β€” your call, based on those flags, iykyk πŸ’…

and the important part, no cap: this routine may be called in atomic context if the RPM_ASYNC flag is set, or if pm_runtime_irq_safe has been called. that's the vibe check right there πŸ‘‘

🫢 fr fr, remember that atomic-context bit β€” it's giving "read the flags before you do anything unhinged."

🌈 SEE ALSO 🌈

Kernel file ./drivers/base/power/runtime.c 🌸

and the whole bestie squad, all of them, in this exact order, slay:


and that's the whole page bestie, go wake up some devices πŸ’œπŸ¦‹

sign-off szn πŸŽ€ β€” this cutie lives in ./drivers/base/power, dated October 2026, and it's literally the __pm_runtime_resume(9) page, periodt. mwah πŸ’‹βœ¨

πŸ“¦ where this page comes from