Always-On Logic translates low-power intent into release-grade evidence. Always-on logic hosts power-management controls, retention supplies, and wake-up paths that must remain functional when switchable domains are OFF. The practical challenge is proving policy correctness under real transitions and ensuring each owner closes their layer without semantic drift.
When AON rail continuity, control-signal survivability, and leakage budget for AON islands regresses, can you identify the failing transition, policy owner, implementation evidence, and minimum regression that proves closure?
POWER INTENT FLOW — Always-On Logic
architecture intent
|
v
UPF objects (domain/supply/state/strategy)
|
v
RTL + synthesis + PD interpretation
|
v
verification + signoff evidence
|
v
release decision
Primary metric: AON rail continuity, control-signal survivability, and leakage budget for AON islandsStart with domain/state diagrams before diving into logs. These are the models to sketch in design and interview reviews.
AON ISLAND
[PMU FSM] [isolation controls] [retention controls] [wake IRQ]
| | | |
must survive when switchable domains are OFF
AON leakage is tradeoff vs control survivability.POWER DOMAIN MAP — Always-On Logic
+------------------- 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 — Always-On Logic
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 — Always-On Logic
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: AON rail continuity, control-signal survivability, and leakage budget for AON islands.
Primary artifact: AON island floorplan, control path audit, and AON leakage report.
Owners to bring into review: architecture owner, PD owner, UPF owner.
One failing transition timeline with state markers and control signals.
One report snippet proving policy intent versus implementation behavior.
OWNERSHIP MAP — Always-On Logic
artifact owner
---------------- -----------------
intent policy architecture owner
implementation PD owner
verification UPF 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.
Voltage translation and switch topology must be co-optimized with transition reliability.
CROSSING + GATING
domain crossing -> level shifter
domain enable -> staged switchesINRUSH RISK
single-stage enable █████████ high
staged enable ███ lowerLS insertion summary
switch enable schedule
inrush profile
AON control audit
Staged switch enable solved rail dip without violating wake latency budget.
Check shifter direction map
Audit switch staging
Correlate with transient IR
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/level-shifters-switches/always-on-logic: 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/level-shifters-switches/always-on-logic
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/level-shifters-switches/always-on-logic: 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/level-shifters-switches/always-on-logic
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/level-shifters-switches/always-on-logic: 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/level-shifters-switches/always-on-logic
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/level-shifters-switches/always-on-logic: 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/level-shifters-switches/always-on-logic
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/level-shifters-switches/always-on-logic: 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/level-shifters-switches/always-on-logic
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/level-shifters-switches/always-on-logic: 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/level-shifters-switches/always-on-logic
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/level-shifters-switches/always-on-logic: 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/level-shifters-switches/always-on-logic
STATE WINDOW: <from -> to>
POLICY OBJECT: <isolation / retention / shifter / switch>
OWNER: <name>
PRIMARY ARTIFACT: <report/waveform/formal result>
RELEASE DECISION: <close / bounded waiver / escalate>