device_wakeup_attach(9)

📦 version 7.3.1, in nixpkgs unstable

💖 device_wakeup_attach — the Kernel API Manual, section 9, bestie 💖

okay so real quick before we dive in: this is device_wakeup_attach(9), straight out of the Kernel API Manual (section 9, the kernel-functions girlies). it lives in ./drivers/base/power and it's dated October 2026 — bookmark that, we'll circle back at the end 🎀

✨ NAME ✨

device_wakeup_attach — attach a wakeup source object to a device object. that's it, that's the whole vibe. it's giving "matchmaker, but for kernel structs" 🫶

🌸 SYNOPSIS 🌸

int device_wakeup_attach (struct device *dev , struct wakeup_source *ws
);

yes bestie, it returns an int — don't ignore the return value, that's not very main character of you 💅

🦋 ARGUMENTS 🦋

  • dev — the device to handle. this is the one getting the glow-up, the one we're attaching stuff to. literally the main character of this function call 🔥
  • ws — the wakeup source object to attach to dev. this is the accessory, the it-girl bag, the thing being clipped onto dev. so cunty of them both tbh ✨

🎀 DESCRIPTION 🎀

so what does this actually do, you ask? it causes dev to be treated as a wakeup device. that's the whole description. no cap, no extra lore, that's the sentence 🌈

like — dev is now Officially A Wakeup Device™. it's been added to the roster. it's on the list. it has woken up and chosen ✨itself✨. the wakeup source object ws is now attached to it, and from this moment forward the kernel treats dev as a thing that can wake stuff up 👑

lowkey iconic behaviour, highkey exactly what the name says. device_wakeup_attach attaches. dev + ws = attached. the math is mathing 🧚

💜 SEE ALSO 💜

okay bestie, buckle up, because the see-also list here is long — like, "she brought her whole group chat to the function" long 😭 every single one of these, no skipping:

first up, the kernel file itself:

  • ./drivers/base/power/wakeup.c — literally the file this whole situation lives in. the mothership 🚀

then the wakeup_source_* girlies:

the read-lock / walk girlies:

the device_wakeup_* fam (we're literally one of these, hiii 💅):

the device_set_wakeup_* duo:

the wakeup source state girlies:

the pm_stay_awake / pm_relax sacred texts (note the double-underscore versions, do NOT come for me):

the pm_wakeup_* section:

the stats girlies:

and finally the bpf girlies, bringing up the rear:

that's 39 references and i listed every single one, because we don't do "etc." in this house 💖

ngl bestie, the entire documented behaviour of device_wakeup_attach is one sentence long. don't overthink it, don't over-read it. it attaches. it's attached. periodt 💅

okay so like — that's the whole page!! and before i go, huge huge shoutout to the source it came from: ./drivers/base/power, dated October 2026, delivered to you in the Kernel API Manual, section 9. she's built different, she's been here since before you were compiling, and honestly? we stan 🎀✨💖

bye bestie, go attach something 🦋💜

📦 where this page comes from