omap2_dflt_clk_enable(9)

💅 omap2_dflt_clk_enable(9) 💅

okay so welcome to the Kernel API Manual bestie, and today's main character is omap2_dflt_clk_enable — the girl whose whole job is turning a clock ON. in the hardware. fr fr. 🕐✨

---

✨ NAME ✨

omap2_dflt_clk_enable — enable a clock in the hardware 🌸

---

🦋 SYNOPSIS 🦋

int omap2_dflt_clk_enable (struct clk_hw *hw );

---

🎀 ARGUMENTS 🎀

• hw — a struct clk_hw *, aka the clock you're trying to enable. this is the one, the only, the pointer in question 💅

---

💖 DESCRIPTION 💖

so like. we're enabling the clock hw in the hardware. and it's a whole little ritual, bestie, let me walk you through it:

1. first we call into the OMAP clockdomain code to "enable" the corresponding clockdomain — but only if this is the first enabled user of that clockdomain. no cap, first one in switches the lights on for everybody. 🔥
2. then we program the hardware to actually enable the clock. iconic.
3. then we wait for the IP block that uses this clock to leave idle (if that's applicable — sometimes it's just vibing and doesn't need the wait). 😌

and what do we return, you ask? 🫶

• the error value from clkdm_clk_enable if that call terminated with an error 😭
• -EINVAL if hw has a null clock enable_reg 💀
• zero upon success — slay ✨

---

👑 SEE ALSO 👑

• Kernel file ./drivers/clk/ti/clkt_dflt.c
• _wait_idlest_generic(9)
• _omap2_module_wait_ready(9)
• omap2_clk_dflt_find_companion(9)
• omap2_clk_dflt_find_idlest(9)
• omap2_dflt_clk_disable(9) — the reverse queen 🧚
• omap2_dflt_clk_is_enabled(9) — the vibe check 💜

---

okay that's the whole page, go enable some clocks responsibly bb 🩷 this came from ./drivers/clk/ti and the date on it is October 2026 — mwah, talk later! 🍓💫