clk_hw_regis...te_parent_hw(9)

📦 version 7.3.1, in nixpkgs unstable

💅 clk_hw_register_fixed_rate_parent_hw(9) — the Kernel API Manual, bestie edition 🎀

okay so this is a page straight out of the Kernel API Manual (that's the manual name, iykyk ✨) and it's all about one very specific little function. No cap, if you're here you're probably writing a clock driver, so let's go 🌸

✨ NAME ✨

clk_hw_register_fixed_rate_parent_hw — literally registers a fixed-rate clock with the clock framework. that's it, that's the whole vibe. a clock that does not adjust. iconic behavior 👑

🦋 SYNOPSIS 🦋

clk_hw_register_fixed_rate_parent_hw (dev , name , parent_hw , flags , fixed_rate );

five arguments, in that order, bestie. don't shuffle them 🙈

🌈 ARGUMENTS 🌈

  • dev — the device that's registering this clock. it's the one doing the paperwork, basically the main character of this call 💖
  • name — the name of this clock. give it a good one, people will be looking it up 🎀
  • parent_hw — a pointer to the parent clk. your clock's ancestry, its lore, its nepo-baby connection 🫶
  • flags — framework-specific flags. every framework has opinions, and these are them ⭐
  • fixed_rate — the non-adjustable clock rate. non-adjustable, meaning it does not move, it does not negotiate, it is simply that girl 💅

👑 SEE ALSO 👑

genuinely the longest see-also list i've ever seen and i'm obsessed with it. the Kernel file to go peek at is ./include/linux/clk-provider.h, and then there's the clk framework's own little friend group:

like, the whole clock family reunion 🧚💜 read them, they're all your besties too now.

💀 one little thing: this page gives you the arguments and the vibe, but it does not tell you what the function returns or what it does on failure. so don't go inventing that, ok? go read the header for the real tea 🍓

and that's the page!! brought to you by the lovely folks at ./include/linux, dated October 2026, and wrapped up in this very good-looking manual 🙈✨ slay, go register a clock, periodt 💖🦋🌸

📦 where this page comes from