pm_clk_notify(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… pm_clk_notify β€” the manual page (Kernel API Manual, bestie edition) πŸ’…

okay so welcome to pm_clk_notify(9), the notifier routine for when devices get added or removed, and honestly she's lowkey the glue holding the clock situation together. let's get into it 🫢


✨ NAME ✨

pm_clk_notify β€” Notify routine for device addition and removal. that's it, that's the vibe ✨


🌸 SYNOPSIS 🌸

int pm_clk_notify (struct notifier_block *nb , unsigned long action ,
       void *data );

πŸŽ€ ARGUMENTS πŸŽ€

  • nb β€” the notifier block object that this function is literally a member of. she knows her family πŸ‘‘
  • action β€” whatever operation the caller is out here carrying out. main character behaviour fr fr
  • data β€” the device this routine is being run for. yes bestie, that device πŸ’–

πŸ¦‹ DESCRIPTION πŸ¦‹

okay so for this function to actually work β€” and we do want her to work β€” nb must be a member of an object of type struct pm_clk_notifier_block that's containing all of the requisite data. no shortcuts, no vibes-only setup 🫢

specifically?? the con_ids member of that object is the one doing the heavy lifting β€” it's used to enable or disable the device's clocks, depending on action. so action comes in, con_ids handles the clock enable/disable situation accordingly, and the whole thing just works. iconic, honestly πŸ’…


πŸ”₯ SEE ALSO πŸ”₯

Kernel file ./drivers/base/power/clock_ops.c β€” that's where she lives 🏠

the whole friend group, all of them slay ⭐


and that's the page!! 🌈 this lil cutie comes from <purple>./drivers/base/power</purple> and is dated <mint>October 2026</mint>, and yes she's still showing up as pm_clk_notify(9) in the index β€” periodt πŸ’…πŸ’–βœ¨

πŸ“¦ where this page comes from