_omap2_module_wait_ready(9)

✨ NAME ✨

_omap2_module_wait_ready — wait for an OMAP module to leave IDLE

This one lives in the Kernel API Manual, bestie. It's giving "lowkey important kernel helper" energy.

---

🌸 SYNOPSIS 🌸

void _omap2_module_wait_ready (struct clk_hw_omap *clk );

---

💅 ARGUMENTS 💅

• clk — the struct clk * belonging to the module. Yep, that's the whole vibe: it's the clock handle for the module you're waiting on.

---

🦋 DESCRIPTION 🦋

Okay so here's the tea: if the necessary clocks for the OMAP hardware IP block that corresponds to clock clk are enabled, then this function waits for the module to indicate readiness — aka it waits for the module to leave IDLE. Iconic behaviour, honestly.

Real talk though: this code does not belong in the clock code, and it will be moved in the medium term to module-dependent code. So it's a little "living on borrowed time" situation. No cap.

And the return value? None. It's void, bestie — no return value, no notes, periodt.

---

🔥 SEE ALSO 🔥

Kernel file ./drivers/clk/ti/clkt_dflt.c and these absolute icons:

• _wait_idlest_generic(9)
• omap2_clk_dflt_find_companion(9)
• omap2_clk_dflt_find_idlest(9)
• omap2_dflt_clk_enable(9)
• omap2_dflt_clk_disable(9)
• omap2_dflt_clk_is_enabled(9)

---

That's the whole page, bestie 🫶 — sourced from ./drivers/clk/ti, dated October 2026, and yes, the manual is still calling itself _omap2_module_wait_ready(9) at the end like the main character it is 💅✨