exynos_arm64...ister_cmu_pm(9)

💖 NAME 💖

exynos_arm64_register_cmu_pm — bestie, this is the one that registers an Exynos CMU domain with PM support. Yes, PM as in power management. She's the glow-up version, okurrr ✨

Oh and hi, welcome, you're reading a page from the Kernel API Manual, section 9 — the header up top says exynos_arm64...ister_cmu_pm(9), which is just the long name being dramatic and refusing to fit. We stan a mysterious abbreviation 🎀

---

✨ SYNOPSIS ✨

int exynos_arm64_register_cmu_pm (struct platform_device *pdev , bool
init_clk_regs );

Literally just two arguments. You got this, iykyk 💅

---

🦋 ARGUMENTS 🦋

• pdev — the platform device object 🫶 like, the actual device you're doing this for
• init_clk_regs — if it's true, she initializes the CMU registers. That's the whole vibe check right there 🌸

---

👑 DESCRIPTION 👑

So basically: this is the version of exynos_arm64_register_cmu that comes with PM support — same energy, upgraded ✨

You should call it from the probe function of your platform driver. That's the assignment, no cap 📌

---

⭐ RETURN ⭐

• 0 on success 🎉 slay, you did it
• a negative error code on error 😭 it's giving "something went wrong", read the code and cope

---

🌈 SEE ALSO 🌈

• the Kernel file, ./drivers/clk/samsung/clk-exynos-arm64.c — go read the source bestie, it's all there 💖
• exynos_arm64_init_clocks(9)
• exynos_arm64_enable_bus_clk(9)
• exynos_arm64_register_cmu(9) — the non-PM sibling, the icon, the blueprint 👑

---

ngl, if you're calling this outside a probe function, please re-read the description. I'm not mad, I'm just disappointed 🥺

---

okay that's the whole page, go be a main character in ./drivers/clk/samsung 🧚‍♀️ this came out of the Kernel API Manual, dated October 2026, and the footer says ./drivers/clk/samsung too, so like… the source and the date said hi, and so did exynos_arm64...ister_cmu_pm(9) 💜 periodt.