tinyusb.git/src/host/usbh.c, branch pr3864-alt

usbh: fix mount and enumeration retry state

2026-09-04T06:49:19Z

host: retry enumeration of the roothub port after a failed attach

2026-09-04T06:49:15Z

enum_full_complete() already closes the failed device (from #3815). Nothing retries the root port itself: the host then sits idle until reboot. Re-post the attach up to USBH_ENUM_ROOT_RETRY_MAX times while the port still reports a connection. The budget is per port and given back when the attachment ends, including when an attach event tears down an in-flight enumeration. tuh_umount_cb() is only called for a device that reached tuh_mounted(). Co-authored-by: Cursor

host: close dev0 when the whole roothub port goes away

2026-09-04T06:49:11Z

A remove for hub_addr = 0, hub_port = 0 covers everything below the root port, but process_remove_event() only closed dev0 when the event named the exact bus address it was enumerating on. Mid-enumeration behind a downstream hub then left enumerating_daddr at 0 and deferred every later attach. Co-authored-by: Cursor

Merge remote-tracking branch 'origin/master' into agent/fix-dwc2-host-fifo-allocation

2026-09-02T13:21:41Z

USBH: fail enumeration cleanly after disconnect

2026-09-02T13:21:41Z

A disconnect can close endpoint zero after an enumeration control stage completes but before USBH submits the next stage or request. HCD submission then legitimately returns false; treating that result as an invariant violation asserts during rapid replug and can leave enumeration unfinished. Complete an in-progress control request as failed when its DATA or status stage cannot be submitted. Propagate submission failures from every asynchronous enumeration continuation and finish enumeration through the normal failure cleanup path. This keeps controller teardown races out of assertions without fabricating a successful transfer. Validated by interrupting enumeration during rapid STM32U5A5 replug tests with DWC2 DMA and slave modes.

Merge pull request #3828 from dxbjavid/ep2drv-endpoint-bound

2026-09-01T08:42:39Z

bound endpoint number in tu_bind_driver_to_ep_itf

propagate the endpoint-bound failure on the host path

2026-09-01T08:41:53Z

tu_bind_driver_to_ep_itf() now returns false when ep_num >= CFG_TUH_ENDPOINT_MAX, but the host caller ignores that result and continues enumeration. Configurations such as host/bare_api set the limit to 8, while valid USB devices may use endpoints 8–15. A recognized class can therefore continue and later index ep_status[epnum] or ep2drv[epnum] out of bounds. Wrap this call in TU_ASSERT(...), as the device path already does, so parsing fails immediately. Signed-off-by: HiFiPHile

vendor: remove the obsolete host vendor driver

2026-08-21T04:06:14Z

vendor_host.c/.h implemented a CFG_TUH_VENDOR class driver that no example, board or test ever enabled: usbh's driver table entry was compiled out everywhere, and the six tusb_config.h files that mentioned the macro all set it to 0. Maintainer call - dead code, not a shrinking of supported classes. Removes the sources, the usbh driver-table entry, the CFG_TUH_VENDOR default in tusb_option.h, the tusb.h include, both build-system source lists, the rp2040 family.cmake entry and the IAR project template rows.

bound endpoint number in tu_bind_driver_to_ep_itf

2026-08-17T15:30:57Z

Fix usbh empty builtin driver warning

2026-07-05T13:27:30Z

Signed-off-by: HiFiPhile