__wrpll_calc_filter_range(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… __wrpll_calc_filter_range β€” like, the NAME section but make it cute

okay so this page lives in the Kernel API Manual (section 9, for the uninitiated ✨) and it's literally all about one thing: determine PLL loop filter bandwidth. That's it. That's the whole vibe. πŸŽ€


✨ SYNOPSIS ✨

int __wrpll_calc_filter_range (unsigned long post_divr_freq );

bestie. it's one function. it takes one argument. it returns an int. we love a low-maintenance icon. πŸ‘‘


🌸 ARGUMENTS 🌸

  • post_divr_freq β€” the input clock rate after the R divider. yes. after. please don't hand it the before-divider number, i'm begging πŸ™ˆ

πŸ¦‹ DESCRIPTION πŸ¦‹

so here's the tea β˜• β€” this function picks the value you're gonna present to the PLL RANGE input signals, and it makes that call based on the input clock frequency after the post-R-divider, which is post_divr_freq.

and like, does it just make something up? no ma'am. πŸ’… this code follows the recommendations in the PLL datasheet for filter range selection. the datasheet said what it said. we're respecting the datasheet.

no cap, that's the whole description. sometimes a function just does its job and doesn't need a whole saga. 🌈


πŸ”₯ RETURN πŸ”₯

two possible endings, bestie:

  • the RANGE value to be presented to the PLL configuration inputs β€” the good ending 🫢
  • or a negative return code upon error β€” the 😭 ending. check for it. fr fr.

πŸ’œ SEE ALSO πŸ’œ

like, the whole friend group honestly. go read all of them. iykyk. 🧚


ngl this one's short and sweet, but that doesn't mean you get to skip the error check. negative return code = actual thing that can happen. πŸ’€

and that's the page!! 🌸 brought to you by ./drivers/clk/analogbits, dated October 2026, starring __wrpll_calc_filter_range(9) in the main character role. slay, periodt, go configure your PLL responsibly πŸ’–βœ¨πŸŽ€

πŸ“¦ where this page comes from