ti_dt_clk_init_retry_clks(9)

💅 ti_dt_clk_init_retry_clks 💅

okay so this is a page from the Kernel API Manual, section 9 — yes bestie, the kernel kernel, we're in the big leagues now 🫶

✨ NAME ✨

ti_dt_clk_init_retry_clks — the function that goes back and inits the clocks from the retry list 🔁

🌸 SYNOPSIS 🌸

void ti_dt_clk_init_retry_clks (void );

🎀 ARGUMENTS 🎀

• void — literally no arguments. nothing. zero. she takes nothing and she gives everything 👑

🦋 DESCRIPTION 🦋

So here's the vibe: this one initializes any clocks that failed to initialize before. why did they fail? because their parent node(s) were missing during an earlier init 😭 like showing up to the party before the party even started.

This typically only happens for DPLLs which need to have both of their parent clocks ready during init. both. not one. both. the way that DPLLs are so high-maintenance 💅

tl;dr — it's the cleanup crew that comes back once the parents finally show up. no cap. 🔥

⭐ SEE ALSO ⭐

• Kernel file ./drivers/clk/ti/clk.c
• ti_clk_setup_ll_ops(9)
• ti_dt_clocks_register(9)
• ti_clk_retry_init(9)
• ti_clk_get_reg_addr(9)
• ti_clk_get_legacy_bit_shift(9)
• omap2_clk_provider_init(9)
• omap2_clk_legacy_provider_init(9)
• ti_dt_clk_name(9)
• ti_clk_add_aliases(9)
• ti_clk_setup_features(9)
• ti_clk_get_features(9)
• omap2_clk_enable_init_clocks(9)
• ti_clk_add_alias(9)
• of_ti_clk_register(9)
• of_ti_clk_register_omap_hw(9)
• omap2_clk_for_each(9)
• omap2_clk_is_hw_omap(9)

and that's the whole page babes 💖 source is ./drivers/clk/ti, dated October 2026, and the page itself is ti_dt_clk_init_retry_clks(9). go read the rest of the clk family, they all ate 🌈👑