Allowing CSR Width to Exceed Frontdoor Interface Data Width #177
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
mkorbel1
approved these changes
Feb 21, 2025
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.
Description & Motivation
Adds an optional configuration on the CSR block and top modules in which CSR widths can be greater than the frontdoor interface data width. In this case, frontdoor accesses are broken out until logical "chunks" with their own addresses. This can be convenient for implementations with parametrizable register widths (as well as implementations where this happens to be the mode of operation).
Related Issue(s)
N/A
Testing
Enhanced/added to the existing CSR unit tests.
Backwards-compatibility
This is a fully backwards compatible change due to the fact that the new behavior is controlled by a new configuration parameter.
Documentation
Documentation has been updated accordingly.