dev_pm_enabl...ke_irq_check(9)

📦 version 7.3.1, in nixpkgs unstable

🎀 dev_pm_enabl...ke_irq_check — Kernel API Manual vibes 🎀

okay so bestie, welcome to the Kernel API Manual entry for dev_pm_enabl...ke_irq_check — yes the name is a whole entire mouthful and yes we're gonna get through it together, hand in hand, no cap 💖

✨ NAME ✨

dev_pm_enable_wake_irq_check — literally checks and enables the wake-up interrupt, that's the whole gig 🫶

🌸 SYNOPSIS 🌸

void dev_pm_enable_wake_irq_check (struct device *dev , bool can_change_status );

🦋 ARGUMENTS 🦋

  • dev — the device, bestie. the main character of this whole function 💅
  • can_change_status — tells us whether we're allowed to change the wake-up interrupt status. like, permission slip energy ✨

💜 DESCRIPTION 💜

so the vibe here is: this enables the wakeirq conditionally. not just whenever, okay? we enable the wake-up interrupt lazily on the first rpm_suspend — and honestly that's so real of it 🧚

why, you ask? because the consumer device starts in RPM_SUSPENDED state, and the first pm_runtime_get would otherwise try to disable an already-disabled wakeirq, which is giving messy. we don't do messy. and the wake-up interrupt starts disabled with IRQ_NOAUTOEN set — iconic, self-aware, knows its boundaries 💀

bestie this is important: it should be called from rpm_suspend, rpm_resume, pm_runtime_force_suspend or pm_runtime_force_resume. no random drive-bys please 🙈

and the caller must hold dev->power.lock or disable runtime PM to change wirq->status. that part is not a suggestion, that's the law, periodt 🔥

👑 SEE ALSO 👑

the kernel file lives at ./drivers/base/power/wakeirq.c and here's the whole friend group, mwah:

and that's the page, bestie — go forth and enable those wake-up interrupts responsibly 🌈💖

sign-off szn: this one comes from ./drivers/base/power, dated October 2026, and belongs to dev_pm_enabl...ke_irq_check(9). slay, bye 🎀✨💅

📦 where this page comes from