[pwrmgr, dv] Power manager vendoring#553
Conversation
f5a7773 to
8620551
Compare
martin-velay
left a comment
There was a problem hiding this comment.
I have few comments so far but I'd prefer to not have that much commit to review as most of these changes I think are because of the OpenTitan hash update. Would it be possible to squash commits which come from the OT hash update? And if you have other automated code generated, it's best to have them in one commit, then I know I can just skip them from my review and focus only on your edits.
bc35e3d to
1ed4c06
Compare
|
@csabakiss-semify could you pull the latest |
1ed4c06 to
a9f46f5
Compare
|
I just checked against OT results when we run with Xcelium and we are getting similar results.
|
marnovandermaas
left a comment
There was a problem hiding this comment.
A few initial comments from my end.
There was a problem hiding this comment.
Did you skip number 3?
There was a problem hiding this comment.
Yes, good catch. I had that during the development but then became useless so I removed and forgot to renumber. I’ll renumber the patches to make them cleaner.
| ''' | ||
| stage: V2S | ||
| - tests: ["pwrmgr_wakeup_reset", "pwrmgr_repeat_wakeup_reset"] | ||
| + tests: ["pwrmgr_wakeup_reset"] |
There was a problem hiding this comment.
What is wrong with the repeat wakeup reset test?
There was a problem hiding this comment.
Nothing. The pwrmgr_repeat_wakeup_reset_vseq still exists, and it is used by the pwrmgr_sec_cm_lc_ctrl_intersig_mubi test. It was only that the testplan which listed pwrmgr_repeat_wakeup_reset as a test, but there is no test with that name. This patch is only to remove the stale testplan entry, not the sequence.
Signed-off-by: Csaba Kiss <csaba.kiss@semify-eda.com>
Signed-off-by: Csaba Kiss <csaba.kiss@semify-eda.com>
a9f46f5 to
b144dc1
Compare
This is a PR about the power manager block level DV vendoring.
Linked to issue #431