pm_clk_list_lock(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸŽ€ pm_clk_list_lock(9) β€” Kernel API Manual πŸŽ€

okay so bestie, welcome to the Kernel API Manual page for pm_clk_list_lock(9) β€” this one is short, iconic, and all about locking before you touch the PM clock entry list. πŸ’…

✨ NAME ✨

pm_clk_list_lock β€” ensure exclusive access for modifying the PM clock entry list. That's literally the assignment, no cap. 🫢

🌸 SYNOPSIS 🌸

void pm_clk_list_lock (struct pm_subsys_data *psd );

πŸ¦‹ ARGUMENTS πŸ¦‹

  • psd β€” the pm_subsys_data instance corresponding to the PM clock entry list and the clk_op_might_sleep count that's about to be modified. This is your main-character argument, bestie. ✨

πŸ’– DESCRIPTION πŸ’–

Okay so the vibe here: get exclusive access before you modify the PM clock entry list and the clock_op_might_sleep count, because we're guarding against concurrent modifications. No chaotic edits allowed, periodt. πŸ”₯

This also protects against a concurrent clock_op_might_sleep and PM clock entry list usage in pm_clk_suspend/pm_clk_resume that may or may not happen in atomic context. That's why both the mutex and the spinlock must be taken here β€” yes, both, bestie. πŸ’…

🌈 SEE ALSO 🌈

Kernel file ./drivers/base/power/clock_ops.c is the source-file bestie, and the whole squad is: 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), enable_clock(9), disable_clock(9), pm_clk_notify(9), pm_clk_add_notifier(9).

mwah πŸ’‹ β€” this page ships from ./drivers/base/power, is dated October 2026, and belongs to pm_clk_list_lock(9) 🫢

πŸ“¦ where this page comes from