clk_hw_get_clk_kunit(9)

💖 clk_hw_get_clk_kunit(9) 💖

okay bestie, welcome to the Kernel API Manual ✨ this one lives in section 9 and it's literally the kunit-managed glow-up of clk_hw_get_clk(). let's get into it 🎀

---

✨ NAME ✨

clk_hw_get_clk_kunit — the test-managed version of clk_hw_get_clk(), no cap 🫶

---

🦋 SYNOPSIS 🦋

struct clk * clk_hw_get_clk_kunit (struct kunit *test , struct clk_hw
*hw , const char *con_id );

like, that's the whole signature. struct clk pointer coming at ya, three args, we move 💅

---

🌸 ARGUMENTS 🌸

• test — the test context, aka your kunit bestie holding the vibes together 🧚
• hw — the clk_hw that's associated with the clk being consumed 👑
• con_id — the connection ID string on the device, yep that's the one 🎀

---

🔥 DESCRIPTION 🔥

so it's just like clk_hw_get_clk, except — and this is the iconic part — the clk is managed by the test case, and it gets automatically put with clk_put after the test case concludes. like, you don't even have to clean up after yourself, the framework does it for you. main character energy fr fr ⭐

---

💜 RETURN 💜

a new clk consumer 💖 … or ERR_PTR on failure 😭 (iykyk, always check for the error pointer, don't just vibe-check it and move on)

---

🌈 SEE ALSO 🌈

kernel file: ./drivers/clk/clk_kunit_helpers.c 🗂️

the whole friend group:

• clk_prepare_enable_kunit(9)
• clk_get_kunit(9)
• of_clk_get_kunit(9)
• clk_hw_get_clk_prepared_enabled_kunit(9)
• clk_hw_register_kunit(9)
• of_clk_hw_register_kunit(9)
• of_clk_add_hw_provider_kunit(9)

---

ok that's the page!! now go write some tests and let the cleanup handle itself, you deserve it 💅✨

---

and that's a wrap, babe 🫶 this one's from ./drivers/clk, dated October 2026, and it's clk_hw_get_clk_kunit(9) all day 💖 slay 🎀