# Power aware verification

**URL:** <https://verificationacademy.com/forums/t/power-aware-verification/50025>\
**Category:** UVM\
**Tags:** Low-Power--UPF\
**Created:** [April 11, 2025, 11:22am UTC](https://verificationacademy.com/forums/t/power-aware-verification/50025 "2025-04-11T11:22:57Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![zoro](https://verificationacademy.com/forums/letter_avatar_proxy/v4/letter/z/ecc23a/32.png) [@zoro](https://verificationacademy.com/forums/u/zoro)\
**Post date:** [April 11, 2025, 11:22am UTC](https://verificationacademy.com/forums/t/power-aware-verification/50025/1 "2025-04-11T11:22:57Z")

</div>

In low power verification, we typically deal with power-up and power-down sequences for power-gated IPs.

During the power-up sequence, the order I’ve often seen is:

Power ON → Reset → State Restore → Isolation Enable De-asserted → Clock Enable

However, I have a concern:  
Without the clock being active, how are the restored values (from state retention logic) updated inside the IP?

Is this power-up sequence correct, or should the clock be enabled earlier in order to properly latch the restored values?

---

<div class="post-metadata">

**Author:** ![dave\_59](https://verificationacademy.com/forums/user_avatar/verificationacademy.com/dave_59/32/4499_2.png) [@dave\_59](https://verificationacademy.com/forums/u/dave_59)\
**Post date:** [April 14, 2025, 4:02pm UTC](https://verificationacademy.com/forums/t/power-aware-verification/50025/2 "2025-04-14T16:02:47Z")

</div>

It depends on how the State restore gets implemented. Many times it is done asynchronously.
