omap_cm_module_enable(9)

💅 omap_cm_module_enable(9) — straight from the Kernel API Manual, bestie ✨

okay so like, this is the page for omap_cm_module_enable(9) from the Kernel API Manual, and it's literally about enabling a module. group-chat energy but make it kernel internals, yk? 🫶

---

🌸 NAME 🌸

omap_cm_module_enable — enable a module 💖

---

🦋 SYNOPSIS 🦋

int omap_cm_module_enable (u8 mode , u8 part , u16 inst , u16
clkctrl_offs );

---

💅 ARGUMENTS 💅

• mode — target mode for the module ✨
• part — PRCM partition 🎀
• inst — PRCM instance 🌈
• clkctrl_offs — CM_CLKCTRL register offset for the module ⭐

---

🌸 DESCRIPTION 🌸

So what it does is enable clocks for a module identified by (part, inst, clkctrl_offs), which makes its IO space accessible. It's giving "let there be light" but for clocks and IO space, fr fr. 🔥

It returns 0 upon success, and -EINVAL if no per-SoC module_enable function pointer has been registered. Not me being dramatic about -EINVAL, it's literally in the docs. 😭

no cap: those return values are the whole vibe check here. 0 = slay, -EINVAL = the per-SoC module_enable function pointer was never registered. 💀

---

🔥 SEE ALSO 🔥

Kernel file ./arch/arm/mach-omap2/cm_common.c — and the friend group is:

• cm_split_idlest_reg(9)
• omap_cm_wait_module_ready(9)
• omap_cm_wait_module_idle(9)
• omap_cm_module_disable(9)
• cm_register(9)
• cm_unregister(9)
• omap2_cm_base_init(9)
• omap_cm_init(9)

---

mwah 💋 source: ./arch/arm/mach-omap2, version/date vibe: October 2026 — iconic, periodt. 👑