lmk04832_check_vco_ranges(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ lmk04832_check_vco_ranges πŸ’…

okay so bestie, welcome to the Kernel API Manual β€” this one's a little function with main character energy, and it lives in lmk04832_check_vco_ranges(9) πŸŽ€


πŸ’– NAME

lmk04832_check_vco_ranges β€” literally checks whether the VCO frequency you're asking for actually fits inside the VCO ranges 🌸


πŸ¦‹ SYNOPSIS

int lmk04832_check_vco_ranges (struct lmk04832 *lmk , unsigned long rate );

πŸ“ ARGUMENTS

  • lmk β€” your reference to the lmk device, like your plus-one at the function call 🫢
  • rate β€” the desired output rate for the VCO, i.e. the vibe you're going for ✨

πŸ‘‘ DESCRIPTION

okay so the LMK04832 has 2 internal VCO, and each one has its own independent operating ranges β€” no cap, they don't share πŸ’€

so what you do is: use the device_info structure to figure out which VCO to use based on rate. that's the whole assignment. iconic, honestly 🌈


πŸ”₯ RETURN

returns the VCO_MUX value β€” or a negative errno if things did not, in fact, slay 😭


🧚 SEE ALSO


and that's the page, bestie πŸ’œ it's giving ./drivers/clk, version October 2026, straight from the Kernel API Manual β€” go forth and check those ranges, periodt πŸŽ€βœ¨πŸ¦‹

πŸ“¦ where this page comes from