From: Felipe Balbi <felipe.balbi@linux.intel.com>
To: ayaka <ayaka@soulik.info>
Cc: Greg KH <gregkh@linuxfoundation.org>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
b-liu@ti.com
Subject: Re: musb: am3358: having problem with high-speed on usb1 at peripheral
Date: Thu, 18 Aug 2016 09:35:22 +0300 [thread overview]
Message-ID: <87twei60ut.fsf@linux.intel.com> (raw)
In-Reply-To: <680379fb-52ac-a717-0657-dd60911f8276@soulik.info>
[-- Attachment #1: Type: text/plain, Size: 2039 bytes --]
Hi,
ayaka <ayaka@soulik.info> writes:
>>>>>> On 08/13/2016 01:44 AM, Greg KH wrote:
>>>>>>> On Sat, Aug 13, 2016 at 12:38:46AM +0800, ayaka wrote:
>>>>>>>
>>>>>>>> On 08/12/2016 03:40 PM, Greg KH wrote:
>>>>>>>>> On Fri, Aug 12, 2016 at 10:23:15AM +0800, ayaka wrote:
>>>>>>>>> Hello all:
>>>>>>>>> I recently add a support for customize am3358 board using the branch
>>>>>>>>> processor-sdk-linux-03.00.00 from Ti git. But I meet a problem with musb
>>>>>>>>> at the peripheral mode.
>>>>>>>> Then you are going to have to get support from TI for this, nothing we
>>>>>>>> can do here about random vendor kernel trees, sorry.
>>>>>>>>
>>>>>>>> If you can use the 4.7 tree, or better yet, the 4.8-rc tree, then we
>>>>>>> I have tried the 4.8-rc1, I meet the same problem.
>>>>>> What problem is that exactly?
>>>>> Sorry, the USB1 can't work at high speed gadget mode and have DMA problem.
>>>>> musb-hdrc musb-hdrc.0.auto: Failed to request rx1.
>>>>> musb-hdrc musb-hdrc.0.auto: musb_init_controller failed with status -517
>>>> -517 is EPROBE_DEFER. Most likely DMA hasn't probed and MUSB is
>>>> deferring to try later. This does _NOT_ MUSB can't work with
>>>> DMA. Perhaps you didn't enable support for MUSB's DMA engine.
>>>>
>>> I have set the status of cppi41dma to okay in dts. And CONFIG_USB_TI_CPPI41_DMA,
>>> CONFIG_TI_CPPI41 and CONFIG_TI_EDMA are enabled with build into kernel.
>>>
>>> Anything else I should do?
>> no, that should do it. Since musb returned -EPROBE_DEFER, it will retry
>> probing later. Check if musb probed fine. The easiest way is to check if
>> you have anything in /sys/class/udc/
> Yes, it has musb-hdrc.0.auto. But it doesn't mean that it fallback PIO mode?
no, it doesn't. MUSB knows it needs the DMA, that's why is defers its
own probe routine.
> Actually I don't care whether it use PIO or DMA, I just can't bear it
> work in USB 2.0 Full Speed mode, too slow.
So it always enumerates in Full-speed? That's odd. Bin, any ideas?
--
balbi
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 800 bytes --]
next prev parent reply other threads:[~2016-08-18 6:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-12 2:23 musb: am3358: having problem with high-speed on usb1 at peripheral ayaka
2016-08-12 7:40 ` Greg KH
2016-08-12 16:38 ` ayaka
2016-08-12 17:44 ` Greg KH
2016-08-12 17:59 ` ayaka
2016-08-16 7:10 ` Felipe Balbi
2016-08-16 8:10 ` Ayaka
2016-08-16 8:31 ` Felipe Balbi
2016-08-16 14:05 ` ayaka
2016-08-18 6:35 ` Felipe Balbi [this message]
2016-08-15 20:53 ` musb: am3358: having performance problem with usb1 ayaka
2016-08-18 16:08 ` musb: am3358: having problem with high-speed on usb1 at peripheral Bin Liu
2016-08-23 1:57 ` Ayaka
2016-08-23 15:17 ` Bin Liu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87twei60ut.fsf@linux.intel.com \
--to=felipe.balbi@linux.intel.com \
--cc=ayaka@soulik.info \
--cc=b-liu@ti.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).