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: Fri, 9 May 2014 21:00:47 +0800 [thread overview]
Message-ID: <20140509130046.GP2794@dragon> (raw)
I'm running next-20140508 kernel on imx6q-sabresd board with USB
mouse/keyboard connected to OTG port. It works well on 3.15-rc but
is broken on recent linux-next kernel with the message like below.
...
usb 1-1: device v413c p2107 is not supported
hub 1-0:1.0: unable to enumerate USB device on port 1
With the help from Peter, I found that the issue shows up only when
CONFIG_USB_OTG_FSM is enabled. The option is enabled by commit 8fd2f1f
(ARM: imx_v6_v7_defconfig: Enable drivers for i.MX51 USB Host support.)
from IMX tree.
I guess this is a sign that chipidea otg_fsm driver is buggy? I do not
think dropping CONFIG_USB_OTG_FSM selection from imx_v6_v7_defconfig is
a solution, and we need to fix the issue in usb driver, right?
Shawn
next reply other threads:[~2014-05-09 13:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-09 13:00 Shawn Guo [this message]
2014-05-10 11:10 ` i.MX6 USB OTG support is broken on linux-next 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
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=20140509130046.GP2794@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).