pm_runtime_resume_and_get(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ pm_runtime_resume_and_get(9) ✨

okay bestie, welcome to the Kernel API Manual πŸ’– you're literally about to learn pm_runtime_resume_and_get, and honestly? she's that girl. let's get into it 🫢


🌸 NAME 🌸

pm_runtime_resume_and_get β€” bump up the usage counter of a device and resume it. that's it, that's the whole vibe. counter goes up, device wakes up, main character energy πŸ”₯


✨ SYNOPSIS ✨

int pm_runtime_resume_and_get (struct device *dev );

like, no cap, that's the whole signature. int in, int out, struct device pointer goes in the middle πŸ’…


πŸŽ€ ARGUMENTS πŸŽ€

  • dev β€” the target device. your lil guy. the one you're doing all this for πŸ¦‹

πŸ’œ DESCRIPTION πŸ’œ

so here's the tea, bestie πŸ“: this function resumes dev synchronously, and only if that resume actually goes through does it increment the device's runtime PM usage counter. it's giving "wake up bestie, then lock in."

the return value is lowkey simple:

  • returns 0 if the runtime PM usage counter of dev has been incremented βœ…
  • returns a negative error code otherwise 😭 (translation: it did not pan out, don't celebrate yet)

periodt. that's the contract πŸ’€ no hidden drama, no extra steps, just "resume, then bump the counter, or give me a negative number."


🌈 SEE ALSO 🌈

okay this is the part where the friend group gets long, and every single one of them matters, so we're listing all of them fr fr πŸ‘‘


and that's the whole page, bestie, you ate that πŸ’…βœ¨

cute lil sign-off before you go 🧚: this one lives in ./include/linux, and the footer was stamped October 2026 β€” so like, mark your calendar, she's dated and she knows it πŸ’–πŸŽ€

πŸ“¦ where this page comes from