dev_pm_genpd...rmance_state(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… dev_pm_genpd...rmance_state(9) πŸ’…

okay so this is a page from the Kernel API Manual, and bestie, it's literally about dev_pm_genpd_set_performance_state β€” yes the whole name, we're not abbreviating, the kernel doesn't do nicknames πŸ’€


✨ NAME ✨

dev_pm_genpd_set_performance_state β€” sets the performance state of a device's power domain. that's it, that's the whole vibe πŸŽ€


πŸ¦‹ SYNOPSIS πŸ¦‹

int dev_pm_genpd_set_performance_state (struct device *dev , unsigned int state );

🌸 ARGUMENTS 🌸

  • dev β€” the device you're setting the performance state for. your main character device, basically πŸ‘‘
  • state β€” the target performance state of the device. and here's the lil ✨detail✨: you can set this to 0 when the device doesn't have any performance state constraints left β€” which means the device wouldn't participate anymore in finding the target performance state of the genpd. so like, it's out of the group chat 🫢

πŸ’– DESCRIPTION πŸ’–

so the assumption here is that the users guarantee that the genpd wouldn't be detached while this routine is getting called. read that again. that's on you, bestie πŸ™ˆ

and then the return situation, which is honestly so clean:

Returns 0 on success, and negative error values on failures πŸ’€


πŸ”₯ SEE ALSO πŸ”₯

Kernel file ./drivers/pmdomain/core.c β€” and honestly? the whole genpd friend group showed up. like, everyone came to the party πŸŽ‰


lowkey the most important part: that detached-genpd thing is on the users. not a suggestion, it's an assumption. don't come for the docs if it breaks 😭

okay that's the page!! it lives in ./drivers/pmdomain, dated October 2026, and it's part of the Kernel API Manual β€” go set some performance states, bestie, you're gonna slay πŸ’…βœ¨πŸŒˆ

πŸ“¦ where this page comes from