Low Power Verification · All levels

Level-Shifter Direction, Threshold, and Enable Checks: Review Checklist

Review Checklist for Level-Shifter Direction, Threshold, and Enable Checks.

Review checklist

Review Checklist for Level-Shifter Direction, Threshold, and Enable Checks is anchored on Illegal voltage-direction crossing count and level-shifter control-sequence violations across static signoff and dynamic low-power regressions.. Convert observations into mechanism-backed and owner-bound actions.

  • Scope, mode, seed, and metadata are explicit.

  • Mechanism classification is evidence-backed.

  • Ownership and rollback boundary are documented.

  • Validation matrix includes deterministic replay checks.

  • Owners signed: library and circuit integration owner, low-power architecture owner, implementation/PD owner, power intent verification owner, DFT and test integration owner.

Low-power verification deep dive

Boundary correctness depends on timing: isolate and shift at the right crossings and right phases.

Concept diagram

diagram
BOUNDARY SAFETY VIEW

domain crossing -> level-shift requirement -> isolation control -> OFF/ON transition behavior

Metric graph

diagram
BOUNDARY BUG CLASSES

missing isolation      █████
late isolation         ████
LS misdirection        ███

Metrics and artifacts to collect

  • cross-domain boundary inventory

  • clamp-value correctness report

  • LS direction and threshold checks

  • missing or redundant boundary action list

Mini case study

A boundary bug escaped unit tests until domain-off traffic stress revealed late isolation enable timing.

Debug branches

  • Map each crossing to expected LS and isolation behavior.

  • Verify enable timing against collapse and restore edges.

  • Check clamp safety for protocol-facing signals.

Senior review question

Ask: what exact low-power transition boundary failed first, and which artifact proves the closure claim reproducibly?

Key takeaways

  • Tie each LPV claim to a concrete transition boundary and one proving artifact.

  • Prefer minimal reversible fixes with explicit owner and rollback criteria.

Common pitfalls

  • Treating power-aware failures as random before boundary classification.

  • Waiving X-prop failures before proving impact and root cause.

  • Declaring closure without deterministic replay across key modes.

Principal LPV review addendum

Level-Shifter Direction, Threshold, and Enable Checks should be reviewed as a transition integrity system, not just isolated checks.

Use Illegal voltage-direction crossing count and level-shifter control-sequence violations across static signoff and dynamic low-power regressions. as alarm and Cross-domain voltage-compatibility report with shifter direction rules, enable-timing waveforms, and approved exception ledger. as proof.

Isolation and level-shifting quality is measured at crossing correctness, clamp safety, and timing of control intent. Closure quality comes from reproducible evidence and explicit owners.