dev_pm_opp_f...loor_indexed(9)

📦 version 7.3.1, in nixpkgs unstable

🌸 dev_pm_opp_find_freq_floor_indexed 💅

okay so bestie, welcome to the Kernel API Manual — yes this is that dev_pm_opp_f...loor_indexed(9) page, the one with the truncated name that looks like it fell asleep mid-word 😭 don't worry, we're getting into it together 🫶

✨ NAME ✨

dev_pm_opp_find_freq_floor_indexed — bestie, this one searches for a rounded floor frequency for the clock that corresponds to the index 👑

🦋 SYNOPSIS 🦋

struct dev_pm_opp * dev_pm_opp_find_freq_floor_indexed (struct device
*dev , unsigned long *freq , u32 index );

like, that's the whole vibe right there ✨

🎀 ARGUMENTS 🎀

  • dev — the Device we're doing this whole operation for 🫶
  • freq — the start frequency, that's where the search kicks off 📍
  • index — the clock index 🕐

💖 DESCRIPTION 💖

So the way this works: it searches for the matching floor available OPP for the clock corresponding to the specified index — starting from a start freq, for a device ✨ ngl, "floor" here is doing a lot of work and it's kind of iconic for it.

Caller obligations, no cap: you literally have to call dev_pm_opp_put for the returned OPP after you use it 🔥 don't just vibe with it forever, that's a leak bestie 😭

🌈 RETURN 🌈

  • On a win: the matching *opp, and it refreshes *freq accordingly 💅✨
  • Otherwise: it returns ERR_PTR in case of error — and you should be handling that with IS_ERR 🙈

the possible error return values, laid out cute:

  • EINVAL — for bad pointer 🚫
  • ERANGE — no match found for search 😭
  • ENODEV — if the device is not found in the list of registered devices 💀

🧚 SEE ALSO 🧚

Kernel file ./drivers/opp/core.c, plus this whole friend group of manpages — every single one, we're not skipping anybody, everybody's invited to the group chat 👑

and that's the page bestie 💜 this one lives over in ./drivers/opp and it's dated October 2026 — yeah, from the future, main character energy fr fr 🎀 go call dev_pm_opp_put when you're done, ily, bye 💅✨

📦 where this page comes from