devm_devfreq_add_device(9)

📦 version 7.3.1, in nixpkgs unstable

💖 devm_devfreq_add_device — the Kernel API Manual page you didn't know you needed 💖

okay so like, real talk bestie, this is a page straight out of the Kernel API Manual and it's about devm_devfreq_add_device, which is the resource-managed glow-up of devfreq_add_device(). it's giving "I handle the cleanup so you don't have to" energy and honestly? obsessed. ✨

🌸 NAME 🌸

devm_devfreq_add_device — the resource-managed version of devfreq_add_device(), no cap 🫶

✨ SYNOPSIS ✨

struct devfreq * devm_devfreq_add_device (struct device *dev , struct
       devfreq_dev_profile *profile , const char *governor_name , void *data );

like, it hands you back a struct devfreq *, that's the whole vibe 💅

🎀 ARGUMENTS 🎀

  • dev — the device that's getting the devfreq feature added to it. this is your main character device fr.
  • profile — the device-specific profile that devfreq is gonna run. it's the personality of the device, iykyk.
  • governor_name — the name of the policy that chooses the frequency. yes bestie, name — it's a const char *, not the governor itself.
  • data — the devfreq driver passes this along to the governors, and the governor should not change it. hands off 🚫

🦋 DESCRIPTION 🦋

so what this function does is it manages the memory of the devfreq device automatically using device resource management — like it just handles it for you — and it simplifies the free operation for the memory of the devfreq device. literally the "don't worry about it, I got u" friend of kernel APIs 💖

no manual cleanup arc for you. it's already handled. slay. ✨

🔥 SEE ALSO 🔥

okay this list is LONG and honestly iconic for it. here's every single one, in the exact order, because we do not skip entries in this house 👑

Kernel file ./drivers/devfreq/devfreq.c, plus:

bestie that is thirty-eight cross-references. thirty-eight. whoever wrote this page said "I will not be gatekeeping" and honestly? respect. 🌈

and that's the page!! this whole thing lives under ./drivers/devfreq, it's dated October 2026, and the header you'd normally see up top is devm_devfreq_add_device(9) — so yeah, that's your sign-off bestie. go read some devfreq source, you're gonna eat 💅✨🎀

📦 where this page comes from