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: Tue, 13 May 2014 09:42:48 +0800	[thread overview]
Message-ID: <20140513014247.GH8330@dragon> (raw)
In-Reply-To: <04dad7ad8f0247b9bef4fea1db8a8bc8@BL2PR03MB226.namprd03.prod.outlook.com>

On Tue, May 13, 2014 at 08:25:18AM +0800, Chen Peter-B29397 wrote:
>  
> > > >
> > >
> > > In your case, you should not set CONFIG_USB_OTG no matter at defconfig
> > > and at menuconfig.
> > 
> > Hmm, at least in my testing (USB mouse/keyboard connected to OTG port),
> > it works as before even I enable CONFIG_USB_OTG, as long as I do *not*
> > enable CONFIG_USB_OTG_FSM.
> > 
> > Since it works for my case, I'm wondering why you think I shouldn't
> > enable CONFIG_USB_OTG at all.
> > 
> 
> If your device is not OTG device, there is no reason you need to enable
> CONFIG_USB_OTG.

Whether I should enable CONFIG_USB_OTG depends on what devices I will
use?  This is insane to me.

Look, there is an USB OTG port on my board, and it should just be the
reason that's good enough for me to build a kernel with CONFIG_USB_OTG,
shouldn't it?  I do not even know what type of devices will be plugged
into this USB OTG port when I was building the kernel.

Shawn

> Yes, it may work for some devices when enable CONFIG_USB_OTG,
> but it will confuse other host or device which is connected with you, eg,
> your device will report your have supported some otg capabilities, eg, SRP or
> HNP.

  reply	other threads:[~2014-05-13  1:42 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
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 [this message]
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=20140513014247.GH8330@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).