_init_clocks(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸŽ€ _init_clocks(9) πŸŽ€

πŸ’– NAME πŸ’–

okay so bestie, this page is from the Kernel API Manual, and it's all about _init_clocks β€” the one that does clk_get() on all clocks associated with this hwmod. Retrieve as well the clockdomain. It's giving β€œcollect the whole clock crew” energy, no cap. 🫢

✨ SYNOPSIS ✨

int _init_clocks (struct omap_hwmod *oh , struct device_node *np );

πŸŽ€ ARGUMENTS πŸŽ€

  • oh β€” struct omap_hwmod *; the hwmod we're working with. Main character energy.
  • np β€” device_node mapped to this hwmod. The device-tree bestie.

πŸ’– DESCRIPTION πŸ’–

So this one is called by omap_hwmod_setup_*() (after omap2_clk_init). It resolves all clock names embedded in the hwmod. That's the vibe: find the clock names, handle them.

It returns 0 on success, or a negative error code on failure. So 0 is the slay outcome; anything negative means something went wrong, and you should definitely notice, bestie. 😭

πŸ¦‹ SEE ALSO πŸ¦‹

Kernel file: ./arch/arm/mach-omap2/omap_hwmod.c. And yes, the whole reference squad is here β€” all of them, don't skip πŸ’€:

mwah πŸ’‹ β€” footer vibes: source/version ./arch/arm/mach-omap2, October 2026, page _init_clocks(9).

πŸ“¦ where this page comes from