dev_pm_opp_g...uired_pstate(9)

📦 version 7.3.1, in nixpkgs unstable

💅 dev_pm_opp_get_required_pstate(9) — the Kernel API Manual, bestie edition 🎀

okay so real talk, this is dev_pm_opp_get_required_pstate(9), straight out of the Kernel API Manual, section 9 (that's the kernel-API section, iykyk). The page header literally gets cut off as dev_pm_opp_g...uired_pstate(9) because the name is lowkey too long for the header, and honestly? iconic of it. Let's get into it ✨

🌸 NAME 🌸

dev_pm_opp_get_required_pstate — gets the required performance state corresponding to an available opp. That's it, that's the whole vibe 🫶

🦋 SYNOPSIS 🦋

unsigned int dev_pm_opp_get_required_pstate(struct dev_pm_opp *opp,
                                            unsigned int index);

like, you hand it an opp and an index, and it hands you back an unsigned int. no drama, no cap 💜

✨ ARGUMENTS ✨

  • opp — the opp you want the performance state for. literally the opp in question, bestie 👑
  • index — the index of the required opp. which one you're pointing at, fr fr 🔥

🌈 RETURN 🌈

it returns the performance state that it read from the device tree, corresponding to the required opp. and if there's nothing to return? it gives you back U32_MAX instead. that's the fallback, that's the safety net, that's the "sorry bestie, nothing here" value 😭💀

💖 SEE ALSO 💖

so there are a lot of siblings in this family. the kernel file lives at ./drivers/opp/core.c, and everybody here is in section 9 — go say hi:

like, that's the whole opp friend group right there. main character energy from every single one 💅✨

ngl this page is short and sweet — no warnings, no deprecated anything, no scary undefined behaviour. just one little getter doing its job. slay 🎀

and that's the tea, bestie 🍓 this cutie of a page comes to you from ./drivers/opp and it's dated October 2026 — so yeah, the footer is giving very much "future kernel manual, but make it fashion" 🌟 love that for us. bye pookie, go read the device tree 💜🦋

📦 where this page comes from