Skip to content
DenseChip
Learn
PracticeCode labInterview

DenseChip

Navigate

Menu

LearnPracticeCode labInterview

Tools

All toolsSV editorCode repoResume
DenseChip

Practice, courses, and chip-design tools in one focused workspace.

LearnPracticeCode labInterviewToolsLearning paths

© 2026 DenseChip

AboutContactPrivacyTerms
Skip to lesson

Course contents

  • RTL Foundations36
  • Combinational Design25
  • Sequential Design27
  • FSM & Control27
  • Timing & Clocking39
    • STA Foundations
    • Setup, Hold and Slack
    • Skew and Variation
    • Timing Exceptions
    • Clock Gating
    • RTL for Timing
    • Clock Architecture
      • Clock-Domain Plan
      • Glitch-Free Clock Mux
      • Generated and Virtual Clocks
      • PLL Lock and Reset Coordination
      • Source-Synchronous Interfaces
      • DVFS Transition Protocol
      • Clock Constraint Examples
  • Reset & CDC34
  • Memory & Buses57
  • Advanced RTL28
  • Senior & Interview76
  • Glossary and Notation
Loading lesson

‹Clock Architecture
  1. Topics
  2. RTL Design
  3. Timing & Clocking
  4. Clock Architecture
  5. DVFS Transition Protocol

Part 5 · Timing & Clocking · Intermediate

DVFS Transition Protocol

Quiesce traffic, coordinate voltage and frequency, relock clocks, update timing mode, and resume without corrupting state.

Why this matters

Raising frequency before voltage can violate timing before the voltage reaches its new level. Changing a divider register is not DVFS: it is a protocol across workload control, power management, clock controller, reset, CDC and software.

After this lesson you can: order a DVFS transition safely, list the failure cases with their containment, and explain why every legal state needs its own timing view.

  1. Request transition and block new transactions.

  2. Drain or checkpoint outstanding work; acknowledge quiescence.

  3. For frequency increase, raise voltage before frequency; for decrease, lower frequency before voltage.

  4. Switch/divide clock through approved hardware and wait for stable/lock indication.

  5. Select the matching timing/voltage mode and release reset if the domain was reset.

  6. Resume traffic and log completion or timeout.

The order of steps 2 to 6 for a frequency increase (voltage first) and a decrease (frequency first)

Read each panel left to right. The shaded columns are the start and end of the protocol; the two middle columns are the only places where voltage or frequency moves.

  • Both directions start by quiescing and end by resuming: the change itself never happens under live traffic.

  • Going faster, the voltage step comes first, so the cells are already fast enough when the clock speeds up.

  • Going slower, the frequency step comes first, so the clock is already slow when the cells slow down.

In the worked tree, the power manager moves the core between the signed-off 400 MHz nominal scenario and a lower-frequency, lower-voltage scenario. Hardware selects operating state at runtime; STA separately signs off an analysis view for every legal state.

Failure

Containment

Quiesce timeout

Abort transition and report blocking owner

PLL does not lock

Keep domain reset/isolated; fall back to safe clock

Voltage acknowledgement missing

Do not increase frequency

Clock loss during transition

Assert containment and restart sequence

CDC peer remains active

Handshake at boundary or isolate before clock change

Warning

DVFS is not a register write to a divider. It is a distributed protocol across workload control, power management, PLL/clock controller, reset, CDC boundaries, STA modes, and software-visible status.

Check yourself Why must voltage rise before a frequency increase?

Higher frequency requires faster cell delay, which depends on sufficient voltage. Increasing frequency first can violate timing before the voltage reaches its new level.

Remember

  • Raise voltage before frequency, and lower frequency before voltage.

  • Block new work, drain, switch the clock through approved hardware, wait for lock, select the matching timing mode, then resume.

  • Handle a quiesce timeout, no lock, a missing voltage acknowledgement, clock loss and an active CDC peer with a stated containment.

Rule of thumb: never increase frequency until the voltage acknowledgement has arrived.

Keep going

  • Code lab: DVFS counter

  • Interview: run a mock interview on this topic

Related topics

  • Clock constraint examples

  • Low-power intent course

  • STA mastery course

Previous

153 / 350

Next: Clock Constraint Examples

Up next

Up nextClock Constraint Examples

Sign in to save progress

Practice this lessonReport an error

See also

  • Clock-Domain Plan
  • Glitch-Free Clock Mux
  • Generated and Virtual Clocks