EFC/Kasli: Add sys5x clock domain #137
Merged
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
It would be better if the MMCM configuration stays completely intact when it is disabled, so we can just disable it on release-7 and not worry about introducing regressions. Disabling it right now doesn't seem to do much, Vivado would probably remove the unused BUFG on its own already. |
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.
This PR adds the
sys5xclock domain to Kasli_RTIOSysCRG(optional, default disabled) and EFC.sys4xandsys5xsys4x_dqsis generated by an additional MMCM, which takessys4xMemory test are passing for both Kasli v2.0 and EFC.