zynqmp_clk_get_max_divisor(9)

💅 zynqmp_clk_get_max_divisor(9) — like, the Kernel API Manual obviously

okay bestie, buckle up, because we're diving into zynqmp_clk_get_max_divisor 🦋 — yes it's a whole mouthful, no I will not be shortening it, it's giving main character energy and honestly the name ate.

---

✨ NAME ✨

zynqmp_clk_get_max_divisor — literally just: get the maximum supported divisor from firmware. that's the whole vibe. 💫

---

🎀 SYNOPSIS 🎀

u32 zynqmp_clk_get_max_divisor (u32 clk_id , u32 type );

so it takes two u32s and hands you back a u32, periodt. 🫶

---

🌸 ARGUMENTS 🌸

okay so here's what you're actually feeding it:

• clk_id — the id of the clock, like its little name tag at the party 💌
• type — the divider type. which kind of divider we're talking about, bestie ✨

---

⭐ RETURN ⭐

here's the tea ☕:

• if the query data is successful 👑 → you get the maximum divisor of a clock
• if the query data is not a success 😭 → you get U16_MAX

so yeah, heads up: U16_MAX is the "welp, that didn't work" answer. don't @ me, that's just what it does 💀

---

🦋 SEE ALSO 🦋

go look at these, iykyk:

• Kernel file ./drivers/clk/zynqmp/divider.c
• struct zynqmp_clk_divider(9)
• zynqmp_clk_divider_recalc_rate(9)
• zynqmp_clk_divider_determine_rate(9)
• zynqmp_clk_divider_set_rate(9)
• zynqmp_clk_register_divider(9)

---

and that's the whole page, bestie 🧚💖

shoutout to the source at ./drivers/clk/zynqmp, dated October 2026, for the Kernel API Manual, page zynqmp_clk_get_max_divisor(9) — mwah, iconic, no notes 💅🔥