pm_clk_op_unlock(9)

💅 pm_clk_op_unlock(9) 💅

okay bestie, welcome to the Kernel API Manual ✨ — grab a lil snack 🍓 because this one is short and sweet and honestly kind of iconic for it.

✨ NAME ✨

pm_clk_op_unlock — it's literally the counterpart to pm_clk_op_lock(). that's it. that's the whole vibe 🎀 like, they're a matching set, you can't have one without the other, iykyk 🫶

🌸 SYNOPSIS 🌸

void pm_clk_op_unlock (struct pm_subsys_data *psd , unsigned long *flags
);

the way that signature just sits there and does its thing 💅 it returns void, so like — no reward, no little return value to obsess over, she just does the unlock and leaves 🌈

🦋 ARGUMENTS 🦋

• psd — the same pm_subsys_data instance you previously passed to pm_clk_op_lock. yes, the SAME one, bestie 🙈 not a lookalike, not a cousin, the actual same instance. it's giving "you had one job" energy but make it a lock pairing 😭
• flags — the irq flags that pm_clk_op_lock handed you. like, the lock gives you these flags, and you give them right back here. it's a whole handoff situation 🤝 do not lose them, do not improvise your own, just pass the ones you got 💀

🔥 SEE ALSO 🔥

the kernel file ./drivers/base/power/clock_ops.c is where all this lives, and if you wanna go down the whole rabbit hole (and honestly? you should 👑), here's the full squad:

• pm_clk_list_lock(9)
• pm_clk_list_unlock(9)
• pm_clk_op_lock(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)
• enable_clock(9)
• disable_clock(9)
• pm_clk_notify(9) — yes she's listed twice, and honestly? double the notify, double the slay ⭐
• pm_clk_add_notifier(9)

okay that's the whole page, you ate that 💖 before you go, tiny sign-off: this lil masterpiece lives under ./drivers/base/power 🌸 and the date stamp on it is October 2026 🎀 so like, future vibes only, no cap. mwah 💋 🧚‍♀️ periodt