of_clk_add_h...ovider_kunit(9)

💅 of_clk_add_hw_provider_kunit — Kernel API Manual ✨

okay bestie, so this is a page from the Kernel API Manual, and the star of the show is of_clk_add_hw_provider_kunit — yes, that's a long name, yes, it's iconic, we move 💅

---

🎀 NAME 🎀

of_clk_add_hw_provider_kunit — the test-managed glow-up of of_clk_add_hw_provider(), fr fr 🧚

---

✨ SYNOPSIS ✨

int of_clk_add_hw_provider_kunit (struct kunit *test , struct
device_node *np , struct clk_hw *(*get)(struct of_phandle_args *clkspec,
void *data) , void *data );

like, that signature is a lot, but we're gonna break it down together, no cap 🫶

---

🌸 ARGUMENTS 🌸

• test — the test context 💖 this is the whole reason she's special, keep reading
• np — the device node pointer that's associated with the clock provider 🌈
• get — callback for decoding clk_hw ✨
• data — the context pointer handed to the get callback 🎀

---

🦋 DESCRIPTION 🦋

okay so basically she's just like of_clk_add_hw_provider, except — and this is the main character energy part — the clk_hw provider is managed by the test case, and it gets automatically unregistered after the test case concludes 👑 no manual cleanup, no messy teardown, she just handles it 🫶 periodt.

---

🔥 RETURN 🔥

0 on success, or a negative errno value on failure. that's it, that's the vibe check 💀

---

⭐ 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_hw_register_kunit(9)

literally the whole kunit clock friend group, iykyk 🌸

---

okay so that's the whole page!! sign-off time: this one comes from ./drivers/clk, dated October 2026, and she's filed under the Kernel API Manual as of_clk_add_h...ovider_kunit(9) 🎀💖 go forth and test those clock providers bestie, slay 🌈⭐