genpd_xlate_onecell(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… genpd_xlate_onecell(9) β€” a Kernel API Manual moment

okay so bestie, welcome to the Kernel API Manual page for genpd_xlate_onecell(9) β€” yes the whole thing is named after the function, iconic, we love a self-titled queen πŸ‘‘


✨ NAME ✨

genpd_xlate_onecell β€” the xlate function that uses a single index. that's it, that's the whole vibe πŸŽ€


🌸 SYNOPSIS 🌸

struct generic_pm_domain * genpd_xlate_onecell (const struct
       of_phandle_args *genpdspec , void *data );

look at her. returns a struct generic_pm_domain *, takes two args, no notes. slay πŸ’…


πŸ¦‹ ARGUMENTS πŸ¦‹

  • genpdspec β€” the OF phandle args that get mapped into a PM domain. literally the "which one tho" of the whole operation πŸ”
  • data β€” the xlate function's private data, and it's a pointer to struct genpd_onecell_data. iykyk 🫢

πŸ’– DESCRIPTION πŸ’–

okay so here's the tea β˜• β€” this is a generic xlate function, and you'd use it to model the simple PM domain controllers: the ones that have one device tree node but hand out multiple PM domains. main character energy but make it a controller ✨

and how does it pick? a single cell is used as an index into an array of PM domains β€” that array lives in the genpd_onecell_data struct that you specify when you register the provider. so: one cell in, index out, domain located. no cap, that's the whole magic trick πŸŽ©πŸ‡


πŸ”₯ SEE ALSO πŸ”₯

bestie there are so many of these and i'm not skipping a single one, we stan completeness πŸ‘‘

like i said. all of them. πŸ’€


and that's the page, bestie 🫢 this little love letter lives down in ./drivers/pmdomain, it's stamped October 2026, and it answers to the name genpd_xlate_onecell(9) β€” go forth and index your one cell, you absolute icon πŸ‘‘βœ¨

πŸ“¦ where this page comes from