pm_wakeup_dev_event(9)

📦 version 7.3.1, in nixpkgs unstable

💖 pm_wakeup_dev_event(9) — from the Kernel API Manual, bestie 💖

okay so picture this: you're deep in the kernel, the power-management girlies are all vibing, and something just happened that the PM core needs to know about. That's this function. It's the little messenger that says "hey bestie, wakeup event, handle it" 🫶

✨ NAME ✨

pm_wakeup_dev_event — Notify the PM core of a wakeup event. literally its whole job, and it does it flawlessly, no cap 💅

🦋 SYNOPSIS 🦋

void pm_wakeup_dev_event (struct device *dev , unsigned int msec , bool
hard );

🎀 ARGUMENTS 🎀

  • dev — the struct device this wakeup event is related to. like, whose event is this? this one. 🫵
  • msec — the anticipated event processing time, in milliseconds. yes, milliseconds, keep that unit in your head bestie ⏱️
  • hard — if this is set, it aborts suspends that are in progress and wakes up from suspend-to-idle. so it's the dramatic one 💀 set it and things actually get interrupted.

🌸 DESCRIPTION 🌸

So what does it actually do? The way that it just calls pm_wakeup_ws_event for dev's wakeup source object. that's it, that's the whole description, and honestly? iconic. it delegates and it slays ✨

ngl this one is a thin wrapper — all the real lore lives in pm_wakeup_ws_event(9), which is down there in SEE ALSO 👀

👑 SEE ALSO 👑

Kernel file ./drivers/base/power/wakeup.c — and now the whole friend group, in order, nobody left out:

that's 39 entries bestie, I counted, we do not skip a single one in this house 🏠💜 (and yes, pm_wakep_autosleep_enabled(9) really is spelled like that — I did not touch it, I would never 🙈)

✨ that's the whole page, mwah ✨

cute little sign-off: this one lives in ./drivers/base/power, dated October 2026, and it goes by pm_wakeup_dev_event(9). go forth and wake things up responsibly 🧚‍♀️💖🎀

📦 where this page comes from