handle_threaded_wake_irq(9)

💅 handle_threaded_wake_irq(9) — a Kernel API Manual moment

okay so bestie, welcome to the handle_threaded_wake_irq page from the Kernel API Manual. this one's short but it's lowkey important, so pay attention 🫶

---

✨ NAME ✨

handle_threaded_wake_irq — the handler for dedicated wake-up interrupts 💤➡️🔥

---

🌸 SYNOPSIS 🌸

irqreturn_t handle_threaded_wake_irq (int irq , void *_wirq );

---

🎀 ARGUMENTS 🎀

• irq — the device-specific dedicated wake-up interrupt. this is the interrupt in question, the one whose whole job is waking stuff up ⭐
• _wirq — the wake IRQ data. literally the data, no cap 🙈

---

🦋 DESCRIPTION 🦋

so like, some devices have a separate wake-up interrupt on top of their normal device IO interrupt. the wake-up interrupt is the one that signals "hey, this device should be woken up from its idle state" 🔔

this handler uses device specific pm_runtime functions to wake the device, and then it's up to the device to do whatever it needs to do. it's giving main character energy — everyone else is just supporting cast 💅

note that because the device may need to restore context and start up regulators, we use a threaded IRQ 🧵 (yes, that's why it's in the name, iykyk).

also note: we are not resending the lost device interrupts. we assume that the wake-up interrupt just needs to wake-up the device, and then the device's pm_runtime_resume can deal with the situation. periodt. 💀

---

🔥 SEE ALSO 🔥

• the kernel file ./drivers/base/power/wakeirq.c
• dev_pm_attach_wake_irq(9)
• dev_pm_set_wake_irq(9)
• dev_pm_clear_wake_irq(9)
• devm_pm_set_wake_irq(9)
• dev_pm_set_dedicated_wake_irq(9)
• dev_pm_set_dedicated_wake_irq_reverse(9)
• dev_pm_enable_wake_irq_check(9)
• dev_pm_disable_wake_irq_check(9)
• dev_pm_enable_wake_irq_complete(9)
• dev_pm_arm_wake_irq(9)
• dev_pm_disarm_wake_irq(9)

like, the whole wake IRQ friend group honestly 🌈👑

---

and that's the page!! it lives in ./drivers/base/power, dated October 2026, and it's iconic for it 🎀✨ bye bestie, go wake up some devices 💖