linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: shawn.guo@freescale.com (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: i.MX6 USB OTG support is broken on linux-next
Date: Sun, 11 May 2014 09:40:28 +0800	[thread overview]
Message-ID: <20140511014027.GV2794@dragon> (raw)
In-Reply-To: <4285b0d55d2545b99c4ba6b703e65a12@BL2PR03MB226.namprd03.prod.outlook.com>

On Sun, May 11, 2014 at 08:40:25AM +0800, Chen Peter-B29397 wrote:
> As I explained before: 
> "OTG devices and Embedded Hosts both have Targeted Host functionality,
> and each Targeted Host has its TPL (Targeted Peripheral List), only the 
> devices are at TPL are supported by Targeted Host."
> 
> So when the board is OTG & EH (CONFIG_USB_OTG is set), it should
> have TPL according to spec. In fact, even the CONFIG_USB_OTG_WHITELIST
> is not set, the non-TPL devices have not worked well, eg, it will
> not be enumerated again after it has disconnected from host 10 seconds
> later due to vbus has turned off by host.

So all in all, it sounds to me that in my case, USB_OTG_FSM shouldn't be
set, neither in defconfig nor manually in menuconfig, right?

What about USB_OTG?  Can I set it in defconfig or manually in
menuconfig?

Shawn

  reply	other threads:[~2014-05-11  1:40 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-09 13:00 i.MX6 USB OTG support is broken on linux-next Shawn Guo
2014-05-10 11:10 ` Peter Chen
2014-05-10 13:18   ` Shawn Guo
2014-05-10 13:57     ` Li Jun
2014-05-11  1:34       ` Shawn Guo
2014-05-12  5:45       ` Sascha Hauer
2014-05-13  0:33         ` Peter Chen
2014-05-13  5:48           ` Sascha Hauer
2014-05-11  0:40     ` Peter Chen
2014-05-11  1:40       ` Shawn Guo [this message]
2014-05-12  1:22         ` Peter Chen
2014-05-12 13:54           ` Shawn Guo
2014-05-13  0:25             ` Peter Chen
2014-05-13  1:42               ` Shawn Guo
2014-05-13  1:10                 ` Li Jun
2014-05-13  2:40                   ` Shawn Guo
2014-05-13  2:40                 ` Peter Chen

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=20140511014027.GV2794@dragon \
    --to=shawn.guo@freescale.com \
    --cc=linux-arm-kernel@lists.infradead.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).