ti_clk_get_reg_addr(9)

💅 NAME 💅

okay so welcome to the Kernel API Manual page for ti_clk_get_reg_addr — we're getting the register address for a clock register, and it's giving very specific kernel-clock realness ✨

🎀 SYNOPSIS 🎀

int ti_clk_get_reg_addr (struct device_node *node , int index , struct clk_omap_reg *reg );

✨ ARGUMENTS ✨

• node — device node for the clock, the whole tree-info moment 🌳
• index — register index from the clock node, iykyk 🔢
• reg — pointer to target register struct, aka where the answer gets dropped off 🎯

💖 DESCRIPTION 💖

So ti_clk_get_reg_addr builds the clock register address from device tree information, and returns the data via the provided output pointer reg. On success it returns 0; on failure it returns a negative error value. Slay? More like slay-ng return-value check 💅

🌈 SEE ALSO 🌈

Kernel file: ./drivers/clk/ti/clk.c — and the whole linked bestie squad is, no cap:

• ti_clk_setup_ll_ops(9)
• ti_dt_clocks_register(9)
• ti_clk_retry_init(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(9)
• of_ti_clk_register_omap_hw(9)
• omap2_clk_for_each(9)
• omap2_clk_is_hw_omap(9)

later bestie 💖 — this little manual moment comes from source/version ./drivers/clk/ti, dated October 2026, and it's the ti_clk_get_reg_addr(9) page. periodt ✨