sifive_prci_...el_use_hfclk(9)

📦 version 7.3.1, in nixpkgs unstable

💅 sifive_prci_hfpclkpllsel_use_hfclk(9) ✨

okay so bestie, welcome to the Kernel API Manual 🎀 — this is the page for sifive_prci_hfpclkpllsel_use_hfclk, and no, the name isn't a typo, that's just how kernel devs name things when they're feeling dramatic 💀

✨ NAME ✨

sifive_prci_hfpclkpllsel_use_hfclk — switch the HFPCLKPLL mux to output HFCLK 🦋

Like, it literally flips the mux so the output is HFCLK. That's the whole vibe check. Slay.

🌸 SYNOPSIS 🌸

void sifive_prci_hfpclkpllsel_use_hfclk (struct __prci_data *pd );

returns void, so no ✨return value✨ to obsess over, she just does her thing and leaves 💅

🧚 ARGUMENTS 🧚

  • pd — a struct __prci_data * for the PRCI that's holding the HFPCLKPLL mux reg 👑 like, this is the one and only thing you hand her, and she needs it to be the right PRCI, iykyk

🔥 DESCRIPTION 🔥

she switches the HFPCLKPLL mux over to the HFCLK input source, and then comes right back once it's complete 🫶 that's it, that's the function. short and iconic. main character energy fr fr.

⭐ CONTEXT ⭐

any context bestie 🌈 — literally any, no restrictions on where you call her from. BUT (and this is the important part, don't skip it 🙈) the caller must prevent concurrent changes to the PRCI_HFPCLKPLLSEL_OFFSET register. so like, you gotta handle that yourself, she's not doing your locking for you 💀

no cap, that's a real requirement — if two people poke PRCI_HFPCLKPLLSEL_OFFSET at the same time, that's on you, not her 😭

💖 SEE ALSO 💖

the kernel file ./drivers/clk/sifive/sifive-prci.c — that's where all her friends live 🌸 go say hi to:

and that's the page, bestie 🎀 sign-off time: this whole thing lives over in ./drivers/clk/sifive, it's dated October 2026, and you can find it filed under sifive_prci_...el_use_hfclk(9) 🦋 mwah, go flip that mux 💜

📦 where this page comes from