public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bin Liu <b-liu@ti.com>
To: ayaka <ayaka@soulik.info>
Cc: <linux-usb@vger.kernel.org>, Felipe Balbi <balbi@kernel.org>,
	<gregkh@linuxfoundation.org>, <linux-kernel@vger.kernel.org>
Subject: Re: musb: am3358: having problem with high-speed on usb1 at peripheral
Date: Thu, 18 Aug 2016 11:08:40 -0500	[thread overview]
Message-ID: <20160818160712.GA1853@uda0271908> (raw)
In-Reply-To: <1470968595-29231-1-git-send-email-ayaka@soulik.info>

Hi,

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.
>   I have force usb1 in peripheral mode in dts as it only have USB_DP,
> USB_DM and USBDRV connected. I start up a ether gadget using the configfs,

Do you mean USB1_DRVVBUS pin? If so, you have wrong hw design. For
peripheral mode, you should float this pin, but connect USB1_VBUS pin
instead.

Regards,
-Bin.

> But I found it would always work on the USB 2.0 full speed mode,
> even the testmode can't force it in high speed mode or it won't appear
> at host side. If I want it work at high speed mode, what should I do?
>   I also meet the DMA problem, I have to apply the "ARM: dts: am33xx: 
> fix DMA support for the second USB interface", but does patches really
> work? Although it make the error message disapear, but the mail list
> said the just make the usb back to PIO mode.
> 
> -- 
> 2.7.4
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-usb" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2016-08-19  1:46 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
2016-08-15 20:53       ` musb: am3358: having performance problem with usb1 ayaka
2016-08-18 16:08 ` Bin Liu [this message]
2016-08-23  1:57   ` musb: am3358: having problem with high-speed on usb1 at peripheral 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=20160818160712.GA1853@uda0271908 \
    --to=b-liu@ti.com \
    --cc=ayaka@soulik.info \
    --cc=balbi@kernel.org \
    --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