omap2_clkops_enable_clkdm(9)

💅 omap2_clkops_enable_clkdm(9) 💅

okay so bestie, welcome to the Kernel API Manual ✨ — yes, that's the manual name, and yes, this page lives in it, right next to all the other little clock functions. we're talking omap2_clkops_enable_clkdm(9) today, and honestly? she's a small function with big main character energy 👑

---

🌸 NAME 🌸

omap2_clkops_enable_clkdm — increment usecount on clkdm of @hw 💖

like, that's literally the whole job description. increment the usecount. on the clkdm. of @hw. she's focused. she's not doing extra. periodt.

---

🎀 SYNOPSIS 🎀

int omap2_clkops_enable_clkdm (struct clk_hw *hw );

one function, one argument, one int coming back at you. no cap, that's it 🫶

---

🦋 ARGUMENTS 🦋

• hw — a struct clk_hw * of the clock being enabled. that's the clock you're turning on, bestie, she's the one getting the glow-up ✨

---

🔥 DESCRIPTION 🔥

okay so here's the vibe: this function increments the usecount of the clockdomain of the clock that hw points to. it's giving "keep track of who's using this thing" energy, and it does it by bumping that number up by one 💅

and the cute part? if the usecount is 1, the clockdomain will be "enabled." (yes, in quotes in the original, so we're keeping the quotes — she's enabled, with a little sparkle ✨). first one in turns on the lights, iykyk.

now the part where you gotta pay attention, bestie, because this is the only needed for clause and it matters 👀

this is Only needed for clocks that don't use omap2_dflt_clk_enable as their enable function pointer. if your clock already uses omap2_dflt_clk_enable, you do not need this. she's for the special cases. the ones doing their own thing. the individuallists 💜

and what does she return? so glad you asked, because it's one of three things:

• she passes along the return value of clkdm_clk_enable — whatever that gives back, she hands it straight to you, no edits, no notes 🫡
• -EINVAL if hw is not associated with a clockdomain — i.e. there's no clkdm to even talk about, and she's telling you that gently but firmly 😭
• 0 if clock framework-based clockdomain control is not implemented — so like, the mechanism isn't there, nothing to do, here's a zero, have a nice day 🌈

---

⭐ SEE ALSO ⭐

• Kernel file ./drivers/clk/ti/clockdomain.c — go read the source, bestie, it's right there 📖
• omap2_clkops_disable_clkdm(9) — the other half of the duo, the "turn it back off" one 🦋
• omap2_init_clk_clkdm(9) — the setup era 🎀
• ti_dt_clockdomains_setup(9) — device tree clockdomain setup, very demure, very mindful 🌸

---

kisses and good luck out there 💖 this page was brought to you by the source tree at ./drivers/clk/ti and it's dated October 2026 — so yeah, she's from the future, and she slayed 💅✨👑