dev_pm_opp_...able_indexed(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ dev_pm_opp_of_add_table_indexed(9) ✨

okay bestie, welcome to the Kernel API Manual πŸ’… this little cutie is dev_pm_opp_of_add_table_indexed β€” yes the header up top shortens it to dev_pm_opp_...able_indexed(9) because apparently even manpage headers get shy πŸ™ˆ β€” and it's here to get your OPP table poppin' straight out of the device tree 🌸


πŸŽ€ NAME πŸŽ€

dev_pm_opp_of_add_table_indexed β€” initialize an indexed opp table from the device tree, no cap πŸ¦‹


⭐ SYNOPSIS ⭐

int dev_pm_opp_of_add_table_indexed (struct device *dev , int index );

that's the whole vibe. two args, one int coming back atcha πŸ”₯


🫢 ARGUMENTS 🫢

  • dev β€” the device pointer, aka the lil handle we use to look up the OPP table. main character energy honestly πŸ‘‘
  • index β€” the index number. just… a number. an index one might say πŸ’€

πŸ’– DESCRIPTION πŸ’–

So like β€” this function registers the initial OPP table with the OPP library for whatever device you passed in ✨ and it does it only using the "operating-points-v2" property. that's it, that's the whole personality. no other property gets a look in, periodt πŸ’…


🌈 RETURN 🌈

ngl, there's no drama here β€” for the return values you gotta refer to dev_pm_opp_of_add_table 🫢 it's giving "ask your friend, she knows" and honestly? valid.


πŸ¦‹ SEE ALSO πŸ¦‹

Kernel file ./drivers/opp/of.c β€” that's where the magic lives, iykyk 🧚

and the whole friend group:


πŸ’€ tiny reminder bestie: it's the initial table and it's indexed and it's "operating-points-v2"-only β€” don't go expecting it to read anything else, fr fr.

okay that's the whole page, ily, go forth and index your OPPs πŸŒΈπŸ’–βœ¨ this one came out of ./drivers/opp, dated October 2026 β€” mwah, see u in the next manpage πŸ«ΆπŸŽ€

πŸ“¦ where this page comes from