clk_hw_regis...ent_accuracy(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… clk_hw_regis...ent_accuracy(9) πŸ’…

okay bestie, welcome to the Kernel API Manual ✨ β€” yes this is that one page, clk_hw_regis...ent_accuracy(9), and it's literally about registering a fixed-rate clock with the clock framework. iconic behaviour tbh πŸŽ€


🌸 NAME 🌸

clk_hw_register_fixed_rate_parent_accuracy β€” register fixed-rate clock with the clock framework πŸ•°οΈβœ¨

so basically: you got a clock, its rate does not move, and you want the framework to know about it. that's the whole vibe.


πŸ¦‹ SYNOPSIS πŸ¦‹

clk_hw_register_fixed_rate_parent_accuracy (dev , name , parent_data ,
       flags , fixed_rate );

look at her. five args, no notes. πŸ’…


πŸ‘‘ ARGUMENTS πŸ‘‘

  • dev β€” the device that is registering this clock 🫢 like, whose clock is this? this device's clock. periodt.
  • name β€” name of this clock 🏷️ give her a name, she deserves one.
  • parent_data β€” name of clock's parent 🌳 yes, the clock has a parent, it's giving family tree energy.
  • flags β€” framework-specific flags 🚩 the little toggles that tell the framework how to treat her.
  • fixed_rate β€” non-adjustable clock rate πŸ“ key word: non-adjustable. it does not change. not now, not ever. no cap.

🌈 SEE ALSO 🌈

the whole friend group, fr fr β€” go read these too:


bestie reminder 🫢 the parent is described as name of clock's parent and the rate is non-adjustable β€” don't show up expecting to change it, she said what she said πŸ’€

that's the whole page, go slay your clock registration πŸ§šπŸ’œ this little number lives in ./include/linux, dated October 2026, and it's clk_hw_regis...ent_accuracy(9) signing off β€” mwah πŸ’‹βœ¨

πŸ“¦ where this page comes from