enable_clock(9)

💖 enable_clock(9) — the Kernel API Manual, bestie edition 💖

okay so you're reading a page from the Kernel API Manual (yes, that manual, the kernel one, we're doing this) and the whole entire vibe is: turn a device clock ON. that's it. that's the function. let's get into it 🫶

---

✨ NAME ✨

enable_clock — Enable a device clock. literally what it says on the tin, no cap 💅

---

🌸 SYNOPSIS 🌸

void enable_clock (struct device *dev , const char *con_id );

she takes two things and returns void, so don't go looking for a return value, there isn't one, periodt ✨

---

🦋 ARGUMENTS 🦋

• dev — the struct device whose clock we're enabling. this is the main character, the device in question, the one getting its clock turned on 🔥
• con_id — the Connection ID of the clock. yep, the con_id. that's the string that tells everyone which clock we mean 👑

ngl, that's the whole argument list. two args, both kinda important, neither optional-looking. slay 💀

---

🎀 SEE ALSO 🎀

bestie the reading list is LONG and honestly iconic for it. the kernel file to go look at is ./drivers/base/power/clock_ops.c, and then there's the whole friend group:

• pm_clk_list_lock(9)
• pm_clk_list_unlock(9)
• pm_clk_op_lock(9)
• pm_clk_op_unlock(9)
• __pm_clk_enable(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)
• disable_clock(9)
• pm_clk_notify(9)
• pm_clk_add_notifier(9)

(and yes, pm_clk_notify(9) is in there twice. not a typo, not me being messy, that's just the list. she said "be seen" twice and honestly? respect 🌈)

---

that's the whole page!! go forth and enable some clocks, you've got this, ./drivers/base/power edition, dated October 2026 — mwah 💜✨