axi_to_reg_v2: Use RegDataWidth for output multiplexing
#49
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
…DataWidth reg_mux at end was using AxiDataWidth instead of RegDataWidth when it's inputs and outputs were both reg_*_t
|
Sorry for my late reply; thank you for the fix, LGTM 👍 |
paulsc96
approved these changes
Sep 11, 2024
paulsc96
changed the title
RegDataWidth for destination multiplexing
paulsc96
changed the title
RegDataWidth for destination multiplexingRegDataWidth for output multiplexing
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.
Was getting lint error in reg_mux. Saw that reg_mux at end was using AxiDataWidth instead of RegDataWidth when it's inputs and outputs were both reg_req_t and reg_resp_t respectively.