-
Notifications
You must be signed in to change notification settings - Fork 7.6k
usb: device_next: usb3 support #82801
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
74d2fa4
to
d5fda25
Compare
force-push:
|
force-push:
|
The USB3 driver in question is soon to be contributed, and the implementation lives here in the meantime: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The fact that Super-Speed requires bulk endpoints wMaxPacketSize to be 1024 makes #76255 even more important
74cf9e3
to
7249333
Compare
force-push:
SuperSpeedPlus still lacks other modifications to be enabled: everywhere SuperSpeed (SS) is introduced, SuperSpeedPlus (SSP) needs to be introduced as well. |
Here is what this PR it looks like on top of #76255: I thought it would be more suited to wait #76255 to be rebased before force-pushing this here. |
force-push:
|
This pull request has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this pull request will automatically be closed in 14 days. Note, that you can always re-open a closed pull request at any time. |
Force-push:
Should USB 3 Super-Speed Gen1x1/Gen1x2/Gen2x1/Gen2x2 naming be adopted anticipating the possibility of the FX5/FX5N/FX10/FX20 controllers joining? [EDIT: wrong keybinding, I did not mean to close it] |
force-push:
|
It might be possible to dodge the problem by using:
Combined with this to describe the full Gen1x1, Gen1x2, Gen2x1, Gen2x2:
|
960448b
to
9f6a4fd
Compare
Introduce definitions to enable USB3 device controllers to be written. So far, USB 3 support got added to the subsystem, UDC common code, the Loopback class, and the CDC-ACM class. Signed-off-by: Josuah Demangeon <me@josuah.net>
Force-push:
|
|
This adds definitions needed for USB3 support.
There is no USB3 controller supported upstream yet. Should I wait to have the driver contributed in the same PR?
Here is the result of USB3CV for a this upcoming driver:
https://josuah.net/paste/rOzDHBjCbAIWO8d4qZu3/Chapter_9_Tests_USB_3_Gen_X_Failed_2024_12_10_08_18_16.html
It fails at SetFeature, as well as re-enumerating as USB2 (but this is related to the driver, not the USB3 handling).
But everything else is passing.
It also runs well with Twister on SuperSpeed configuration:
west twister --platform native_sim --scenario tests/subsys/usb/device_next/usb.device_next --inline-logs