__pm_clk_enable(9)

💖 NAME 💖

okay so bestie, meet __pm_clk_enable — it enables a clock, and it's not shy about reporting any errors while it does it. ✨

this one lives in the Kernel API Manual (yes, the kernel has lore 💅).

---

✨ SYNOPSIS ✨

void __pm_clk_enable (struct device *dev , struct pm_clock_entry *ce );

that's the whole vibe: return type void, two args, no cap. 🫶

---

🎀 ARGUMENTS 🎀

• dev — the device that owns the clock you're messing with. like, whose clock is this? this one. 🫵
• ce — the PM clock entry that corresponds to the clock. the lil handle for the actual clock, iykyk. ⏰

---

🦋 SEE ALSO 🦋

first up, the source of truth: kernel file ./drivers/base/power/clock_ops.c — go read it, it's giving main character energy. 📖🔥

and then the whole clock-ops friend group, all together, all iconic:

• pm_clk_list_lock(9)
• pm_clk_list_unlock(9)
• pm_clk_op_lock(9)
• pm_clk_op_unlock(9)
• pm_clk_acquire(9)
• pm_clk_add(9)
• pm_clk_add_clk(9)
• of_pm_clk_add_clks(9)
• __pm_clk_remove(9)
• pm_clk_remove_clk(9)
• pm_clk_init(9)
• pm_clk_create(9)
• pm_clk_destroy(9)
• pm_clk_suspend(9)
• pm_clk_resume(9)
• pm_clk_notify(9)
• enable_clock(9)
• disable_clock(9)
• pm_clk_notify(9) ← yes bestie it's listed twice, and honestly? she deserves the double feature 💀🌸
• pm_clk_add_notifier(9)

---

ngl the whole "reporting any errors" thing in the NAME is the moment of truth here — that's the actual pitch of this function, so don't sleep on it. 👑

---

and that's the page!! source/version: ./drivers/base/power, dated October 2026 — stamped, sealed, slayed. 🎀💜 bye bestie, go enable some clocks responsibly 🕰️✨