sifive_prci_..._dvfscorepll(9)
π sifive_prci_..._dvfscorepll(9) π
okay bestie, this page is from the Kernel API Manual and it's giving one tiny mux switch, one very specific job β¨ honestly? iconic.
πΈ NAME πΈ
sifive_prci_corepllsel_use_dvfscorepll β switch the COREPLL mux to output DVFS_COREPLL π
β¨ SYNOPSIS β¨
void sifive_prci_corepllsel_use_dvfscorepll (struct __prci_data *pd );
π ARGUMENTS π
pdβ astruct __prci_data *for the PRCI containing the COREPLL mux reg. like, hand over the PRCI that has the mux reg, bestie π«Ά
π¦ DESCRIPTION π¦
So this function switches the COREPLL mux to the DVFSCOREPLL output clock, then returns once it's complete. no extra drama, no lingering β it's done and it's out β¨
π CONTEXT π
Any context is fine, fr fr. But the caller must prevent concurrent changes to the PRCI_COREPLLSEL_OFFSET register β that part is not a vibe, it's a requirement π
π₯ SEE ALSO π₯
Kernel file: ./drivers/clk/sifive/sifive-prci.c
__prci_readl(9)__prci_wrpll_unpack(9)__prci_wrpll_pack(9)__prci_wrpll_read_cfg0(9)__prci_wrpll_write_cfg0(9)__prci_wrpll_write_cfg1(9)sifive_prci_coreclksel_use_hfclk(9)sifive_prci_coreclksel_use_corepll(9)sifive_prci_coreclksel_use_final_corepll(9)sifive_prci_corepllsel_use_corepll(9)sifive_prci_hfpclkpllsel_use_hfclk(9)sifive_prci_hfpclkpllsel_use_hfpclkpll(9)__prci_register_clocks(9)sifive_prci_probe(9)
π«Ά that's the whole page, bestie. source/version:./drivers/clk/sifive; date: October 2026; page:sifive_prci_..._dvfscorepll(9)β slay and bye π
π¦ 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