devm_clk_hw_get_clk(9)

📦 version 7.3.1, in nixpkgs unstable

💖 devm_clk_hw_get_clk(9) — from the Kernel API Manual, bestie 💖

Okay so picture this: you're deep in the kernel, you need a clock, and you do not want to remember to clean it up later. Enter devm_clk_hw_get_clk. This is the resource-managed glow-up of clk_hw_get_clk(), and honestly? It ate. 🎀

✨ SYNOPSIS ✨

struct clk * devm_clk_hw_get_clk (struct device *dev , struct clk_hw *hw
, const char *con_id );

Yeah it's a whole three-argument situation — she's thorough, we respect it. 💅

🫶 ARGUMENTS 🫶

  • dev — the device that's registering this clock. Like, the one signing the permission slip 📝
  • hw — the clk_hw associated with the clk being consumed. This is the hardware-side bestie 🦋
  • con_id — the connection ID string on device. Her little name tag at the party 🏷️

🌸 DESCRIPTION 🌸

So this is the managed version of clk_hw_get_clk. The way that works is: any clocks you get with this function get automatically clk_put on driver detach. No manual cleanup, no leaks, no 3am panic — she handles it herself, main character energy fr fr. 👑

If you wanna know more about the putting situation, go read clk_put. That's the whole lore. 💀

🔥 SEE ALSO 🔥

Kernel file ./drivers/clk/clk.c, plus a truly iconic guest list of related functions — no cap, it's giving red carpet:

💜 Quick vibe check: the auto-clk_put-on-detach thing is the WHOLE point of the devm_ prefix here. Don't sleep on it, that's the resource-managed magic and it's literally iconic. ✨

And that's the page, bestie! 🍓 This one lives in ./drivers/clk, dated October 2026 — mwah, sending you good vibes and leak-free drivers, devm_clk_hw_get_clk(9) out. 🧚💖🌸

📦 where this page comes from