clk_enable_regmap(9)

💅 clk_enable_regmap — from the Kernel API Manual, section 9, bestie 🎀

Okay so picture this: you're a kernel clock driver, you're doing all your register I/O through regmap, and your enable operation is literally always the same three lines. Girl. Same. That's exactly why this function exists — it's the standard enable() for regmap users, and it's about to save you so much code. ✨

---

✨ SYNOPSIS ✨

int clk_enable_regmap (struct clk_hw *hw );

---

🫶 ARGUMENTS 🫶

• hw — the clk you're operating on. That's it, that's the whole argument. Main character energy, honestly. 💅

---

🌸 DESCRIPTION 🌸

So here's the vibe: if your clocks use regmap for their register I/O, you set the enable_reg and enable_mask fields in your struct clk_regmap, and then you just point this function at your enable operation. Done. No cap. 🦋

It's giving "write less boilerplate," it's giving "the framework handles it," and it genuinely saves you some code. Since these clocks already know where the enable bit lives and which bit it is, there's no reason for every single driver to hand-roll the same thing. Reuse the icon, periodt. 👑

---

🔥 SEE ALSO 🔥

• Kernel file ./drivers/clk/qcom/clk-regmap.c 💜
• clk_is_enabled_regmap(9)
• clk_disable_regmap(9)
• devm_clk_register_regmap(9)

---

ngl, if you're poking around clk-regmap.c anyway, those three siblings up there are your next stops — like a little friend group of regmap clock helpers. 😭🫶

---

And that's the whole page, bestie! 🌈 This lil' gem comes to you from ./drivers/clk/qcom, dated October 2026, and it's filed under clk_enable_regmap(9) in the Kernel API Manual — go forth and stop reimplementing enable, mwah! 💖🎀🧚