devm_clk_hw..._parent_data(9)

📦 version 7.3.1, in nixpkgs unstable

💅 devm_clk_hw_register_fixed_rate_parent_data — a Kernel API Manual moment

okay so bestie, welcome to the Kernel API Manual ✨ this one's about registering a fixed-rate clock with the clock framework, and honestly? it's giving "I have a device, I have a very specific number, and I refuse to change it" 💅

🌸 NAME 🌸

devm_clk_hw_register_fixed_rate_parent_data — register fixed-rate clock with the clock framework 🎀

no cap, that's the whole thing. it registers. it's fixed-rate. it has parent data. she's a package deal ✨

🦋 SYNOPSIS 🦋

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

look at her 🫶 all lowercase, all business, five args and not one more.

💖 ARGUMENTS 💖

okay let's break down the group chat one by one 👑

  • dev — the device that is registering this clock. like, whose name is going on the lease bestie 🏠
  • name — name of this clock. she needs a name or nobody knows who she is 💅
  • parent_data — the parent clk data. that's her ancestry, her lore, her main character origin story 🌈
  • flags — framework-specific flags. little toggles that tell the framework how to treat her ⭐
  • fixed_rate — the non-adjustable clock rate. non-adjustable means non-adjustable, bestie — this number is not negotiating 😭 it's fixed, periodt 💀
quick vibe check: that's it, that's the whole argument list. no hidden extras, no secret sixth arg hiding in the replies 🙈

💅 SEE ALSO 💅

sit down and get comfy because this list is long and she ate 🔥 everything here lives in the kernel file ./include/linux/clk-provider.h and honestly it's the whole clk-provider fam reunion:

like I said — the whole fam 🫶 iykyk.

and that's the page, bestie 🌈 sourced from ./include/linux, dated October 2026, and filed under devm_clk_hw..._parent_data(9) in this very Kernel API Manual. slay, go register your fixed-rate clock, and hydrate 💖🧚‍♀️

📦 where this page comes from