OMMemoryMap: register map can only go to 1 memory region #2496
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
…y 1 matching memory region
sequencer
added a commit
to sequencer/sifive-blocks
that referenced
this pull request
May 13, 2022
sequencer
added a commit
to chipsalliance/rocket-chip-blocks
that referenced
this pull request
Jun 5, 2022
sequencer
added a commit
to chipsalliance/rocket-chip-blocks
that referenced
this pull request
Mar 9, 2023
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.
OM Memory Map: prohibit passing a register map if there is not exactly 1 matching memory region
Related issue:
Type of change: other enhancement
Impact: no functional change
Development Phase: implementation
Release Notes
Add requirement to ensure that
getOMMemoryRegionsis called correctly