fix(MiscDrivers,PeriphDrivers): Fix TMR and TFT build errors for MAX32570 #901
Conversation
This file contains 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
|
/clang-format-run |
Jake-Carter
approved these changes
Feb 1, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
Related to issue #900
This PR fixes the build errors for MAX32570A as a result of the changes made for the MAX32572 and MAX32570B.
The previous changes made in
tmr.hwere directed towards the MAX32570B, but did not take into account of the existing MAX32570A naming convention.The TFT drivers used the incorrect SPI definitions for the MAX32570A.
Checklist Before Requesting Review