[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <874m6l9ojr.fsf@linux.intel.com>
Date: Tue, 16 Aug 2016 10:10:48 +0300
From: Felipe Balbi <felipe.balbi@...ux.intel.com>
To: ayaka <ayaka@...lik.info>, Greg KH <gregkh@...uxfoundation.org>
Cc: linux-usb@...r.kernel.org, linux-kernel@...r.kernel.org,
b-liu@...com
Subject: Re: musb: am3358: having problem with high-speed on usb1 at peripheral
Hi,
ayaka <ayaka@...lik.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.
--
balbi
Download attachment "signature.asc" of type "application/pgp-signature" (819 bytes)
Powered by blists - more mailing lists