forked from hathach/tinyusb
-
Notifications
You must be signed in to change notification settings - Fork 39
Synchronization patch with changes from release/v0.18 [v0.19] #68
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
Draft
roma-jam
wants to merge
53
commits into
release/v0.19
Choose a base branch
from
sync/release_v0.18
base: release/v0.19
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
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
…ounter fix(usbd/dcd_dwc2): Fixed epin counter assert, update buffer name for usbd_control debug
…_build_check feature(ci): Added esp-iot-solution USB Device examples build verification
…st_apps ci(tinyusb): Added esp-usb test_apps build and run (esp32s2)
Upstream synchronization
…_class feature(uvc): Applied proprietary changes in UVC Device class
Upstream synchronization
feature(tusb): Added tusb_teardown()
ci(tinyusb): Added esp-idf run (esp32s2)
* fixed unit test with ceedling 1.0.0
fix(ci): Fixed CI workflows
Upstream synchronization
ci(workflow): Update ubuntu runners to ubuntu-latest
TinyUSB does not provide any locking means to protect the DCD variables. This can lead to race conditions when the user is trying to submit a transfer while the device is being disconnected. This can cause the device to be in an inconsistent state, leading to a crash or undefined behavior. This commit adds a spin-lock to protect the DCD variables during device disconnect. Closes espressif/esp-idf#9691 Also reported in espressif/esp-usb#131
fix(dcd): Fixed race condition on device disconnect
Upstream synchronization
feature(usbtmc): add usbtmc device class
fix(ci): Fixing build IDF and IOT solutions examples
Add ESP32-H4 as a supported MCU in TinyUSB and wire it into build/runtime: - CMakeLists: map IDF target esp32h4 → OPT_MCU_ESP32H4, family=esp32sx - tusb_option.h: define OPT_MCU_ESP32H4 - tusb_mcu.h: enable DWC2 USBIP for H4 - dcd_dwc2.c: add H4 USB_WRAP field aliases (wrap_* → legacy names) - dwc2_esp32.h: add H4 controller entry (FS base/IRQ, ep caps) - family.c: include H4 in USB init/PHY setup - idf_component.yml: add esp32h4 target This enables TinyUSB examples to build for ESP32-H4.
feat(usb): Add ESP32-H4 support in tinyusb
- Add all targets to esp-usb test apps and esp-idf examples - Fix override tinyusb in the network example
…_example fix(ci): Cleanup and extension of workflows [v0.18]
…_example feature(ci): Adding esp32p4 target to Run step [v0.18]
- Added esp-idf release v6.0 to build & run - Enabled preview target build to the esp-idf examples - Updated the idf-build-apps version to 2.13.3
feature(ci): Updated CI workflows
Upstream synchronization - Partial [v0.18]
…ing_file fix(ci): Added path to recently added ignore_warning_file.txt in esp-usb
2 tasks
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
Synchronization logic:
release/v0.19branch from Prepare release/v0.19 branch #60sync/release_v0.18branch fromrelease/v0.18branch from fix(ci): Added path to recently added ignore_warning_file.txt in esp-usb #67release/v0.19branch from step 1 tosync/release_v0.18branch with solved conflicts:idf_component.ymlsrc/portable/synopsys/dwc2/dcd_dwc2.c(BValid override + Critical Section for xfer)src/portable/synopsys/dwc2/dwc2_common.cReset proceduresrc/tusb.c(teardown vs deinit)src/tusb.h(teardown vs deinit)src/tusb_option.h(H4 controller definition vs H4, C5, C61)sync/release_v0.18branch torelease/v0.19branch (current PR)Changes
This PR applies the ESP-related changes from the
release/v0.18branch torelease/v0.19branch.release/v0.19branch (tags:v0.19.0.1-rc0andv0.19.0.1)Related
Test & Verification
Verify, that final version includes:
workflows/upload_component.ymlfrom Prepare release/v0.19 branch #60README.mdfrom Prepare release/v0.19 branch #60idf_component.ymlfrom Prepare release/v0.19 branch #60tusb.h, lines 141-144, backward compatibility fortusb_teardown()now renamed totusb_deinit()from Prepare release/v0.19 branch #60dwc2_common.c, lines 48-55 Reset sequence from the fix(dcd/dwc2): Fix reset procedure for versions >=4.20a hathach/tinyusb#3228dcd_dwc2.cfrom fix(dcd_dwc2): Changed OTG Bvalid override configuration for ESP32 #19Tests, that are not available in CI yet:
Limitations