Low-Power Design with UPF/CPF is the methodology for specifying, implementing, and verifying power management features in SoC designs using standardized power intent formats — Unified Power Format (UPF, IEEE 1801) or Common Power Format (CPF, Cadence) — that describe voltage domains, power switches, isolation, level shifting, and retention strategies in a machine-readable format driving the entire EDA tool flow.
Power management in modern SoCs is extraordinarily complex: a mobile processor may have 20+ independently controlled power domains, support 8+ voltage/frequency operating points, and implement multiple sleep states. Capturing this complexity requires a formal power intent specification.
UPF Power Concepts:
| Concept | UPF Command | Purpose |
|---|---|---|
| Supply network | create_supply_net, create_supply_set | Define power/ground rails |
| Power domain | create_power_domain | Group cells sharing supply |
| Power switch | create_power_switch | Header/footer MTCMOS gates |
| Isolation | set_isolation | Clamp outputs of powered-off domains |
| Level shifting | set_level_shifter | Convert between voltage levels |
| Retention | set_retention | Preserve state during power-off |
| Power state | add_power_state | Define legal voltage combinations |
Implementation Flow: UPF drives every step: synthesis reads UPF to insert isolation cells, level shifters, and retention registers; floorplanning creates domain regions and places power switches; place-and-route respects domain boundaries and inserts special cells at crossings; signoff performs UPF-aware DRC, LVS, and power verification.
Power Switch Implementation: MTCMOS (Multi-Threshold CMOS) header or footer switches gate the supply to switchable domains. Critical parameters: on-resistance (determines IR drop in active mode — keep <5% VDD drop), rush current (inrush when domain powers on — can cause supply droop affecting always-on domains), leakage (switch transistor leakage is the floor of domain power savings), and switch staging (turning on switches gradually over multiple clock cycles to limit rush current).
Retention Strategy: When powering off a domain, state in flip-flops is lost unless retention flip-flops (balloon latches that maintain state on a separate always-on supply) are used. Trade-offs: retention FFs are 2-3x the area of standard FFs; save/restore operations add latency (1-10 cycles); not all state needs retention (caches can be invalidated, register files can be re-loaded). Selective retention — retaining only critical architectural state while re-initializing everything else — minimizes area overhead.
Verification Challenges: Power-aware simulation must model: supply states (on/off/transitioning), corruption of powered-off signals, isolation cell behavior, level shifter delays, retention save/restore, and illegal power state transitions. UPF-aware simulators (Synopsys VCS, Siemens Questa) corrupt signals from powered-off domains to detect missing isolation.
Low-power design with UPF has transformed power management from ad-hoc implementation to a rigorous engineering discipline — the power intent specification serves as the single source of truth that coordinates synthesis, implementation, and verification tools, ensuring the complex power architecture functions correctly across all operating modes.
Explore 500+ Semiconductor & AI Topics
From EUV lithography to CUDA optimization — search the full knowledge base or chat with our AI assistant.