Fixup SPI init procedure, SPI EEPROM sequencing #17534
Merged
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.
Description
Something weird going on with SPI in the sense that the first use would seemingly fail after init, but only on RP2040.
Under normal circumstances, the first read would be EEPROM when using SPI EEPROM, specifically the magic... which would then trigger an EEPROM reset as the data returned is zero'd out on SPI failure.
This PR changes the sequencing:
spi_initit stops the SPI peripheral as a final action,spi_stop()on failure -- the previous assumption was thatspi_start()failing did not necessitate a subsequentspi_stop()-- this now explicitly invokes the stop upon all failures.Types of Changes
Checklist