dev_pm_genp...next_hrtimer(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– dev_pm_genp...next_hrtimer(9) πŸ’–

okay bestie, welcome to the Kernel API Manual β€” yes that's the manual name, we're fancy here β€” and today's main character is dev_pm_genp...next_hrtimer(9). buckle up, this one's a quick little baddie but she's important. ✨


🌸 NAME 🌸

dev_pm_genpd_get_next_hrtimer β€” she returns the next_hrtimer for the genpd. that's it, that's the whole job, and she does it flawlessly. πŸ’…


πŸŽ€ SYNOPSIS πŸŽ€

ktime_t dev_pm_genpd_get_next_hrtimer (struct device *dev );

literally just hand her a device and she hands you back a ktime_t. no cap. 🫢


πŸ¦‹ ARGUMENTS πŸ¦‹

  • dev β€” a device that is attached to the genpd. that's the vibe check: it has to be attached, iykyk.

✨ DESCRIPTION ✨

so here's the tea β˜• β€” this routine should typically be called for a device at the point of when a GENPD_NOTIFY_PRE_OFF notification has been sent for it. that's the moment. that's her window. don't be weird about it. πŸ•

what she gives you back is the aggregated value of the genpd's next hrtimer, or KTIME_MAX if no valid value have been set. so if nothing's been set, you're not getting a cute little number, you're getting KTIME_MAX. periodt. πŸ’€


πŸ’œ SEE ALSO πŸ’œ

the kernel file herself: ./drivers/pmdomain/core.c 🧚

and now, the entire group chat β€” every single one of her mutuals, no one left on read:

like, that is a whole friend group and they all live in the same directory. obsessed. πŸ”₯


okay that's the page, bestie! πŸ’– this iconic little slice of documentation is from the kernel source tree at ./drivers/pmdomain, dated October 2026, and we've got the manual name Kernel API Manual up top so you always know where you are. go forth, get that next_hrtimer, slay. πŸŒˆπŸ‘‘πŸ’…

πŸ“¦ where this page comes from