clk_hw_register_kunit(9)

okay bestie, welcome to the clk_hw_register_kunit(9) page from the Kernel API Manual 💖 this one is literally about test-managed clock registration, and yes, it’s giving “clean up after yourself” energy ✨

🌸 NAME 🌸

clk_hw_register_kunit — Test managed clk_hw_register() 🎀

🎀 SYNOPSIS 🎀

int clk_hw_register_kunit (struct kunit *test , struct device *dev ,
struct clk_hw *hw );

🦋 ARGUMENTS 🦋

• test — The test context 🧪✨
• dev — device that is registering this clock 🖥️💫
• hw — link to hardware-specific clock data 🔗🕰️

💅 DESCRIPTION 💅

okay so this is just like clk_hw_register, except the clk registration is managed by the test case and is automatically unregistered after the test case concludes 🫶 no cap, the test case is the main character here and it handles the cleanup ✨

🌈 RETURN 🌈

0 on success or 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)
• of_clk_hw_register_kunit(9)
• of_clk_add_hw_provider_kunit(9)

bye bestie, mwah 💋 — source/version lives under ./drivers/clk, date is October 2026, and this iconic page is clk_hw_register_kunit(9) 🌸🫶✨