omap2_clk_provider_init(9)

💅 omap2_clk_provider_init — from the Kernel API Manual, bestie ✨

Okay so we're in omap2_clk_provider_init(9) territory, and lowkey this one is the main character of clock provider setup. Buckle up 🎀

---

🌸 NAME 🌸

omap2_clk_provider_init — init master clock provider 👑

---

✨ SYNOPSIS ✨

int omap2_clk_provider_init (struct device_node *parent , int index ,
struct regmap *syscon , void __iomem *mem );

---

🦋 ARGUMENTS 🦋

• parent — the master node, fr fr. The big boss node. 🌳
• index — the internal index for clk_reg_ops. iykyk 🔢
• syscon — a syscon regmap pointer, used for accessing the clock registers. 💫
• mem — an iomem pointer for the clock provider memory area. Heads up bestie: this one's only used if syscon is not provided. 🙈

---

💖 DESCRIPTION 💖

So what does it actually do? It initializes a master clock IP block. Basically it sets up the mapping from the clocks node over to the memory map index. ✨

Then — and this is the slay part — all the clocks get initialized through the common of_clk_init call, and the clocks will access their memory maps based on the node layout. It's giving organized. It's giving structured. It's giving iconic mapping energy. 🌈

Returns 0 in success. 🫶

---

🔥 SEE ALSO 🔥

Kernel file ./drivers/clk/ti/clk.c — and the whole friend group:

• 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_legacy_provider_init(9)
• ti_dt_clk_init_retry_clks(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)

---

Okay that's the whole page, no notes 💅 Huge shoutout to ./drivers/clk/ti — that's the source/version tag — dated October 2026, living under the Kernel API Manual banner as omap2_clk_provider_init(9). Go read some clocks, bestie, you've got this 🧚💜