clk_hw_regis...te_parent_hw(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ‘‘ NAME πŸ‘‘

clk_hw_register_gate_parent_hw β€” bestie, it registers a gate clock with the clock framework πŸŽ€ (yes, this is a Kernel API Manual page, and yes it's about to be your new obsession ✨)


✨ SYNOPSIS ✨

clk_hw_register_gate_parent_hw (dev , name , parent_hw , flags , reg ,
bit_idx , clk_gate_flags , lock );

🌸 ARGUMENTS 🌸

okay so here's the whole cast, no cap πŸ’…

  • dev β€” the device that is registering this clock. it's giving "who's the parent here" energy 🫢
  • name β€” the name of this clock. name your child, legend ✨
  • parent_hw β€” pointer to parent clk. the main character's main character 😭 πŸ’–
  • flags β€” framework-specific flags for this clock. iykyk 🌈
  • reg β€” register address to control gating of this clock. this is the address, fr fr πŸ“
  • bit_idx β€” which bit in the register controls gating of this clock. one single bit carries the entire vibe check πŸ‘‘
  • clk_gate_flags β€” gate-specific flags for this clock. different flags, different vibe πŸ’«
  • lock β€” shared register lock for this clock. everybody shares, we love to see it πŸ”’

πŸ¦‹ SEE ALSO πŸ¦‹

the whole friend group, literally 😭 β€”


that's the whole page, bestie β€” every flag, every argument, every single SEE ALSO, all intact πŸ’– go forth and register that gate clock πŸ§šβ€β™€οΈ

and that's a wrap 🎬 this iconic little page lives in ./include/linux and it's dated October 2026 β€” see you in the next kernel release, mwah πŸ’‹ slay

πŸ“¦ where this page comes from