dev_pm_set_wake_irq(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

dev_pm_set_wake_irq πŸ’…βœ¨

okay so bestie, welcome to the Kernel API Manual page for dev_pm_set_wake_irq β€” this is the little function that says β€œhey, this device IO interrupt? yeah, it’s a wake IRQ now πŸ’–.” No cap, it’s giving power-management main character energy. πŸŽ€


🌸 NAME 🌸

dev_pm_set_wake_irq β€” Attach device IO interrupt as wake IRQ πŸ¦‹


✨ SYNOPSIS ✨

int dev_pm_set_wake_irq (struct device *dev , int irq );

πŸ’– ARGUMENTS πŸ’–

  • dev β€” Device entry. Like, the device in question, bestie. 🫢
  • irq β€” Device IO interrupt. The interrupt that’s about to get its wake-IRQ moment. ⭐

πŸ¦‹ DESCRIPTION πŸ¦‹

Attach a device IO interrupt as a wake IRQ. Periodt. πŸ’…

The wake IRQ gets automatically configured for wake-up from suspend based on the device specific sysfs wakeup entry. So it’s not doing mystery magic β€” it’s tied to that sysfs wakeup situation. πŸ”₯

Typically called during driver probe after calling device_init_wakeup. That’s the vibe check: driver probe first, device_init_wakeup first, then this. Ngl, order matters, iykyk. 🌈


🌺 SEE ALSO 🌺


bestie, that’s the whole page β€” every argument, every reference, every little wake-IRQ detail preserved with love. πŸ’œ

πŸ’Œ cute little sign-off: this cutie comes from source ./drivers/base/power, dated October 2026. slay. πŸ‘‘

πŸ“¦ where this page comes from