devm_devfreq...ter_notifier(9)
π devm_devfreq...ter_notifier(9)
ok so this is a page straight outta the Kernel API Manual and honestly? it's giving "small but mighty." buckle up bestie, we're unregistering a notifier the resource-managed way β¨
πΈ NAME πΈ
devm_devfreq_unregister_notifier -
no like. that's actually it. the description is literally empty π the kernel devs said "the name says enough" and honestly? respect. main character energy.
β¨ SYNOPSIS β¨
void devm_devfreq_unregister_notifier (struct device *dev , struct
devfreq *devfreq , struct notifier_block *nb , unsigned int list );
it returns void, meaning it hands you nothing back. no return value, no vibes check, it just does the thing and dips π«Ά
π ARGUMENTS π
four args, all of them lowkey essential, let's go one by one:
devβ the devfreq user device. (it's the parent ofdevfreq, iykyk β think of it as the mom friend keeping everyone together π)devfreqβ the devfreq object itself. the actual thing we're working with πnbβ the notifier block that's getting unregistered. it's literally in the name, bestie.listβ here you passDEVFREQ_TRANSITION_NOTIFIER. that's the value, that's the whole assignment. slay β¨
π¦ DESCRIPTION π¦
- Resource-managed
devfreq_unregister_notifier
that's the bullet. that's the whole description. it's a one-liner and it ate π the "resource-managed" part is the whole point: this is the devm-flavored version, so the cleanup is handled for you like a good friend who remembers your charger π
β SEE ALSO β
so there's a whole friend group here, and they all live in the kernel file ./drivers/devfreq/devfreq.c π§ β go say hi to:
find_device_devfreq(9)devfreq_get_freq_range(9)devfreq_get_freq_level(9)devfreq_update_status(9)find_devfreq_governor(9)try_then_request_governor(9)devfreq_update_target(9)update_devfreq(9)devfreq_monitor(9)devfreq_monitor_start(9)devfreq_monitor_stop(9)devfreq_monitor_suspend(9)devfreq_monitor_resume(9)devfreq_update_interval(9)devfreq_notifier_call(9)qos_notifier_call(9)qos_min_notifier_call(9)qos_max_notifier_call(9)devfreq_dev_release(9)devfreq_add_device(9)devfreq_remove_device(9)devm_devfreq_add_device(9)devm_devfreq_remove_device(9)devfreq_suspend_device(9)devfreq_resume_device(9)devfreq_suspend(9)devfreq_resume(9)devfreq_add_governor(9)devm_devfreq_add_governor(9)devfreq_remove_governor(9)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)devfreq_register_notifier(9)devm_devfreq_register_notifier(9)
like, that's the whole group chat right there π₯ and yes, devm_devfreq_register_notifier(9) is the register-side twin β the way that they're literally a matched set ππ
ngl if you're looking for the function that does the registering, it's right there at the bottom of the list. we love a symmetrical moment.
anyway that's the page!! short, sweet, and completely carried by the resource-managed concept π
sign-off time π this lil beauty lives in ./drivers/devfreq, and the date on it is October 2026 β so yeah, she's from the future, no cap ππ
periodt. π β¨
π¦ 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