[DOC] Clarify timing requirements for cptra_pwrgood and cptra_rst_b #571
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…rtion of cptra_rst_b
calebofearth
requested review from
bharatpillilli,
Nitsirks,
varuns-nvidia and
steph-morton
…ally falls in doc'd bound
…h updated timestamp and hash after successful run
|
I think Varun's statement of should is fine IMO because there are SOCs that don't do this today; so it is a recommendation on best security practice but I am OK with "shall" |
steph-morton
approved these changes
Aug 19, 2024
Nitsirks
approved these changes
Aug 20, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add integration requirements to stipulate timing for assertion of cptra_pwrgood and deassertion of cptra_rst_b.