dfll_lock(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… dfll_lock β€” the kernel API manual, but make it make sense

okay so bestie, welcome to dfll_lock(9) β€” yes that's the page name, and yes it lives in the Kernel API Manual because we're fancy like that ✨


🌸 NAME

dfll_lock β€” switch from open-loop to closed-loop mode πŸŽ€


⭐ SYNOPSIS

int dfll_lock (struct tegra_dfll *td );

🫢 ARGUMENTS

  • td β€” the DFLL instance, aka the main character of this whole operation πŸ’–

πŸ”₯ DESCRIPTION

So here's the vibe: you're switching this thing from OPEN_LOOP state to CLOSED_LOOP state. Glow-up complete, no cap πŸ’…

It returns 0 upon success β€” slay.

It returns -EINVAL if the DFLL's target rate hasn't been set yet β€” like bestie, you can't close the loop if you don't even know where you're going 😭

Or it returns -EPERM if the DFLL is not currently in open-loop mode β€” you literally cannot switch from open-loop if you're not in open-loop, that's just not the vibe πŸ™ˆ

ngl, those are the only three outcomes. 0, -EINVAL, -EPERM. Memorize them, they're iconic πŸ‘‘

🌈 SEE ALSO

the whole friend group, fr fr 🧚:


and that's the whole page bestie, go close some loops πŸ’œ

~ sourced straight from ./drivers/clk/tegra, dated October 2026, and yes this page is literally dfll_lock(9) β€” told you it was iconic βœ¨πŸŽ€πŸ¦‹

πŸ“¦ where this page comes from