genpd_dev_pm_attach_by_name(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– NAME πŸ’–

okay bestie, welcome to the genpd_dev_pm_attach_by_name(9) page of the Kernel API Manual β€” and no, the title is not a keyboard smash, it's iconic ✨

genpd_dev_pm_attach_by_name β€” Associate a device with one of its PM domains. that's it, that's the whole vibe πŸ’…


πŸŽ€ SYNOPSIS πŸŽ€

struct device * genpd_dev_pm_attach_by_name (struct device *dev , const char *name );

literally just hand it a device and a name and let it cook πŸ“


πŸ¦‹ ARGUMENTS πŸ¦‹

  • dev β€” the device used to lookup the PM domain. the main character of this operation, no cap πŸ‘‘
  • name β€” the name of the PM domain. this is the one you're going after by name, iykyk πŸ”₯

🌸 DESCRIPTION 🌸

so here's the tea 🍡 β€” this little function parses the device's OF node to find a PM domain specifier, using the power-domain-names DT property. yes, that property. the name-matching one. it's giving "i know exactly which domain i want and i'm not settling" energy πŸ’…βœ¨

and for further description? bestie, go read genpd_dev_pm_attach_by_id β€” that's where the full story lives 🫢

ngl this one's short and sweet, but the family reunion is real β€” the whole squad is down in SEE ALSO πŸ”₯

🌈 SEE ALSO 🌈

first up, the source itself, right here in the kernel files:

  • ./drivers/pmdomain/core.c

and now the entire group chat, in the exact order they're listed β€” every single one, because we don't leave a single bestie out πŸ’œ


and that's the whole page, bestie 🧚✨ it lives over in ./drivers/pmdomain like the little power-domain hub it is, it's stamped October 2026 (yes, future queen behavior πŸ’€), and it answers to the name genpd_dev_pm_attach_by_name(9) β€” periodt. πŸ«ΆπŸ’–πŸŽ€

πŸ“¦ where this page comes from