HT32: SPI: avoid write collisions when SPI FIFO is disabled #361
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 improves SPI transmission reliability when SPI FIFO is not used. Without this change, I experienced hangups when frequently transmitting data to SPI flash.
For reference:
When SPI FIFO is enabled, a write collision occurs when writing to SPIDR register while both the TX buffer and SPI shift register are full (which is when TXE flag is not asserted).
When SPI FIFO is disabled, a write collision occurs when writing to SPIDR register while both TX FIFO and TX shift register are full. Here, the TXBE flag remains appropriate since it is used to check when TX buffer is empty and when the TX FIFO is below a set threshold value.