pm_runtime_put_sync(9)

💖 pm_runtime_put_sync(9) 💖

Okay bestie, welcome to the Kernel API Manual, specifically the page for pm_runtime_put_sync(9). This is the function you call when you want to drop a device's usage counter and maybe let it go idle. Let's get into it, no cap.

✨ NAME ✨

pm_runtime_put_sync — Drop device usage counter and run "idle check" if 0. That's literally the whole vibe. Periodt.

🌸 SYNOPSIS 🌸

int pm_runtime_put_sync (struct device *dev );

🎀 ARGUMENTS 🎀

• dev — Target device. The main character. The device you're doing runtime PM on. iykyk

🦋 DESCRIPTION 🦋

So the way this works: you call pm_runtime_put_sync and it decrements the runtime PM usage counter of dev. If that counter turns out to be equal to 0, it invokes the "idle check" callback of dev and, depending on its return value, sets up autosuspend of dev or suspends it (depending on whether or not autosuspend has been enabled for it).

The runtime PM usage counter of dev remains decremented in all cases, even if it returns an error code. So like, no take-backs. The counter stays dropped. Slay.

💅 RETURN 💅

• 1 — Success. Usage counter dropped to zero, but device was already suspended. It's giving "already chilling" energy. Obsessed.
• 0 — Success. Plain and simple. Slay.
• -EINVAL — Runtime PM error. Something's off.
• -EACCES — Runtime PM disabled. Not today.
• -EAGAIN — Runtime PM usage counter became non-zero or Runtime PM status change ongoing. Try again later vibes.
• -EBUSY — Runtime PM child_count non-zero. It's busy with its kids, okay?
• -EPERM — Device PM QoS resume latency 0. That's the whole note.
• -ENOSYS — CONFIG_PM not enabled. Other values and conditions for the above values are possible as returned by Runtime PM suspend callbacks. The config said no, bestie.

🌈 SEE ALSO 🌈

Kernel file ./include/linux/pm_runtime.h — and honestly a whole friend group of functions. Let's list them all because we're thorough bestie:

• pm_suspend_ignore_children(9)
• pm_runtime_get_noresume(9)
• pm_runtime_put_noidle(9)
• pm_runtime_suspended(9)
• pm_runtime_active(9)
• pm_runtime_status_suspended(9)
• pm_runtime_enabled(9)
• pm_runtime_blocked(9)
• pm_runtime_has_no_callbacks(9)
• pm_runtime_mark_last_busy(9)
• pm_runtime_is_irq_safe(9)
• pm_runtime_idle(9)
• pm_runtime_suspend(9)
• pm_runtime_autosuspend(9)
• pm_runtime_resume(9)
• pm_request_idle(9)
• pm_request_resume(9)
• pm_request_autosuspend(9)
• pm_runtime_get(9)
• pm_runtime_get_sync(9)
• pm_runtime_resume_and_get(9)
• pm_runtime_put(9)
• __pm_runtime_put_autosuspend(9)
• pm_runtime_put_autosuspend(9)
• pm_runtime_put_sync_suspend(9)
• pm_runtime_put_sync_autosuspend(9)
• pm_runtime_set_active(9)
• pm_runtime_set_suspended(9)
• pm_runtime_disable(9)
• pm_runtime_use_autosuspend(9)
• pm_runtime_dont_use_autosuspend(9)

Cute sign-off: this page lives in ./include/linux and the date on it is October 2026. Also the manual page name is pm_runtime_put_sync(9) just so you know. Bye bestie! 💖✨🫶