omap_hwmod_setup_one(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… omap_hwmod_setup_one(9) β€” Kernel API Manual ✨

🌸 NAME 🌸

omap_hwmod_setup_one β€” set up a single hwmod. That's the whole assignment, bestie. 🫢

πŸ¦‹ SYNOPSIS πŸ¦‹

int omap_hwmod_setup_one (const char *oh_name );

πŸŽ€ ARGUMENTS πŸŽ€

  • oh_name β€” const char * name of the already-registered hwmod to set up. Like, it has to be already registered β€” don't roll up with a random string and expect main character magic. πŸ’…

✨ DESCRIPTION ✨

Okay so omap_hwmod_setup_one initializes and sets up a single hwmod. She's intended to be used for a small number of early devices, such as the timer IP blocks used for the scheduler clock. So this is very much "small guest list only" energy β€” not the whole hwmod fleet. ⏰✨

⚠️ Timing tea, no cap: this function must be called after omap2_clk_init. Do not skip that step, bestie. 😭

She resolves the struct clk names to struct clk pointers for each registered omap_hwmod. Also calls _setup on each hwmod. Returns -EINVAL upon error or 0 upon success. So when you see 0, that's the slay. When you see -EINVAL, that's the "not me crying in kernel" moment. πŸ’€πŸ’–

πŸ”₯ SEE ALSO πŸ”₯

Kernel file ./arch/arm/mach-omap2/omap_hwmod.c, plus the whole SEE ALSO squad β€” every single one, because we do not leave the group chat on read:


mwah πŸ’– cute little source/version footer tea: this page lives under ./arch/arm/mach-omap2, dated October 2026, and the page name/version vibe is omap_hwmod_setup_one(9). Byeee 🫢✨

πŸ“¦ where this page comes from