tegra124_clock_init(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

🌸 tegra124_clock_init(9) β€” from the Kernel API Manual πŸ’…

okay so bestie, grab your iced coffee, because we're talking about tegra124_clock_init β€” the Tegra124-specific clock initialization girlie. she's in the kernel API manual, she's iconic, she's lowkey the reason your SoC clocks even wake up in the morning. ✨


✨ NAME ✨

tegra124_clock_init β€” Tegra124-specific clock initialization. that's it, that's the vibe. πŸŽ€


πŸ¦‹ SYNOPSIS πŸ¦‹

void tegra124_clock_init (struct device_node *np );

no cap, that's the whole signature. she returns nothing, she takes one thing, she slays. πŸ’…


πŸ’– ARGUMENTS πŸ’–

  • np β€” a struct device_node * pointing at the DT node for the SoC CAR IP block. that's her one (1) job: know which device tree node she's working with. 🫢

πŸ‘‘ DESCRIPTION πŸ‘‘

so here's the tea, bestie: this function registers most of the SoC clocks for the Tegra124 system-on-chip. most of this code is shared between the Tegra124 and Tegra132 SoCs, although some of the initial clock settings and CPU clocks differ β€” yes, they're siblings, not twins, and the differences are real. πŸ‘―

she's intended to be called by the OF init code when a DT node with the "nvidia,tegra124-car" string is encountered, and she's declared with CLK_OF_DECLARE. so the OF init code sees that magic string, and boom β€” she gets summoned. πŸͺ„

no return value. none. zero. she gives nothing back and honestly? main character energy. πŸ’€

πŸ”₯ SEE ALSO πŸ”₯


and that's the whole page, bestie β€” go forth and initialize those clocks 🌈

mwah πŸ’‹ β€” this one came from ./drivers/clk/tegra, dated October 2026, and she answers to the name tegra124_clock_init(9) whenever you call her. πŸŽ€βœ¨

πŸ“¦ where this page comes from