[DOC] Revise explanatory language about I3C core frequency requirements and CDC#1143
Merged
Conversation
Updated the required frequency for I3C core operation and clarified the change from a 170 MHz clock due to CDC issues. Added references to discussions about CDC violations.
upadhyayulakiran
approved these changes
May 5, 2026
calebofearth
added a commit
that referenced
this pull request
May 20, 2026
…12, 1125, 1129, 1143, 1144) (#1149) * [Cherry-pick] [DOC] RDC constraint and version update (#922) * [Cherry-pick] [DOC] Clarify min clock frequency requirement (#1011) * Update clock frequency requirements in specification Clarified minimum operating clock frequency requirements for I3C core. * Correct timing reference in clock frequency section * [Cherry-pick] [DOC] Update I3C core integration details (#1012) * [Cherry-pick] [DOC] Strap and reset clarifications (#1125) * update reset requirement to be consistent update strap signals with requirement details for driving before reset de-assertion * MICROSOFT AUTOMATED PIPELINE: Stamp 'user/dev/michnorris/doc_updates' with updated timestamp and hash after successful run --------- Co-authored-by: EMRE KARABULUT <63821295+ekarabu@users.noreply.github.com> * [Cherry-pick] Document LCC token fuse provisioning for HKMS (#1129) Extend the Token Validation python code block to show the full cSHAKE128 hashing workflow with byte-arrays: - Show raw token as little-endian byte-array input - Show hashed token as byte-array output for HKMS to provision into SECRET_LC_TRANSITION_PARTITION fuses - Fix TOKEN_OFFSET word ordering (was misordered for OFFSET 1 and 2) to match RTL register mapping - Fix 'Toke' typo to 'Token' Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * [Cherry-pick] [DOC] Revise explanatory language about I3C core frequency requirements and CDC (#1143) Updated the required frequency for I3C core operation and clarified the change from a 170 MHz clock due to CDC issues. Added references to discussions about CDC violations. * [Cherry-pick] [DOC] Clarify connection requirement for AXI additional signals (#1144) * Clarify connection requirement for AXI additional signals * Update AXI signal specifications in documentation Clarify unused AXI signals and their role in the Caliptra Subsystem. Provide details on AXI USER width and ID width requirements. --------- Co-authored-by: pjangid30 <pjangid@nvidia.com> Co-authored-by: Clayton Kuchta <ckuchta@microsoft.com> Co-authored-by: EMRE KARABULUT <63821295+ekarabu@users.noreply.github.com> Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Updated the required frequency for I3C core operation and clarified the change from a 170 MHz clock due to CDC issues.