dev_pm_genpd_resume(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– dev_pm_genpd_resume β€” the dev_pm_genpd_resume(9) glow-up guide πŸ’–

Okay bestie, buckle up, because this is the kernel API manual page for dev_pm_genpd_resume(9) and honestly? she's short but she's important. Let's get into it. ✨


🌸 NAME 🌸

dev_pm_genpd_resume β€” synchronously try to resume the genpd for @dev. That's it, that's the whole name, and yes, the "synchronously" is doing a lot of heavy lifting there, iykyk. πŸ’…


πŸ¦‹ SYNOPSIS πŸ¦‹

void dev_pm_genpd_resume (struct device *dev );

Look at her. Returns void. Doesn't even hand you an error code back. Iconic, lowkey terrifying. 🫢


πŸŽ€ ARGUMENTS πŸŽ€

  • dev β€” the device that's attached to the genpd, the one that needs to be resumed. That's your main character right there. πŸ‘‘

⭐ DESCRIPTION ⭐

So here's the tea: this routine should typically be called for a device that needs to be resumed during the syscore resume phase. Like, that's her whole moment to shine. ✨

She may also be called during suspend-to-idle, to resume a corresponding CPU device that's attached to a genpd. So yes, there are two vibes she shows up for. Versatile queen. 🌈

ngl, the word "synchronously" in the NAME is not a suggestion β€” this thing does the resume right then and there, no queuing, no "I'll get to it later". Plan accordingly bestie πŸ’€

πŸ’œ SEE ALSO πŸ’œ

Where do we even start. The whole genpd friend group is here, and they all ate:

Yeah. Fifty-eight of them. She knows everyone. 🧚


That's the whole page bestie β€” short, sweet, and synchronous. Go forth and resume responsibly. πŸ’œ

Source dir: ./drivers/pmdomain Β· Dated: October 2026 Β· mwah, xoxo, see you in the next manpage πŸ’…βœ¨πŸŽ€

πŸ“¦ where this page comes from