Quantcast
Channel: Raspberry Pi Forums
Viewing all articles
Browse latest Browse all 7503

Advanced users • mass-storage gadget: is stall=0 required due to limitations?

$
0
0
Trying to figure-out some issues around mass-storage gadget.
We often find snippets passing stall=0 parameter when loading driver, in particular to work-around warnings like:

Code:

[   34.516207] dwc2 20980000.usb: dwc2_hsotg_ep_sethalt(ep 51f609dd ep5in, 1)[   34.621578] dwc2 20980000.usb: dwc2_hsotg_ep_sethalt(ep 51f609dd ep5in, 1)[   34.621655] dwc2 20980000.usb: dwc2_hsotg_start_req: ep5 is stalled[   34.621802] dwc2 20980000.usb: dwc2_hsotg_ep_sethalt(ep 51f609dd ep5in, 0)[   34.622059] dwc2 20980000.usb: dwc2_hsotg_ep_sethalt(ep 51f609dd ep5in, 1)[   34.731527] dwc2 20980000.usb: dwc2_hsotg_ep_sethalt(ep 51f609dd ep5in, 1)[   34.731579] dwc2 20980000.usb: dwc2_hsotg_start_req: ep5 is stalled
However default for mass-storage should be stall=1 according to docs, unless interface is known to have limitations (might be some exception list somewhere).

I could not find reference to such limitations in Pi official docs: can anyone comment (which limitation, reasons, etc)?
Could this be a config/dtb issue on some particular devices (PiZero or al.)? Should such devices be added to exception-list?
Thanks for any tip.

Statistics: Posted by macmpi — Mon Jan 05, 2026 2:28 pm — Replies 0 — Views 23



Viewing all articles
Browse latest Browse all 7503

Trending Articles