sunxi_ccu_g..._timing_mode(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– sunxi_ccu_get_mmc_timing_mode β€” the Kernel API Manual page, but make it make sense πŸ’–

okay so bestie, welcome to the Kernel API Manual ✨ this little cutie lives in the sunxi_ccu_g..._timing_mode(9) section and honestly? she's short, she's sweet, she's giving "one function, zero drama" πŸŽ€


✨ NAME ✨

sunxi_ccu_get_mmc_timing_mode β€” get the current MMC clock timing mode πŸ•πŸ’…

like... you're asking a clock "hey girl, which timing mode are you in rn?" and she tells you. iconic behavior tbh.


🌸 SYNOPSIS 🌸

int sunxi_ccu_get_mmc_timing_mode (struct clk *clk );

one function, one arg, returns an int. no cap, that's the whole vibe πŸ¦‹


🫢 ARGUMENTS 🫢

  • clk β€” the clock you wanna query πŸ‘‘ literally just hand her the clock and she'll spill the tea about her timing mode.

⭐ RETURN ⭐

okay so here's the vibe check on what you get back:

  • 0 β€” the clock is in old timing mode πŸ•°οΈ
  • > 0 β€” the clock is in new timing mode ✨ (bigger than zero, so yes, she upgraded)
  • -ENOTSUPP β€” the clock doesn't support this function at all πŸ™ˆ like sorry bestie, wrong number, this clock can't help you
lowkey important: -ENOTSUPP isn't a soft fail, it's a "this clock literally does not do this" so don't go expecting 0 or >0 to save you 😭

πŸ¦‹ SEE ALSO πŸ¦‹

  • Kernel file ./drivers/clk/sunxi-ng/ccu_mmc_timing.c πŸ“ β€” the source, go read it if you're feeling main character energy
  • sunxi_ccu_set_mmc_timing_mode(9) β€” her sister function, the one that actually sets the mode. iykyk πŸ’œ

k that's the whole page, fr fr πŸ’€ short but she ate. go forth and query your clocks responsibly πŸ§šβ€β™€οΈπŸŒˆ

sign-off szn: this lil masterpiece comes from ./drivers/clk/sunxi-ng, dated October 2026 β€” periodt, we're done here πŸ’…πŸŽ€

πŸ“¦ where this page comes from