devm_clk_hw..._parent_data(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… NAME πŸ’…

So the manual page is called devm_clk_hw..._parent_data(9) β€” that's the header, bestie, and this whole lil doc lives in the Kernel API Manual. The actual function is devm_clk_hw_register_gate_parent_data, and what it does is register a gate clock with the clock framework. That's it, that's the whole vibe. Iconic. 🌸


✨ SYNOPSIS ✨

devm_clk_hw_register_gate_parent_data (dev , name , parent_data , flags
, reg , bit_idx , clk_gate_flags , lock );

okay so it literally takes eight arguments, no cap, we love a generous signature 🫢 every single one explained below, don't skip, i'll know πŸ”₯


πŸŽ€ ARGUMENTS πŸŽ€

  • dev β€” the device that's registering this clock. like, who's the main character here? this guy. πŸ‘‘
  • name β€” name of this clock. gotta introduce her properly πŸ’–
  • parent_data β€” parent clk data. the parent situation, the family tree, the lore 🌈
  • flags β€” framework-specific flags for this clock. ✨
  • reg β€” register address to control gating of this clock. this is where the gating magic happens πŸ“
  • bit_idx β€” which bit in the register controls gating of this clock. not just any bit, that bit. the chosen one πŸŽ€
  • clk_gate_flags β€” gate-specific flags for this clock. yes, different flags from the other flags. keep up bestie 😭
  • lock β€” shared register lock for this clock. sharing is caring, and also thread safety is slay πŸ’…

πŸ¦‹ SEE ALSO πŸ¦‹

Kernel file ./include/linux/clk-provider.h, plus the whole extended clock-provider friend group β€” iykyk, this is a long contact list:


ngl that's a lot of cross-references but every one of them is cited in the original, so go read them, bestie, they're all in the family 🧚

and that's a wrap on devm_clk_hw..._parent_data(9) from the Kernel API Manual β€” sourced out of ./include/linux with a date stamp of October 2026. mwah, go register your gate clock, periodt. πŸ’œπŸ¦‹

πŸ“¦ where this page comes from