STM32U5: Add ADC drivers #3688
Merged
STM32U5: Add ADC drivers #3688
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
|
I just wanted to add that I’m also looking for ADC driver support for the STM32U5, as I plan to use the ADC in an upcoming project. Thanks for the work on this PR so far, and I’m looking forward to seeing it reviewed! |
|
could you fix CI? |
|
Should be fixed now! My first attempt failed so I did a force push to remove it from the history. I'm not entirely sure what's considered good practice with git but I hope it's okay. |
github-merge-queue
bot
removed this pull request from the merge queue due to failed status checks
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.
This pull request adds ADC drivers for the U5 series with both blocking and async reads. One quirk of the U5 series is that some models have two simultaneous revisions of the peripheral. To handle this I've had to touch the internals a bit. The issue in stm32-data has some more details.
Closes issue:
#3654