dfll_calculate_rate_request(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… dfll_calculate_rate_request(9) β€” the dfll_calculate_rate_request kernel API manual, bestie edition

okay so picture this: you're deep in the Linux kernel, specifically the dfll_calculate_rate_request(9) page from the Kernel API Manual, and you need DFLL parameters for a rate. that's the whole vibe. let's get into it 🫢


✨ NAME ✨

dfll_calculate_rate_request β€” literally calculates DFLL parameters for a given rate. that's it, that's the function πŸ’–


🌸 SYNOPSIS 🌸

int dfll_calculate_rate_request (struct tegra_dfll *td , struct
dfll_rate_req *req , unsigned long rate );

πŸŽ€ ARGUMENTS πŸŽ€

  • td β€” your DFLL instance, the main character of this whole situation πŸ‘‘
  • req β€” the DFLL-rate-request structure bestie, this is what we're filling in
  • rate β€” the desired DFLL rate, aka the goal, the dream, the target ✨

πŸ¦‹ DESCRIPTION πŸ¦‹

so what this does is it populates the DFLL-rate-request record req's fields β€” specifically the scale_bits and mult_bits fields β€” based on the target input rate. no cap, that's the whole job.

returns 0 upon success πŸ’š … or -EINVAL if the requested rate in req->rate is too high or too low for the DFLL to generate 😭 like it's giving "girl that rate is not happening" energy. too much, too little, either way, invalid.

fr fr: if you're getting -EINVAL back, check that req->rate is actually in range for the DFLL before you start blaming the driver πŸ™ˆ

🌈 SEE ALSO 🌈

the whole friend group, in order, and yes we're listing every single one because we don't do "etc." around here πŸ’…

Kernel file ./drivers/clk/tegra/clk-dfll.c, plus:


okay that's the page!! mwah πŸ’‹ this came out of ./drivers/clk/tegra with a date of October 2026, and the page itself is dfll_calculate_rate_request(9) β€” go forth and calculate those rate requests, bestie, you're gonna slay πŸ§šβ€β™€οΈβ­

πŸ“¦ where this page comes from