On 2018-04-05 11:24, Felipe Balbi wrote:
Felipe, "not all be supported" do u mean some xhci compliant host do not
support uas? and they have such quirks
Greg KH <gre...@linuxfoundation.org> writes:
On Wed, Apr 04, 2018 at 05:14:50PM +0530, tnim...@codeaurora.org
I am able to duplicated the UAS issue on 4.16 as well.
The behavior is same new usb device detects and reset after aprox 30
Logs are already shared below.
We are using Synopsys dwc3 as host controller, May I know have tested
I have tried it on Linux PC (x86 Ubuntu machine) I could not see the
It enumerates well.
Great, stick with an x86 platform! :)
Looks like a dwc3 host controller issue, try enabling tracing and
debugging in that driver when this happens to see what is going on.
Also look at all of the recent dwc3 patches that were just sent to
for 4.17-rc1 to verify if that solves the issue.
dwc3's host side is xhci compliant :-) Some revisions have some quirks
which may not all be supported.
Tushar, which dwc3 revision are you using? Have you gotten in touch
it is DWC3_REVISION_300A ..3.0a
your HW designers to ask for Errata List? A run with xhci tracepoints
will response you, let me cross check once again with errata list.
enabled will probably give a lot of insight into the issue.
Tushar R Nimkar,
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a
member of Code Aurora Forum, hosted by The Linux Foundation
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html