dev_pm_opp_o...required_opp(9)

📦 version 7.3.1, in nixpkgs unstable

💖 dev_pm_opp_of_has_required_opp — your fave little kernel detective 💖

okay so bestie, this is a page from the Kernel API Manual (that's the manual name, she's fancy), and honestly? she's short, she's sweet, and she's serving one specific job — let's get into it ✨

🌸 NAME 🌸

dev_pm_opp_of_has_required_opp — literally just finds out if a required-opps exists. that's it. that's the whole gig 🎀

🦋 SYNOPSIS 🦋

bool dev_pm_opp_of_has_required_opp (struct device *dev );

like, you hand her a struct device *dev and she hands you back a bool. simple. iconic. 💅

✨ ARGUMENTS ✨

  • dev — the device to investigate 🔍 bestie we are investigating her, put on the detective hat, it's giving main character energy

💜 DESCRIPTION 💜

so here's the vibe check 🫶: it returns true if the device's node has an "operating-points-v2" property AND if the corresponding node for the opp-table describes opp nodes that uses the "required-opps" property.

both of those things gotta be true, no cap. it's an and, not an or — the way that matters is so real 😭

⭐ RETURN ⭐

True if a required-opps is present, else false. literally that's it, go off king 👑

🌈 SEE ALSO 🌈

the kernel file lives at ./drivers/opp/of.c — write that down bestie 📝

and here's the whole friend group, all referenced, all accounted for, not a single one left out:

they're all in the group chat, iykyk 💬🧚

lowkey reminder: this page is dated October 2026, lives in ./drivers/opp, and the manual name on the tin is dev_pm_opp_o...required_opp(9) — the truncated header is not a typo, it's just her little nickname okay 🙈

mwah, love u, go read the opp code, periodt 💖🍓💀

📦 where this page comes from