pm_wakeup_timer_fn(9)

📦 version 7.3.1, in nixpkgs unstable

💅 pm_wakeup_timer_fn(9) 💅

okay so bestie, this little angel lives in the Kernel API Manual — that's the (9) section, dev-kernel territory, iykyk 🧚✨ buckle up.

🌸 NAME 🌸

pm_wakeup_timer_fn — the delayed finalization of a wakeup event, fr fr. like the cleanup crew that shows up fashionably late 💅

✨ SYNOPSIS ✨

void pm_wakeup_timer_fn (struct timer_list *t );

that's the whole vibe. one timer list, no return value, in and out 🫶

🎀 ARGUMENTS 🎀

  • t — timer list. that's it, that's the arg. your whole personality for this function is being a timer list 💀

🔥 DESCRIPTION 🔥

okay so here's the tea ☕ — this function calls wakeup_source_deactivate for the wakeup source whose address is stored in data, but only when all three of these things line up:

  • the wakeup source is currently active ✅
  • its timer has not been canceled ✅
  • the expiration time of the timer is not in the future ✅

all three or it's a no-op, no cap. it's giving "finalization but make it delayed" ✨ the parenthetical in the NAME section literally says delayed finalization of a wakeup event, so yeah, it's the slow-mo cleanup moment, main character energy 🌈

ngl bestie, note that the description says the address is stored in data — that's the wording, keep it in your back pocket 🍓

👑 SEE ALSO 👑

hey bestie, the source of all this lore is the kernel file ./drivers/base/power/wakeup.c — go read it, it's iconic 📖✨ and while you're at it, the whole friend group:

and that's the whole page bestie, you ate that 💖

cute lil sign-off: this one's from ./drivers/base/power, dated October 2026, and yeah — it's pm_wakeup_timer_fn(9) all the way down 🦋✨ periodt.

📦 where this page comes from