devm_devfreq_add_governor(9)
π devm_devfreq_add_governor β from the Kernel API Manual β¨
Okay so bestie, welcome to the glow-up era of devfreq governors π This is the devm_devfreq_add_governor(9) page and it's literally about adding a devfreq governor, but the managed way. Let's get into it π
β¨ NAME β¨
devm_devfreq_add_governor β add a devfreq governor, no cap π
πΈ SYNOPSIS πΈ
int devm_devfreq_add_governor (struct device *dev , struct
devfreq_governor *governor );
Look at her. Returning an int, taking a struct device * and a struct devfreq_governor *. Iconic signature, tbh π«Ά
π¦ ARGUMENTS π¦
devβ the device that's adding the devfreq governor. Like, this is the one doing the adding πββοΈgovernorβ the actual devfreq governor to be added. The main character of this whole function, fr fr β
π DESCRIPTION π
So here's the vibe check: this is a resource-managed variant of devfreq_add_governor. That's it, that's the whole thing β the devm_ prefix means managed, and it does the same job as its non-managed twin π
π₯ SEE ALSO π₯
The kernel file lives at ./drivers/devfreq/devfreq.c and it's absolutely giving "I contain multitudes". Here's the whole friend group, don't leave anyone out π«Ά:
find_device_devfreq(9),devfreq_get_freq_range(9),devfreq_get_freq_level(9),devfreq_update_status(9)β the lookup-and-status girlies πfind_devfreq_governor(9),try_then_request_governor(9),devfreq_update_target(9),update_devfreq(9)β the governor-hunting squad π§devfreq_monitor(9),devfreq_monitor_start(9),devfreq_monitor_stop(9),devfreq_monitor_suspend(9),devfreq_monitor_resume(9),devfreq_update_interval(9)β the monitoring committee, they meet constantly πdevfreq_notifier_call(9),qos_notifier_call(9),qos_min_notifier_call(9),qos_max_notifier_call(9)β who's calling? it's the notifiers πdevfreq_dev_release(9),devfreq_add_device(9),devfreq_remove_device(9),devm_devfreq_add_device(9),devm_devfreq_remove_device(9)β device life cycle besties πdevfreq_suspend_device(9),devfreq_resume_device(9),devfreq_suspend(9),devfreq_resume(9)β the nap squad π΄devfreq_add_governor(9),devfreq_remove_governor(9)β the un-managed originals, respect πdevfreq_summary_show(9),devfreq_recommended_opp(9),devfreq_register_opp_notifier(9),devfreq_unregister_opp_notifier(9),devm_devfreq_register_opp_notifier(9),devm_devfreq_unregister_opp_notifier(9)β the OPP+summary crew πdevfreq_register_notifier(9),devm_devfreq_register_notifier(9),devm_devfreq_unregister_notifier(9)β more notifiers because we literally never have enough β¨
ngl bestie, if you got here by scrolling a 38-function SEE ALSO list, you're doing amazing, and this page is your little checkpoint π
And that's the tea β β this page comes to you from ./drivers/devfreq, dated October 2026, and it's the devm_devfreq_add_governor(9) manual page. Slay, go add your governor, and remember: resource-managed or it didn't happen π
π
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms