Power State Verification translates low-power intent into release-grade evidence. Verification environments must drive realistic power-mode transitions and check protocol behavior across ON/OFF/RETENTION states. The practical challenge is proving policy correctness under real transitions and ensuring each owner closes their layer without semantic drift.
When state transition coverage, illegal-transition hits, and reset-after-wakeup pass rate regresses, can you identify the failing transition, policy owner, implementation evidence, and minimum regression that proves closure?
POWER INTENT FLOW — Power State Verification
architecture intent
|
v
UPF objects (domain/supply/state/strategy)
|
v
RTL + synthesis + PD interpretation
|
v
verification + signoff evidence
|
v
release decision
Primary metric: state transition coverage, illegal-transition hits, and reset-after-wakeup pass rateStart with domain/state diagrams before diving into logs. These are the models to sketch in design and interview reviews.
STATE TEST MATRIX
from to RUN RETENTION OFF
RUN - test test
RETENTION test - test
OFF test test -
Cover legal transitions and illegal rejection behavior.POWER DOMAIN MAP — Power State Verification
+------------------- always_on -------------------+
| PMU / control / retention rail |
+---------+----------------------------+----------+
| |
+--------v---------+ +--------v---------+
| domain_A | | domain_B |
| switchable |<------->| switchable |
| iso/ret controls | crossings require policy |
+------------------+ +------------------+
Domain boundaries are policy boundaries, not drawing boundaries.STATE TRANSITIONS — Power State Verification
ON --save--> RETENTION --off--> OFF
^ | |
| +----restore<--------+
+--------------------power_up--------+
Guard checks:
- isolation asserted before OFF
- restore before functional traffic
- reset policy consistent with retained stateLP OWNERSHIP LAYERS — Power State Verification
layer owns typical failure
------------------ --------------------------- --------------------------
architecture domain strategy infeasible power states
UPF intent policy objects + bindings wrong/missing policy
implementation LP cell insertion/routing illegal physical behavior
verification transition scenarios uncovered LP bug
signoff governance waiver + release decisions late escape to siliconPrimary metric: state transition coverage, illegal-transition hits, and reset-after-wakeup pass rate.
Primary artifact: power-state coverage report, transition assertions, and scenario matrix.
Owners to bring into review: verification owner, UPF owner, PMU owner.
One failing transition timeline with state markers and control signals.
One report snippet proving policy intent versus implementation behavior.
OWNERSHIP MAP — Power State Verification
artifact owner
---------------- -----------------
intent policy verification owner
implementation UPF owner
verification PMU owner
Escapes happen when ownership is implicit.Each topic is taught across mechanism, inputs/outputs, reports, debug, worked example, pitfalls, interview, checklist, theory, design space, expanded case study, walkthrough, comparison matrix, software view, and silicon impact.
Always name the transition context for every low-power metric.
Bind each policy decision to a specific owner and artifact.
Re-run LP simulation, formal, and implementation checks after changes.
Treating static pass reports as transition closure.
Fixing symptoms without checking policy binding and sequence order.
Shipping with ambiguous ownership on open LP violations.
Transition-centric verification closes LP risk better than active-mode-centric regressions.
VERIFY LOOP
transition matrix -> simulation + formal -> coverage -> closureCOVERAGE CLOSURE
state transitions covered ███████████
isolation activation █████████
retention restore paths ████████state coverage
formal LP properties
isolation coverage
LP bug triage dashboard
Coverage looked high, but one untested OFF->RUN transition hid a restore race.
Rank by transition criticality
Correlate PMU logs with failures
Escalate unproven properties
Ask: what transition evidence proves this topic is closed, and which owner signs it?
State transition context must accompany every low-power metric claim.
Intent changes require simulation, formal, and implementation re-validation.
Comparing results from mismatched UPF revisions.
Assuming static checks replace transition validation.
Shipping with aged waivers and unclear ownership.
Use this pack to rehearse low-power closure on low-power/low-power-verification/power-state-verification: transition framing, policy ownership, implementation evidence, and release confidence.
State transition explicitly named with legal source/target states.
Crossing and domain ownership are mapped and agreed.
Policy controls are traced to always-on source logic.
Waveform bookmarks align controls with state timestamps.
Which policy object is first to deviate from intent?
Which owner can apply the smallest reversible fix?
What regression matrix proves no collateral damage?
Which waiver conditions would still block release?
LP EVIDENCE CAPSULE 1
PATH: low-power/low-power-verification/power-state-verification
STATE WINDOW: <from -> to>
POLICY OBJECT: <isolation / retention / shifter / switch>
OWNER: <name>
PRIMARY ARTIFACT: <report/waveform/formal result>
RELEASE DECISION: <close / bounded waiver / escalate>Use this pack to rehearse low-power closure on low-power/low-power-verification/power-state-verification: transition framing, policy ownership, implementation evidence, and release confidence.
State transition explicitly named with legal source/target states.
Crossing and domain ownership are mapped and agreed.
Policy controls are traced to always-on source logic.
Waveform bookmarks align controls with state timestamps.
Which policy object is first to deviate from intent?
Which owner can apply the smallest reversible fix?
What regression matrix proves no collateral damage?
Which waiver conditions would still block release?
LP EVIDENCE CAPSULE 2
PATH: low-power/low-power-verification/power-state-verification
STATE WINDOW: <from -> to>
POLICY OBJECT: <isolation / retention / shifter / switch>
OWNER: <name>
PRIMARY ARTIFACT: <report/waveform/formal result>
RELEASE DECISION: <close / bounded waiver / escalate>Use this pack to rehearse low-power closure on low-power/low-power-verification/power-state-verification: transition framing, policy ownership, implementation evidence, and release confidence.
State transition explicitly named with legal source/target states.
Crossing and domain ownership are mapped and agreed.
Policy controls are traced to always-on source logic.
Waveform bookmarks align controls with state timestamps.
Which policy object is first to deviate from intent?
Which owner can apply the smallest reversible fix?
What regression matrix proves no collateral damage?
Which waiver conditions would still block release?
LP EVIDENCE CAPSULE 3
PATH: low-power/low-power-verification/power-state-verification
STATE WINDOW: <from -> to>
POLICY OBJECT: <isolation / retention / shifter / switch>
OWNER: <name>
PRIMARY ARTIFACT: <report/waveform/formal result>
RELEASE DECISION: <close / bounded waiver / escalate>Use this pack to rehearse low-power closure on low-power/low-power-verification/power-state-verification: transition framing, policy ownership, implementation evidence, and release confidence.
State transition explicitly named with legal source/target states.
Crossing and domain ownership are mapped and agreed.
Policy controls are traced to always-on source logic.
Waveform bookmarks align controls with state timestamps.
Which policy object is first to deviate from intent?
Which owner can apply the smallest reversible fix?
What regression matrix proves no collateral damage?
Which waiver conditions would still block release?
LP EVIDENCE CAPSULE 4
PATH: low-power/low-power-verification/power-state-verification
STATE WINDOW: <from -> to>
POLICY OBJECT: <isolation / retention / shifter / switch>
OWNER: <name>
PRIMARY ARTIFACT: <report/waveform/formal result>
RELEASE DECISION: <close / bounded waiver / escalate>Use this pack to rehearse low-power closure on low-power/low-power-verification/power-state-verification: transition framing, policy ownership, implementation evidence, and release confidence.
State transition explicitly named with legal source/target states.
Crossing and domain ownership are mapped and agreed.
Policy controls are traced to always-on source logic.
Waveform bookmarks align controls with state timestamps.
Which policy object is first to deviate from intent?
Which owner can apply the smallest reversible fix?
What regression matrix proves no collateral damage?
Which waiver conditions would still block release?
LP EVIDENCE CAPSULE 5
PATH: low-power/low-power-verification/power-state-verification
STATE WINDOW: <from -> to>
POLICY OBJECT: <isolation / retention / shifter / switch>
OWNER: <name>
PRIMARY ARTIFACT: <report/waveform/formal result>
RELEASE DECISION: <close / bounded waiver / escalate>Use this pack to rehearse low-power closure on low-power/low-power-verification/power-state-verification: transition framing, policy ownership, implementation evidence, and release confidence.
State transition explicitly named with legal source/target states.
Crossing and domain ownership are mapped and agreed.
Policy controls are traced to always-on source logic.
Waveform bookmarks align controls with state timestamps.
Which policy object is first to deviate from intent?
Which owner can apply the smallest reversible fix?
What regression matrix proves no collateral damage?
Which waiver conditions would still block release?
LP EVIDENCE CAPSULE 6
PATH: low-power/low-power-verification/power-state-verification
STATE WINDOW: <from -> to>
POLICY OBJECT: <isolation / retention / shifter / switch>
OWNER: <name>
PRIMARY ARTIFACT: <report/waveform/formal result>
RELEASE DECISION: <close / bounded waiver / escalate>Use this pack to rehearse low-power closure on low-power/low-power-verification/power-state-verification: transition framing, policy ownership, implementation evidence, and release confidence.
State transition explicitly named with legal source/target states.
Crossing and domain ownership are mapped and agreed.
Policy controls are traced to always-on source logic.
Waveform bookmarks align controls with state timestamps.
Which policy object is first to deviate from intent?
Which owner can apply the smallest reversible fix?
What regression matrix proves no collateral damage?
Which waiver conditions would still block release?
LP EVIDENCE CAPSULE 7
PATH: low-power/low-power-verification/power-state-verification
STATE WINDOW: <from -> to>
POLICY OBJECT: <isolation / retention / shifter / switch>
OWNER: <name>
PRIMARY ARTIFACT: <report/waveform/formal result>
RELEASE DECISION: <close / bounded waiver / escalate>