Silicon PPA and closure impact

Clock tree and package coupling can dominate practical jitter outcomes.

Area drivers

• Boundary cells and guards add area

• Routing keepouts can increase utilization pressure

Power drivers

• Added margins cost power

• Jitter/noise mitigation can increase static and dynamic budgets

Timing impact

• Jitter and uncertainty consume timing

• IR/noise shifts practical timing margin

PD consequences

• Keepouts and strap topology alter congestion and CTS paths

• Package constraints affect lane routing

Verification burden

• Need aligned AMS + digital + package evidence

• Waiver discipline is mandatory

PPA — Jitter Budgeting
area/power/timing/closure-time tradeoff

PPA takeaways

• Mixed-signal fixes are multi-objective

• Signoff is cross-team, not single-report

Design option PPA snapshot

BEFORE / AFTER — Jitter Budgeting

health score
  ^
  |                     --- target
  |         o regressed
  |               o before fix
  |                    o after bounded fix
  +--------------------------------------> debug iteration

Prove signal quality, timing margin, and integration safety together.

AMS deep dive

Clock quality evidence must include jitter and sequencing, not lock status alone.

Concept diagram

CLOCKING FLOW

reference -> PLL/DLL -> distribution -> endpoint margin

Metric graph

JITTER TREND

jitter ps
  ^
  |   o baseline
  |      o stress mode
  |         o failure edge

Reports and artifacts

• jitter budget

• lock/unlock counters

• phase-noise snapshot

• STA uncertainty deltas

Mini case study

False-lock condition released reset early; endpoint logic sampled unstable clock edge patterns.

Debug branches

• Lock qualification policy

• Reset sequencing check

• Package/supply contributors

Senior review question

Ask: what boundary condition proves this topic is actually closed?

Key takeaways

• State boundary, mode, and evidence tag with every claim.

• Always align analog, digital, and physical owners before signoff decisions.

Common pitfalls

• Fixing averages while tails still fail.

• Skipping package/supply evidence in jitter or SerDes issues.

• Shipping with waivers that lack owner and expiration criteria.

Principal AMS review addendum

System timing margin is consumed by source jitter, transfer jitter, supply noise, and distribution skew; the budget must close from reference clock to endpoint sampler.

Metric: total jitter budget, deterministic/random split, downstream timing margin