feature(esp_tinyusb): Added tusb_teardown() call while tinyusb_driver_uninstall()

[roma-jam]

Requirements

• To uninstall tinyusb driver, a teardown tinyusb stack should be called.
• tud_deinit() feature was implemented in upstream, starting with version v0.17.0.

Description

• Added tusb_teardown() call while tinyusb_driver_uninstall()
• Added test app to verify teardown feature

Testing

1. Install TinyUSB device without any class
2. Wait SetConfiguration() (tud_mount_cb)
3. If attempts == 0 goto step 8
4. Wait TEARDOWN_DEVICE_DETACH_DELAY_MS
5. Uninstall TinyUSB device
6. Wait TEARDOWN_DEVICE_INIT_DELAY_MS
7. Decrease attempts by 1, goto step 3
8. Wait TEARDOWN_DEVICE_DETACH_DELAY_MS
9. Uninstall TinyUSB device

Notes:

• when amount of teardown configured to 0, then only one install-uninstall routine is fulfilled.
• device presence used subprocess call "lsusb" and check the Espressif VID/PIN in the output

Related issues

• Original espressif/tinyusb PR: feature(usbd): Added tud_teardown() tinyusb#27 (closed, because of synchronizing with upstream v0.17)
• Requires tusb_teardown() API: feature(tusb): Added tusb_teardown() tinyusb#44
• Resolve esp32s3, restarting cdc software serial doesn't work (IDFGH-12813) esp-idf#13788
• Closes USB stack will not reinitialize after deinit. (IDFGH-14332) esp-idf#15122

[roma-jam]

@tore-espressif , @peter-marcisovsky
This changes unlock the possibility to run usb device tests one by one (espressif/tinyusb#27 should be merged first, though).

I posted two questions for both of you, because it seems that we can make it better and we can use it.

I need that for enumeration driver testing (but maybe I will eliminate esp_tinyusb component from the chain, but anyway), so feel free to check it out when possible.

Meanwhile, I will go and cover the Enum Driver as much as I can.

[peter-marcisovsky]

Left some observations from using the test app

[finger563]

Is there a timeline for this feature to be finalized?

[roma-jam]

Hi @finger563 ,

This feature allows the re-configure the driver with these changes: espressif/tinyusb#27
But as far as the same changes are already in the upstream, so we will rebase these changes after updating version to v0.17.0.
For current feature there is no available timeline for now, but the one thing for sure: the update to v0.17.0 will be done first.

Meanwhile, this feature should be available in the upstream of TinyUSB, if anything it is possible to use it.

Sorry for the inconvenience.

[roma-jam]

I have updated the test, changing the logic to checking the result of "lsusb" output to verify device attachment and detachment while install/uninstall.

The previous test with teardown + cdc data exchange between host and device moved here: #106

PTAL

[tore-espressif]

@roma-jam Looks good, thank you for the test!

[roma-jam]

Applied several fixes from review in here: #106

[peter-marcisovsky]

LGTM, I could run the test locally on my setup, works fine.