driver: spi: mcux_dspi: remove obsolete rx_bufs check #99666
+0
−7
Conversation
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
The DMA misconfiguration workaround is no longer necessary. Signed-off-by: Alexandre Rey <[email protected]>
zephyrbot
requested review from
Holt-Sun,
dbaluta,
decsny,
dleach02,
manuargue,
mmahadevan108,
tbursztyka and
teburd
|
dleach02
approved these changes
Nov 26, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
This removes the
rx_bufsNULL check that was introduced as a workaround for DMA misconfiguration issue.The DMA misconfiguration workaround is no longer necessary since I was unable to reproduce the problem described in the comment.
Additionally, the workaround only covered the case where
rx_bufs == NULL, but not cases whererx_bufs->buffers == NULLorrx_bufs->count == 0, which results in the same effective condition. Since the workaround was incomplete and the underlying issue does not appear reproducible anymore, it is clearer and safer to remove it.Fixes: #98634