pm_runtime_is_irq_safe(9)

🦋 pm_runtime_is_irq_safe(9) 🦋

okay bestie, welcome to the Kernel API Manual group chat 💖 — today's main character is pm_runtime_is_irq_safe(9), and she's here to answer one very specific runtime PM question. no cap.

✨ NAME ✨

pm_runtime_is_irq_safe — check if runtime PM can work in interrupt context. literally the vibe check for IRQ-context runtime PM energy 💅

🌸 SYNOPSIS 🌸

bool pm_runtime_is_irq_safe (struct device *dev );

🎀 ARGUMENTS 🎀

• dev — target device. that's the one u pass in, bestie 🫶

💖 DESCRIPTION 💖

So here's the tea: it returns true if dev has been marked as an "IRQ-safe" device (with respect to runtime PM) 💅. In which case, its runtime PM callbacks can be expected to work correctly when invoked from interrupt handlers. periodt.

🔥 SEE ALSO 🔥

The kernel file ./include/linux/pm_runtime.h is the source-y bestie for this one 👑. also go peek at:

• 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_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_use_autosuspend(9)
• pm_runtime_dont_use_autosuspend(9)

mwah 💋 — sourced from ./include/linux, with the manual's date/version showing October 2026. go be IRQ-safe, bestie 🧚💜