sci_clk_determine_rate(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ sci_clk_determine_rate β€” Kernel API Manual ✨

okay so bestie, we're in the sci_clk_determine_rate(9) page, and it's giving "clock math but make it firmware's problem" πŸ’… let me walk you through it πŸŽ€


🌸 NAME 🌸

sci_clk_determine_rate β€” literally determines a clock rate a clock can be set to ✨


πŸ¦‹ SYNOPSIS πŸ¦‹

int sci_clk_determine_rate (struct clk_hw *hw , struct clk_rate_request
*req );

that's the whole vibe, no cap πŸ”₯


πŸ’– ARGUMENTS πŸ’–

  • hw β€” the clock you wanna change the rate for πŸ•
  • req β€” the requested rate configuration for that clock, like it's the wishlist and hw is the genie 🧞

πŸ‘‘ DESCRIPTION πŸ‘‘

so what it actually does: it figures out a suitable clock rate and a parent for a TI SCI clock. ✨

but here's the tea β˜• β€” the parent handling is un-used, because generally the parent clock rates are not known by the kernel. instead, the firmware handles all of that internally, behind the scenes, main character energy 🫢

returns 0 on success, or a negative error value if it fails 😭


🌈 SEE ALSO 🌈

Kernel file ./drivers/clk/keystone/sci-clk.c plus the whole friend group:


πŸŽ€ quick vibe check: the parent handling being un-used isn't a bug bestie, it's just how the firmware rolls β€” don't @ me πŸ’…

k that's the page!! πŸ’œ this one lives in ./drivers/clk/keystone, October 2026 edition, and it ate fr fr β€” hope that cleared it up bestie, mwah πŸ“πŸ§šβ­

πŸ“¦ where this page comes from