dev_pm_opp_find_freq_ceil(9)

💖 dev_pm_opp_find_freq_ceil — Kernel API Manual ✨

okay so bestie, welcome to the group chat about dev_pm_opp_find_freq_ceil(9), which lives in the Kernel API Manual and is genuinely one of those lil functions that's lowkey iconic once you get it 🎀

---

🌸 NAME 🌸

dev_pm_opp_find_freq_ceil — search for a rounded ceil freq

like, it's giving "find me the next frequency up from here" energy, and honestly? we love that for us 💅

---

✨ SYNOPSIS ✨

struct dev_pm_opp * dev_pm_opp_find_freq_ceil (struct device *dev ,
unsigned long *freq );

no cap, that's the whole vibe right there — you hand it a device and a pointer to a frequency, it goes looking 🦋

---

🎀 ARGUMENTS 🎀

• dev — the device we're doing this whole operation for. main character device energy, fr fr 👑
• freq — the start frequency. this is where the search kicks off 💫

---

💜 DESCRIPTION 💜

so basically, it searches for the matching ceil available OPP, starting from a given freq, for a device. the "ceil" is doing a lot of work here — we're rounding up, bestie, not down 📈

ok important psa: the callers are required to call dev_pm_opp_put for the returned OPP after use. do NOT forget this. it's literally the number one thing. put it back. put it back bestie 😭💀

---

🌈 RETURN 🌈

it gives you the matching *opp and refreshes *freq accordingly ✨ — but if something goes sideways it returns ERR_PTR instead, in case of error, and you should handle that using IS_ERR. no skipping the vibe check on that one 🫶

the error return values can be:

• EINVAL — for bad pointer 🙈
• ERANGE — no match found for search 😔
• ENODEV — if device not found in list of registered devices 💀

---

🧚 SEE ALSO 🧚

kernel file ./drivers/opp/core.c and honestly the whole friend group:

• _find_opp_table(9)
• dev_pm_opp_get_bw(9)
• dev_pm_opp_get_voltage(9)
• dev_pm_opp_get_supplies(9)
• dev_pm_opp_get_power(9)
• dev_pm_opp_get_freq_indexed(9)
• dev_pm_opp_get_level(9)
• dev_pm_opp_get_required_pstate(9)
• dev_pm_opp_is_turbo(9)
• dev_pm_opp_get_max_clock_latency(9)
• dev_pm_opp_get_max_volt_latency(9)
• dev_pm_opp_get_max_transition_latency(9)
• dev_pm_opp_get_suspend_opp_freq(9)
• dev_pm_opp_get_opp_count(9)
• dev_pm_opp_find_freq_exact(9)
• dev_pm_opp_find_key_exact(9)
• dev_pm_opp_find_freq_exact_indexed(9)
• dev_pm_opp_find_freq_ceil_indexed(9)
• dev_pm_opp_find_freq_floor(9)
• dev_pm_opp_find_freq_floor_indexed(9)
• dev_pm_opp_find_level_exact(9)
• dev_pm_opp_find_level_ceil(9)
• dev_pm_opp_find_level_floor(9)
• dev_pm_opp_find_bw_ceil(9)
• dev_pm_opp_find_bw_floor(9)
• dev_pm_opp_set_rate(9)
• dev_pm_opp_set_opp(9)
• dev_pm_opp_remove(9)
• dev_pm_opp_remove_all_dynamic(9)
• _opp_add_v1(9)
• dev_pm_opp_set_config(9)
• dev_pm_opp_clear_config(9)
• devm_pm_opp_set_config(9)
• dev_pm_opp_xlate_required_opp(9)
• dev_pm_opp_xlate_performance_state(9)
• dev_pm_opp_add_dynamic(9)
• _opp_set_availability(9)
• dev_pm_opp_adjust_voltage(9)
• dev_pm_opp_sync_regulators(9)
• dev_pm_opp_enable(9)
• dev_pm_opp_disable(9)
• dev_pm_opp_register_notifier(9)
• dev_pm_opp_unregister_notifier(9)
• dev_pm_opp_remove_table(9)

---

and that's the whole page, bestie — go forth and ceil responsibly 💖✨

sign-off time 🫶 this lil manpage comes from ./drivers/opp, dated October 2026, and it's the dev_pm_opp_find_freq_ceil(9) page in the Kernel API Manual. ily, drink water, and don't forget dev_pm_opp_put 🍓🧚‍♀️💜