device_resume_noirq(9)

✨ device_resume_noirq(9) ✨

okay so bestie, welcome to the <pink>Kernel API Manual</pink> 💖 we're literally in device_resume_noirq(9) territory today and it's giving "power management main character energy" fr fr 🫶

---

🌸 NAME 🌸

device_resume_noirq — run a "noirq resume" callback for a given device. that's it, that's the whole vibe 💅

---

🦋 SYNOPSIS 🦋

void device_resume_noirq (struct device *dev , pm_message_t state , bool
async );

like yes, three args, no cap, we love a clean signature ✨

---

🎀 ARGUMENTS 🎀

• dev — the device we're handling. the one being resumed. our little guy 🥺
• state — the PM transition of the system that's currently being carried out. basically "which nap were we waking up from" energy 😴➡️👀
• async — if it's true, then this device is being resumed asynchronously. lowkey multitasking icon behavior ⭐

---

🔥 DESCRIPTION 🔥

okay so here's the tea ☕ — while this function is being executed, the driver of dev will not receive interrupts. literally none. not a single one. the driver is on do-not-disturb mode the entire time, periodt 💀

so like, that's the whole deal — you're running the noirq resume callback, and in that window the driver just doesn't get interrupted. iconic but also please respect the boundary 🙈

---

🌈 SEE ALSO 🌈

the whole friend group 💜 first up, the kernel file it lives in: ./drivers/base/power/main.c — and then the extended crew:

• pm_hibernate_is_recovering(9)
• device_pm_sleep_init(9)
• device_pm_lock(9)
• device_pm_unlock(9)
• device_pm_add(9)
• device_pm_remove(9)
• device_pm_move_before(9)
• device_pm_move_after(9)
• device_pm_move_last(9)
• dpm_wait(9)
• pm_op(9)
• pm_late_early_op(9)
• pm_noirq_op(9)
• dpm_watchdog_handler(9)
• dpm_watchdog_set(9)
• dpm_watchdog_clear(9)
• dev_pm_skip_resume(9)
• dpm_resume_noirq(9)
• device_resume_early(9)
• dpm_resume_early(9)
• dpm_resume_start(9)
• device_resume(9)
• dpm_resume(9)
• device_complete(9)
• dpm_complete(9)
• dpm_resume_end(9)
• resume_event(9)
• device_suspend_noirq(9)
• dpm_suspend_noirq(9)
• device_suspend_late(9)
• dpm_suspend_late(9)
• dpm_suspend_end(9)
• legacy_suspend(9)
• device_suspend(9)
• dpm_suspend(9)
• device_prepare(9)
• dpm_prepare(9)
• dpm_suspend_start(9)
• device_pm_wait_for_dev(9)
• dpm_for_each_dev(9)

like, that's the whole group chat, every single one, no skips 🫶

---

💀 reminder bestie: no interrupts for the driver of dev during execution. that's not a suggestion, that's the rule. iykyk.

---

and that's a wrap on our little page 🧚 it comes to you from ./drivers/base/power, dated <purple>October 2026</purple>, and it's part of the <pink>Kernel API Manual</pink> — slay, go resume some devices responsibly 👑💅