You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not a bug in Raw Gadget but still related to its usage.
dwc2 calls the gadget driver's ->disconnect() callback when the port to which the device is connected gets reset by
the host (via SET_FEATURE/PORT_RESET). It should call ->reset() instead.
Asked kernel maintainers about getting this fixed, see here.
The text was updated successfully, but these errors were encountered:
Hi, was there ever any progress on this? I suspect I might be hitting it in my project. I see an alleged device reset then disconnect. Admittedly I don't know enough about the stack to know for sure what the issue is though.
Using rpi 4b (dwc2) and usb mass storage
Mar 18 00:44:29 host usb-proxy[1435]: Resent Bulk transfer on EP02 for attempt 1. length(1024), transferred(1024)
Mar 18 00:44:29 host usb-proxy[1435]: EP2(bulk_out): device likely reset, stopping thread
Mar 18 00:44:29 host usb-proxy[1435]: End reading thread for EP02, thread id(1709)
Mar 18 00:44:29 host usb-proxy[1435]: event: disconnect
Mar 18 00:44:29 host usb-proxy[1435]: Resetting device
edit: I see you mention testing with dummy_hcd on another issue, I'll give that a go before blaming dwc2
Not a bug in Raw Gadget but still related to its usage.
dwc2 calls the gadget driver's
->disconnect()
callback when the port to which the device is connected gets reset bythe host (via
SET_FEATURE
/PORT_RESET
). It should call->reset()
instead.Asked kernel maintainers about getting this fixed, see here.
The text was updated successfully, but these errors were encountered: