device_wakeup_detach(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸŒ™ device_wakeup_detach(9) β€” the kernel API manual, bestie edition πŸŽ€

okay so real talk, this page lives in the Kernel API Manual family (that's the manual name, yes, and yes it's giving "official documentation but make it make sense" πŸ’…), and it's literally about severing the link between a device and its wakeup source object. nothing dramatic, just a clean breakup ✨


✨ NAME ✨

device_wakeup_detach β€” detach a device's wakeup source object from it, periodt πŸ’”


🌸 SYNOPSIS 🌸

struct wakeup_source * device_wakeup_detach (struct device *dev );

πŸ¦‹ DESCRIPTION πŸ¦‹

so like. after it returns, dev will not be treated as a wakeup device any more. that's the whole vibe check. one moment it's a wakeup device, next moment it's just... a device. no cap 🫢


πŸ’– ARGUMENTS πŸ’–

  • dev β€” the device you're detaching the wakeup source object from. that's the one. she's the main character of this call πŸŽ€

πŸ”₯ SEE ALSO πŸ”₯

the kernel file ./drivers/base/power/wakeup.c is where all the lore lives, and honestly the friend group here is enormous β€” every single one of these is a real function, iykyk:


bestie, this is the detach one β€” if you actually wanted to attach, that's device_wakeup_attach(9) up there, don't come for me πŸ™ˆ

and that's the page fr fr πŸ’œ it shipped from ./drivers/base/power, dated October 2026 β€” go off, power management directory, you ate πŸ‘‘βœ¨

πŸ“¦ where this page comes from