Phase-Locked-Loop

A phase-locked loop, or PLL, is a feedback circuit that generates an output clock signal locked in frequency and phase to a reference clock, built from four core blocks wired in a continuous correction loop: a phase detector, a loop filter, a voltage-controlled oscillator, and a feedback divider. Chips need this because the clock a reference crystal provides directly — typically tens of megahertz — is far slower than the multi-gigahertz clock a modern processor core actually runs on, and a PLL is the circuit that multiplies a slow, stable reference up to a fast, equally stable operating clock without drifting away from it over time. How a PLL continuously locks its output to the reference, cycle after cycle, looks like this:

Stable reference clock arrives
Typically tens of MHz, from an external crystal oscillator
Continuous phase-locking loopRuns constantly, correcting drift in real time
Phase detector compares reference to divided output
Measures the timing error between the two
Loop filter smooths the error signal
Converts a noisy comparison into a clean control voltage
VCO adjusts output frequency
Control voltage speeds up or slows down the oscillator
Feedback divider scales output back down
Lets a fast output be compared against a slow reference
↻ continuous correction
High-frequency, phase-locked clock delivered
Drives the processor core, memory interface, or I/O block

A few things are worth knowing about why a PLL has to be a closed loop, and can't just be an open-ended frequency multiplier:

A PLL's four blocks each solve one specific piece of the frequency-multiplication problem, and skipping any one of them breaks the whole mechanism, not just degrades it. The phase detector doesn't measure frequency directly — it measures the timing difference, the phase error, between the reference clock and a scaled-down copy of the output clock, producing a signal proportional to how far out of alignment the two currently are. The loop filter takes that often-noisy, pulse-like error signal and smooths it into a clean, slowly varying control voltage, because feeding a jumpy raw error signal straight into an oscillator would make the output clock jump around rather than settle. The voltage-controlled oscillator, or VCO, is the component that actually generates the high-frequency output, with its frequency directly set by that control voltage — more voltage, faster oscillation. The feedback divider closes the loop by dividing the VCO's fast output down to roughly the reference clock's frequency before it reaches the phase detector again, which is what lets a slow reference clock and a fast output clock be compared on equal footing at all.

The PLL Feedback Loop four blocks, one continuous correction loop, locked to the reference Reference crystal, ~tens of MHz Phase Detector measures timing error Loop Filter smooths error into clean control voltage VCO voltage sets output frequency Output clock Feedback Divider ÷N, scales output down the divider is what lets a multi-GHz output be compared fairly against a tens-of-MHz reference

A PLL's output doesn't snap instantly to the target frequency — it goes through a settling process called lock acquisition, and until it's locked, the output clock isn't trustworthy enough to drive real logic. When a PLL first powers up or the target frequency changes, the phase detector initially sees a large timing error, and the loop takes a number of reference cycles to converge the VCO's frequency and phase onto the target — during this acquisition period the output can overshoot, oscillate, or drift before settling into a stable lock. Chips explicitly wait for a PLL's lock-detect signal to assert before switching critical logic onto that PLL's output clock, because running real circuits off an unlocked, still-settling clock risks timing violations throughout the design.

Jitter — small, random cycle-to-cycle variations in when each clock edge actually arrives — is the practical limitation that separates a good PLL from a mediocre one, and the loop's own bandwidth setting directly trades off two different jitter sources against each other. A PLL with a wide loop bandwidth tracks the reference clock closely, which suppresses jitter accumulated inside the VCO itself but lets more of the reference clock's own noise pass through to the output. A PLL with a narrow loop bandwidth does the opposite: it filters out reference noise more effectively but lets the VCO's internal jitter accumulate more freely between corrections. Because excess jitter directly eats into a high-speed interface's timing margin — corrupting high-speed memory links or SerDes connections if it gets bad enough — PLL designers tune loop bandwidth deliberately to match whichever jitter source dominates for their specific application, rather than simply maximizing lock speed.

Modern chips rarely use just one PLL — they use several, each generating a different clock domain for a different part of the design, because a single shared clock can't simultaneously be optimal for every block on the die. A processor core might run its PLL at one multiplier of the reference for maximum compute throughput, while a memory interface uses a separate PLL tuned for the precise frequency and low jitter a high-speed memory link demands, and a peripheral I/O block uses yet another PLL at a lower, power-efficient frequency. Isolating these domains behind separate PLLs also lets a chip change one clock's frequency — for dynamic power scaling, for instance — without disturbing the others, which would be impossible if every block shared one single PLL output.

Read a phase-locked loop as a continuous correction mechanism, not a one-time frequency multiplier: its four blocks — phase detector, loop filter, VCO, feedback divider — work together every single reference cycle to hold a fast output clock locked to a slow, stable reference, and the real engineering tradeoffs — lock time, jitter, loop bandwidth, and how many separate PLLs a chip needs — all come down to how tightly and how cleanly that continuous correction is tuned.

Take phase-locked-loop further

Ask the copilot about this term, or have our engineers assess it against your process.