allow respond to read transactions between address write and data write to speed up response#7
Open
AngelaGonzalezMarino wants to merge 1 commit intopulp-platform:masterfrom
Open
Conversation
…te to speed up response
Author
|
Hi @andreaskurth, |
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
1 participant
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.
Current implementation goes to wait valid state after receiving an address write, until the data write comes
The proposal is to permit to respond to read requests that may come in between to speed up the response time
This is useful for example when integrating a DMA
We have tested this change with the CVA6 smoke tests and benchmarks, apart from our own integration tests with other peripherals such as DMA.