pm_runtime_deactivate_timer(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… pm_runtime_deactivate_timer β€” like, the manual page bestie πŸ’…

Okay so hi!! 🫢 You're looking at pm_runtime_deactivate_timer(9) from the Kernel API Manual (section 9, yes, that's the vibe), and honestly? It's a little one. A tiny icon. A single function that does exactly one thing and doesn't overexplain itself, and I respect that so much. ✨


✨ NAME ✨

pm_runtime_deactivate_timer β€” deactivate the given device's suspend timer. That's it. That's the whole gig. πŸŽ€


🌸 SYNOPSIS 🌸

void pm_runtime_deactivate_timer (struct device *dev );

Not me pointing out that this returns void β€” like, it gives nothing back, and that's fine, we love a function with no strings attached. πŸ’€


πŸ¦‹ ARGUMENTS πŸ¦‹

  • dev β€” the device you're handling. That's the one. The device to handle. Hand it over. πŸ™ˆ

πŸ‘‘ SEE ALSO πŸ‘‘

Okay bestie, buckle up, because this is the part where the page goes absolutely feral with the cross-references. Every single one of these is literally right here, no cap, I'm not skipping a single one:

Like… the whole runtime PM friend group showed up to the party. πŸ”₯ Every single one, accounted for, not one left on read. πŸ’œ


Heads up bestie: this page is short on purpose. It hands you the deactivate-timer function and then points you at the entire runtime power-management crew above β€” so if you need actual context on suspend timers, that's where you go. 🌈

That's the whole page, bestie β€” no filler, no fluff, just one function and its forty-ish besties. πŸ“

And for the cute sign-off: this lil beauty comes to you from ./drivers/base/power πŸ’–, dated October 2026, and it's part of the Kernel API Manual, section 9. Slay. Periodt. ⭐

πŸ“¦ where this page comes from