sci_clk_determine_rate(9)
β¨ 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 andhwis 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:
struct sci_clk_provider(9)struct sci_clk(9)sci_clk_prepare(9)sci_clk_unprepare(9)sci_clk_is_prepared(9)sci_clk_recalc_rate(9)sci_clk_set_rate(9)sci_clk_get_parent(9)sci_clk_set_parent(9)_sci_clk_build(9)sci_clk_get(9)ti_sci_clk_probe(9)ti_sci_clk_remove(9)
π 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
- 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