-
Notifications
You must be signed in to change notification settings - Fork 762
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[dv/rstmgr] Apply different reset kinds where applicable #16148
Comments
Please see example:
For |
Triaged for |
Triaged for |
Estimate range: 4 - 8 |
Triaged for |
Discussed with @matutem - this seems to be a coverage closure exercise that can be done after M2.5. |
I undated the issue to state it only applies to rstmgr, not clk or pwrmgr. |
In rstmgr_reset_vseq we apply random resets, which include hard (aon) and regular resets, so this issue can be declared complete. |
Most unit tests use the default apply_reset kind argument. The rstmgr unit has both AON and non-AON domain components, so the apply_reset distinction is important. One way to exercise it could be to call apply_reset with a randomized kind argument between rounds of various tests.
The text was updated successfully, but these errors were encountered: