devm_clk_put(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… devm_clk_put(9)

okay bestie, so this page lives in the Kernel API Manual and it's all about letting go of a clock the ~managed~ way. releasing your grip, but make it devres. 🫢


✨ NAME ✨

devm_clk_put β€” "free" a managed clock source. that's it, that's the whole vibe. it's your official clock-drop. πŸŽ€


πŸŽ€ SYNOPSIS πŸŽ€

void devm_clk_put (struct device *dev , struct clk *clk );

literally the entire function signature, no surprises, no plot twist. πŸ’…


πŸ¦‹ ARGUMENTS πŸ¦‹

  • dev β€” the device you used to acquire the clock. it's the whole reason this is a managed clock, so don't forget who got you here. 🧚
  • clk β€” the clock source itself, and not just any clock: the one you got with devm_clk_get. πŸ’–

πŸ’€ NOTE πŸ’€

drivers must ensure that all clk_enable calls made on this clock source are balanced by clk_disable calls prior to calling this function. unbalanced enables? that's a no from the kernel, fr fr. πŸ”₯
clk_put should not be called from within interrupt context. nope, not in an IRQ, not in your interrupt-era. πŸ™ˆ

🌈 SEE ALSO 🌈

the whole clock friend group showed up, no cap:

like I said. everyone. πŸ’œ


🌸 k thx bye 🌸

this little page came to you straight from ./include/linux and it's dated October 2026 β€” so yeah, future-coded and iconic. go balance those enables and stay out of interrupt context, bestie. slay πŸ’…βœ¨πŸŽ€

πŸ“¦ where this page comes from