_enable(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– NAME πŸ’–

okay so this is the _enable(9) page from the Kernel API Manual, and the whole point is: _enable β€” enable an omap_hwmod. that's the task, bestie. ✨

✨ SYNOPSIS ✨

int _enable (struct omap_hwmod *oh );

πŸŽ€ ARGUMENTS πŸŽ€

  • oh β€” this is a struct omap_hwmod *, aka the hwmod you're about to enable. πŸ’…

πŸ¦‹ DESCRIPTION πŸ¦‹

So _enable enables an omap_hwmod named oh so that the MPU can access that hwmod's register target. iconic behavior, honestly. πŸ‘‘

It returns -EINVAL if the hwmod is in the wrong state, or it passes along the return value of _wait_target_ready. like, whatever that call hands back, _enable hands it right to you. no extra drama. 😭

bestie reminder: wrong state = -EINVAL; and _enable is not out here inventing new return values, okay? 🫢

🌈 SEE ALSO 🌈

Kernel file: ./arch/arm/mach-omap2/omap_hwmod.c.

The related-API group chat is genuinely huge, so here's the whole squad:


mwah πŸ’‹ that's the whole page, and the footer tea is: source ./arch/arm/mach-omap2, date October 2026, manual name _enable(9). periodt. πŸŽ€βœ¨

πŸ“¦ where this page comes from