CLK FRAMEWORK FLAGS(9)

🌸 clk framework flags(9) 🌸

okay bestie, so this is a page from the Kernel API Manual and it's literally just the flag collection for the clock framework — like the group chat of struct clk and everyone's pinned messages. 🎀

---

✨ NAME ✨

clk framework flags — the shared flag vocabulary used all over the common struct clk 💅

---

🦋 DESCRIPTION 🦋

These are the flags that get used across common struct clk. And listen — these flags should only affect the top-level framework. That's the rule, no cap. 🫶

If you've got custom flags for dealing with hardware specifics? Those belong in struct clk_foo, bestie. Not here. Different lane, different vibe. ✨

So here's the whole lineup, and honestly? Every single one of them is kind of iconic:

• CLK_SET_RATE_GATE — must be gated across rate change 🔒
• CLK_SET_PARENT_GATE — must be gated across re-parent
• CLK_SET_RATE_PARENT — propagate rate change up one level ⬆️
• CLK_IGNORE_UNUSED — do not gate even if unused 🙈
• CLK_GET_RATE_NOCACHE — do not use the cached clk rate
• CLK_SET_RATE_NO_REPARENT — don't re-parent on rate change 🚫
• CLK_GET_ACCURACY_NOCACHE — do not use the cached clk accuracy
• CLK_RECALC_NEW_RATES — recalc rates after notifications 🔁
• CLK_SET_RATE_UNGATE — clock needs to run to set rate 🏃‍♀️
• CLK_IS_CRITICAL — do not gate, ever 💀 (like, ever ever)
• CLK_OPS_PARENT_ENABLE — parents need enable during gate/ungate, set rate and re-parent 👑
• CLK_DUTY_CYCLE_PARENT — duty cycle call may be forwarded to the parent clock 📨

periodt. those are all of them, and yes, CLK_IS_CRITICAL really does mean do not gate, ever. don't test it, bestie. 🔥

---

🌈 SEE ALSO 🌈

Kernel file ./include/linux/clk-provider.h — and honestly the whole extended friend group:

• struct clk_rate_request(9)
• struct clk_duty(9)
• struct clk_spread_spectrum(9)
• struct clk_ops(9)
• struct clk_parent_data(9)
• struct clk_init_data(9)
• struct clk_hw(9)
• struct clk_fixed_rate(9)
• clk_hw_register_fixed_rate(9)
• devm_clk_hw_register_fixed_rate(9)
• devm_clk_hw_register_fixed_rate_parent_data(9)
• clk_hw_register_fixed_rate_parent_hw(9)
• clk_hw_register_fixed_rate_parent_data(9)
• clk_hw_register_fixed_rate_with_accuracy(9)
• clk_hw_register_fixed_rate_with_accuracy_parent_hw(9)
• clk_hw_register_fixed_rate_with_accuracy_parent_data(9)
• clk_hw_register_fixed_rate_parent_accuracy(9)
• struct clk_gate(9)
• clk_hw_register_gate(9)
• clk_hw_register_gate_parent_hw(9)
• clk_hw_register_gate_parent_data(9)
• devm_clk_hw_register_gate(9)
• devm_clk_hw_register_gate_parent_hw(9)
• devm_clk_hw_register_gate_parent_data(9)
• struct clk_divider(9)
• clk_register_divider(9)
• clk_hw_register_divider(9)
• clk_hw_register_divider_parent_hw(9)
• clk_hw_register_divider_parent_data(9)
• clk_hw_register_divider_table(9)
• clk_hw_register_divider_table_parent_hw(9)
• clk_hw_register_divider_table_parent_data(9)
• devm_clk_hw_register_divider(9)
• devm_clk_hw_register_divider_parent_hw(9)
• devm_clk_hw_register_divider_parent_data(9)
• devm_clk_hw_register_divider_table(9)
• struct clk_mux(9)
• struct clk_fixed_factor(9)
• devm_clk_hw_register_fixed_factor_parent_hw(9)
• struct clk_fractional_divider(9)
• struct clk_multiplier(9)
• clk_hw_get_dev(9)
• clk_hw_get_of_node(9)

---

💖 that's the whole page, bestie 💖

this one lives in ./include/linux, it's from October 2026, and it's part of the Kernel API Manual — go read it before you touch a clock, ily, bye 🧚‍♀️✨