devfreq_update_target(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… devfreq_update_target β€” kernel API manual, but make it make sense

okay bestie, so this one is a kernel function called devfreq_update_target, and it lives in the Kernel API Manual. No cap, the whole point of it is: reevaluate the device and configure frequency on the final stage. That's the vibe. It's the last-stop, final-stage glow-up moment for your device's frequency. ✨


πŸ¦‹ SYNOPSIS

int devfreq_update_target (struct devfreq *devfreq , unsigned long freq );

that's it, that's the whole signature. returns an int, takes two things, we're gonna go through them one by one, i promise. 🫢


πŸŽ€ ARGUMENTS

  • devfreq β€” the devfreq instance. your actual device object, the main character of this whole story πŸ‘‘
  • freq β€” the new frequency of the parent device. and listen, this one has a very specific lane: this argument is only used for devfreq devices using the passive governor. like, only then. do not come for it otherwise, it's not for you πŸ’€

🌸 NOTE

bestie. read this twice. Lock devfreq->lock before calling devfreq_update_target. do not skip the lock. the lock is not optional, the lock is the whole personality.

and the other thing: this function should only be used by both update_devfreq and devfreq governors. it's not a general-purpose lil helper you sprinkle on your code like glitter. it's an inside job, iykyk. πŸ™ˆ


⭐ SEE ALSO

the whole extended friend group, and yes they all have (9) after their names because that's the section, we don't make the rules:


and that's the page!! mwah πŸ’‹ this whole thing ships out of ./drivers/devfreq and it's dated October 2026, so like, future-coded of it honestly. slay. πŸŒˆπŸŽ€

πŸ“¦ where this page comes from