of_ti_clk_register(9)

💅 of_ti_clk_register(9) — the Kernel API Manual, bestie edition 🎀

okay so hi ✨ you're looking at of_ti_clk_register, straight out of section 9 of the Kernel API Manual, and honestly? she's a little glue function and she slays at it 💖

---

🌸 NAME 🌸

of_ti_clk_register — register a TI clock to the common clock framework 🕰️✨

---

🦋 SYNOPSIS 🦋

struct clk * of_ti_clk_register (struct device_node *node , struct
clk_hw *hw , const char *con );

---

🎀 ARGUMENTS 🎀

• node — the device node for this clock, like, the clock's whole address in the device tree 🌳
• hw — the hardware clock handle, the actual clk_hw thing itself 🫶
• con — the connection ID for this clock, her little name tag 💌

---

⭐ DESCRIPTION ⭐

So what she does is: she registers a TI clock to the common clock framework, and she adds a clock alias for it — two jobs, one function, main character energy 👑💅

If it works you get back a handle to the registered clock. If it doesn't work? You get an ERR_PTR value instead 😭 so like, please check with IS_ERR() before you go dereferencing, iykyk 🙈

---

🌈 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_provider_init(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_omap_hw(9)
• omap2_clk_for_each(9)
• omap2_clk_is_hw_omap(9)

---

ngl the SEE ALSO list is giving "tag yourself, I'm ti_clk_add_alias(9)" 😭💀

---

okay that's the whole page, mwah 💋 this came from ./drivers/clk/ti and it's dated October 2026 — go forth and register your clocks, bestie, you're gonna do amazing 🌟🦋🍓💜