pm_runtime_use_autosuspend(9)

💖 pm_runtime_use_autosuspend(9) 💖

okay so this lil icon is straight out of the Kernel API Manual, and it is literally the “yes bestie, autosuspend is allowed” switch for a device. let’s go ✨

🌸 NAME 🌸

pm_runtime_use_autosuspend — Allow autosuspend to be used for a device. periodt 💅

🦋 SYNOPSIS 🦋

void pm_runtime_use_autosuspend (struct device *dev );

🎀 ARGUMENTS 🎀

• dev — Target device. that’s the one this whole autosuspend moment is for 👑

💫 DESCRIPTION 💫

okay so this function allows the runtime PM autosuspend mechanism to be used for dev whenever requested. if it isn’t allowed, “autosuspend” will be handled as direct runtime-suspend for it. no cap, that’s the whole vibe 🫶

⚠️ NOTE ⚠️

bestie, it is important to undo this with pm_runtime_dont_use_autosuspend at driver exit time — unless your driver initially enabled pm_runtime with devm_pm_runtime_enable (which handles it for you). do not leave this hanging, fr fr 😭

🌈 SEE ALSO 🌈

the kernel file is ./include/linux/pm_runtime.h, and the whole squad is:

• 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(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_dont_use_autosuspend(9)

okay that’s a wrap, bestie 🎀 source/version check: ./include/linux; date check: October 2026. slay and stay suspended responsibly 💖✨💜