of_ti_fixed_...or_clk_setup(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ¦‹ of_ti_fixed_...or_clk_setup(9) πŸ¦‹

okay bestie so this is a page from the Kernel API Manual, section 9 β€” yes, the grown-up kernel section, we're being so serious today πŸ’… don't worry though, I've got you.


✨ NAME ✨

of_ti_fixed_factor_clk_setup β€” the setup function for the TI fixed factor clock. that's it, that's the whole job. she does one thing and she does it well, periodt πŸ‘‘


🌸 SYNOPSIS 🌸

void of_ti_fixed_factor_clk_setup (struct device_node *node );

that's the whole signature. no return value, no drama β€” it's a void, she gives nothing back and honestly? iconic πŸŽ€


πŸ’– ARGUMENTS πŸ’–

  • node β€” the device node for this clock. like, this specific clock's device node. that's your whole input, bestie, hand her the node and she's off πŸ¦‹

πŸ”₯ DESCRIPTION πŸ”₯

so what does she actually do? she sets up a simple fixed factor clock based on device tree info. that's the vibe check: you bring the device tree info, she builds you a fixed factor clock out of it. simple, fixed, factored. no cap ✨

ngl there's not a ton more to say here β€” the manpage is short and I refuse to make stuff up about her. if you want the full tea you gotta go read the source (see below πŸ‘€).

🌈 SEE ALSO 🌈

  • Kernel file ./drivers/clk/ti/fixed-factor.c β€” go read it, iykyk 🫢

and that's the whole page, bestie!! go forth and set up your fixed factor clocks πŸ’œ

β€” cute lil sign-off: this page lives in ./drivers/clk/ti, dated October 2026, and it was literally made for of_ti_fixed_...or_clk_setup(9). mwah πŸ’‹πŸŒΈ

πŸ“¦ where this page comes from