update tinyusb to v0.17.0 (5217cee5) #9664
Merged
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
tannewt
approved these changes
Sep 27, 2024
Member
tannewt
left a comment
tannewt
left a comment
There was a problem hiding this comment.
Thanks! This is only ~30 commits or so. I don't expect to have any issues with it.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
As suggested by tannewt on discord, I'm making this PR to update the lib/tinyusb submodule commit from its old value of tinyusb @ 4349e99f to the new value of tinyusb @ 5217cee5, which is the commit for TinyUSB release 0.17.0.
The main benefit of this from my perspective is to get better support for USB host interfaces using the MAX3421E chip, but there are various other changes (see 0.17.0 release notes).
Scott suggested that updating this submodule would be unlikely to cause problems. But, I haven't done the builds and hardware tests to verify that. This is my first time attempting to change a CircuitPython submodule. Also, I don't have experience with testing what happens to build sizes on all the relevant flash constrained boards, etc. So, reviewers beware.