of_clk_hw_register_kunit(9)

💅 of_clk_hw_register_kunit(9) 💅

okay so bestie, welcome to the Kernel API Manual — this one's a lil helper from ./drivers/clk and it's genuinely so useful, let me tell you everything 🫶

---

✨ NAME ✨

of_clk_hw_register_kunit — the test-managed glow-up of of_clk_hw_register(). literally the same thing but the test case holds the aux cord 🎀

---

🌸 SYNOPSIS 🌸

int of_clk_hw_register_kunit (struct kunit *test , struct device_node
*node , struct clk_hw *hw );

---

🦋 ARGUMENTS 🦋

• test — the test context, aka where all the kunit magic lives ✨
• node — the device_node of the device that's registering this clock, iykyk 🌈
• hw — the link to the hardware-specific clock data, the main character of the operation 👑

---

💖 DESCRIPTION 💖

So it's just like of_clk_hw_register, except — and this is the iconic part — the clk registration is managed by the test case and it gets automatically unregistered after the test case concludes. no cap, no manual cleanup, no tears 😭🫶

it's giving "register it and forget it" energy, and honestly? obsessed 💅

---

⭐ RETURN ⭐

• 0 on success 🎉
• a negative errno value on failure 💀

---

🧚 SEE ALSO 🧚

• Kernel file ./drivers/clk/clk_kunit_helpers.c
• clk_prepare_enable_kunit(9)
• clk_get_kunit(9)
• of_clk_get_kunit(9)
• clk_hw_get_clk_kunit(9)
• clk_hw_get_clk_prepared_enabled_kunit(9)
• clk_hw_register_kunit(9)
• of_clk_add_hw_provider_kunit(9)

---

and that's the whole vibe, bestie 🍓 this lil page lives in ./drivers/clk, dated October 2026, and it's brought to you by of_clk_hw_register_kunit(9) — go forth, register those clocks, and let the test framework clean up after you 💜🧚‍♀️🎀