clk_hw_register_divider(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… clk_hw_register_divider

okay so bestie, welcome to the clk_hw_register_divider(9) page from the Kernel API Manual ✨ β€” this is the one where you tell the clock framework "hey, here's a divider clock, pls take care of it" πŸŽ€


🌸 NAME 🌸

clk_hw_register_divider β€” register a divider clock with the clock framework πŸ•°οΈβœ¨


πŸ¦‹ SYNOPSIS πŸ¦‹

clk_hw_register_divider (dev , name , parent_name , flags , reg , shift
, width , clk_divider_flags , lock );

like, that's the whole call, no cap πŸ’…


✨ ARGUMENTS ✨

okay so here's every single thing you gotta hand over, one by one 🫢

  • dev β€” the device that's registering this clock. it's giving "this is my clock, I'm its person" πŸ’–
  • name β€” the name of this clock. yep, you gotta name it. main character energy πŸ‘‘
  • parent_name β€” the name of the clock's parent. every icon needs an ancestor fr fr 🌈
  • flags β€” framework-specific flags. the vibe check parameters, if you will ⭐
  • reg β€” the register address to adjust the divider. this is where the actual bits live 🏠
  • shift β€” how many bits to shift the bitfield. slide to the left, slide to the right πŸ’ƒ
  • width β€” the width of the bitfield. how many bits wide this whole situation is πŸ“
  • clk_divider_flags β€” divider-specific flags for this clock. yes, there are two kinds of flags, don't @ me πŸ™ˆ
  • lock β€” a shared register lock for this clock. sharing is caring, but like, thread-safely πŸ”’
ngl, if you mix up flags and clk_divider_flags that's a whole mood and also probably a bug. two different flag piles, bestie πŸ’€

πŸ”₯ SEE ALSO πŸ”₯

the whole friend group, assembled 🌸 grab a snack, this is a long guest list:


k that's the whole page, you ate that πŸ’…βœ¨

this lil love letter lives in ./include/linux πŸ“ version date October 2026 🌸 and it's still out here being clk_hw_register_divider(9) β€” mwah, bye bestie, go register some clocks πŸŽ€πŸ¦‹πŸ’œ

πŸ“¦ where this page comes from