CLK NOTIFIER CALLBACK TYPES(9)

📦 version 7.3.1, in nixpkgs unstable

💅 clk notifier callback types(9) 💅

ok so this is from the Kernel API Manual bestie, and it's literally all about the three callback types your clk notifier can get hit with 🎀 buckle up, it's short but it MATTERS.

🌸 PRE_RATE_CHANGE 🌸

okay so PRE_RATE_CHANGE gets called immediately before the clk rate is changed — it's basically the heads-up text before the situation actually goes down, telling you the rate change is gonna proceed fr fr. 🦋

bestie listen: drivers must immediately terminate any operations that will be affected by the rate change. no cap, immediately. 😭

Callbacks may either return NOTIFY_DONE, NOTIFY_OK, NOTIFY_STOP or NOTIFY_BAD.

💀 ABORT_RATE_CHANGE 💀

so ABORT_RATE_CHANGE gets called if the rate change failed for some reason after PRE_RATE_CHANGE happened. in that case, all registered notifiers on the clk will be called with ABORT_RATE_CHANGE — like a group chat broadcast of bad news, everyone gets it 🙈

Callbacks must always return NOTIFY_DONE or NOTIFY_OK. that's the whole vibe check, no other returns allowed 💅

✨ POST_RATE_CHANGE ✨

and then POST_RATE_CHANGE gets called after the clk rate change has successfully completed — the celebratory confetti moment 🎀🌈

Callbacks must always return NOTIFY_DONE or NOTIFY_OK. same deal. periodt. 👑

🫶 SEE ALSO 🫶

Kernel file ./include/linux/clk.h plus a whole roster of icons, so let's go down the list bestie:

that's the whole page babes, ily, go forth and notifier responsibly 💜

sign-off szn: this one lives in ./include/linux, dated October 2026, and it's clk notifier callback types(9) — catch you on the next manpage bestie 🎀✨

📦 where this page comes from