omap3xxx_cm...module_ready(9)

📦 version 7.3.1, in nixpkgs unstable

💅 omap3xxx_cm_wait_module_ready(9) — from the Kernel API Manual, bestie 🫶

okay so this is omap3xxx_cm_wait_module_ready, and it's lowkey serving "wait for the PRCM to tell us the module is clocked" energy ✨ no cap.

✨ NAME ✨

omap3xxx_cm_wait_module_ready — literally just: wait for a module to leave idle or standby 💤➡️🔥

🎀 SYNOPSIS 🎀

int omap3xxx_cm_wait_module_ready (u8 part , s16 prcm_mod , u16 idlest_id , u8 idlest_shift );

like, that's the whole vibe check. four args, one int coming back at you 💖

🌸 ARGUMENTS 🌸

  • part — the PRCM partition. and bestie… it's ignored for OMAP3 🙈 so yeah, it's there, it's cute, it does nothing on this chip. iconic honestly.
  • prcm_mod — the PRCM module offset. this one actually matters fr fr.
  • idlest_id — the CM_IDLESTx register ID, so like x = 1, 2, 3 👑
  • idlest_shift — the shift of the bit inside that CM_IDLEST* register that you're checking. like, which bit are we side-eyeing 💅

🦋 DESCRIPTION 🦋

so basically ✨ you wait for the PRCM to indicate that the module identified by (prcm_mod, idlest_id, idlest_shift) is clocked.

that's it. that's the whole function. it just sits there and waits for the PRCM to say "okay she's clocked" 🎀

it returns 0 upon success 🎉 or -EBUSY if the module doesn't enable in time 😭 (yeah, the classic "didn't make it in time" moment — no notes, just pain).

⚠️ heads up: -EBUSY is a real return value here, not a vibe. if the module doesn't enable in time, you get -EBUSY. don't @ me, that's just what the page says 💀

🌈 SEE ALSO 🌈

  • Kernel file ./arch/arm/mach-omap2/cm3xxx.c — like, go read the source bestie 🧚
  • omap3xxx_cm_split_idlest_reg(9) — the sibling function, same universe, different quest ⭐

and that's the tea ☕ — this little gem lives under ./arch/arm/mach-omap2, dated October 2026, from the Kernel API Manual, and it's giving main character energy all the way to the footer 💜 iykyk 🦋

📦 where this page comes from