sunxi_ccu_s..._timing_mode(9)
π sunxi_ccu_s..._timing_mode(9) β like, the Kernel API Manual page, bestie π
okay so this is a section 9 manpage from the Kernel API Manual, and the full title is literally sunxi_ccu_s..._timing_mode(9) (yes the name is truncated with ... in the header, no that's not me being lazy, that's just how it's printed, iykyk π). it covers one (1) function and honestly she's a short queen. let's get into it β¨
πΈ NAME πΈ
sunxi_ccu_set_mmc_timing_mode β configure the MMC clock timing mode π«Ά
like that's it, that's the whole job. she configures. she's a timing mode setter. main character energy fr.
β¨ SYNOPSIS β¨
int sunxi_ccu_set_mmc_timing_mode (struct clk *clk , bool new_mode );
returns an int, takes a struct clk *clk and a bool new_mode, and the spacing around the commas is exactly like that in the original so don't come for me π
π¦ ARGUMENTS π¦
clkβ the clock to be configured π this is the one getting the glow-up.new_modeβ abool; passtruefor the new timing mode that was introduced in A83T and later π (so yes, "new" is relative, it's giving legacy-but-not-that-legacy π)
β RETURN β
0on success π slay, it worked-ENOTSUPPif the clock does not support switching modes π like it literally can't, don't ask her to
π SEE ALSO π
- Kernel file
./drivers/clk/sunxi-ng/ccu_mmc_timing.cβ go read the source, it's right there π sunxi_ccu_get_mmc_timing_mode(9)β the getter to this setter, they're a matched set fr fr π§
lowkey important: if your clock doesn't support switching modes you get -ENOTSUPP back, not a crash, not a vibe, just a polite no π
and that's the whole page!! this one lives at ./drivers/clk/sunxi-ng, it's dated October 2026, and it's filed under sunxi_ccu_s..._timing_mode(9) in the Kernel API Manual β mwah, bye bestie, go set some timing modes responsibly πβ¨π
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms