data_offload: Second attempt at resolving issues with oversized TX transactions #781
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.
The previous commit did indeed resolve the issue i was trying to address, but broke a bunch of other stuff as reported in #778. This PR reverts the previous changes and introduces an alternative approach that should address the original issue, while also allowing the input valid to go low temporarily for TX transactions which haven't finished yet (Imagine a DMA being unable to keep up).