linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: ayaka <ayaka@soulik.info>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: 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: Sat, 13 Aug 2016 00:38:46 +0800	[thread overview]
Message-ID: <295cf920-535e-9f17-c477-1fa8f4972630@soulik.info> (raw)
In-Reply-To: <20160812074051.GA12546@kroah.com>



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.
I have enabled the CONFIG_OMAP_USB2, I don't find at ti's kernel.
> will be glad to help you out.
>
> good luck!
>
> greg k-h

  reply	other threads:[~2016-08-12 16:39 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 [this message]
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 ` 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=295cf920-535e-9f17-c477-1fa8f4972630@soulik.info \
    --to=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).