STRUCT DEV_PM_OPP_CONFIG(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ struct dev_pm_opp_config(9) ✨

okay so bestie, welcome to the Kernel API Manual πŸ’– β€” this is the little page for struct dev_pm_opp_config, which the header calls "Device OPP configuration values". yes it's a struct, yes it's important, no you can't skip it 🫢


🌸 NAME 🌸

struct dev_pm_opp_config β€” Device OPP configuration values πŸ’…


πŸŽ€ SYNOPSIS πŸŽ€

this is the whole vibe, fr fr, copied exactly:

struct dev_pm_opp_config {
    const char * const *clk_names;
    config_clks_t config_clks;
    const char *prop_name;
    config_regulators_t config_regulators;
    const unsigned int *supported_hw;
    unsigned int supported_hw_count;
    const char * const *regulator_names;
    struct device *required_dev;
    unsigned int required_dev_index;
 };

πŸ¦‹ Members πŸ¦‹

okay now the main character energy β€” every single member, one by one πŸ‘‘

  • clk_names β€” clk names, and it's a NULL terminated array. yes, terminated. don't forget the NULL or it will simply keep going 😭
  • config_clks β€” a custom set clk helper. your own little helper, iconic ✨
  • prop_name β€” the name you postfix to properties. postfix, not prefix. read it again bestie πŸ’€
  • config_regulators β€” a custom set regulator helper. the regulator counterpart, slay πŸŽ€
  • supported_hw β€” array of hierarchy of versions to match. hierarchy! versions! matching! 🌈
  • supported_hw_count β€” number of elements in the array. aka how many of the above you actually have πŸ”₯
  • regulator_names β€” array of pointers to the names of the regulator, NULL terminated. again with the NULL termination, it's giving pattern 🌸
  • required_dev β€” the required OPP device. πŸ‘‘
  • required_dev_index β€” the index of the required OPP for the required_dev. like, which one πŸ’…

πŸ’œ Description πŸ’œ

so what is this thing? this structure contains platform specific OPP configurations for the device. that's it, that's the whole description, no cap 🫢

ngl it's a small struct but it's literally the whole configuration vibe for your device's OPP setup, so treat it with respect 🧚

⭐ SEE ALSO ⭐

go look at these, iykyk:

  • Kernel file ./include/linux/pm_opp.h
  • struct dev_pm_opp_supply(9)
  • struct dev_pm_opp_data(9)
  • struct dev_pm_opp_key(9)

aaaand that's the page!! πŸŽ‰ this little beauty lives in ./include/linux and this version is dated October 2026, all official-like in the Kernel API Manual β€” mwah, bye bestie πŸ’–πŸ’…βœ¨

πŸ“¦ where this page comes from