linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Kamil Debski <kamil@wypas.org>,
	Sylwester Nawrocki <s.nawrocki@samsung.com>,
	Kishon Vijay Abraham I <kishon@ti.com>,
	Felipe Balbi <felipe.balbi@linux.intel.com>,
	Kukjin Kim <kgene@kernel.org>,
	Javier Martinez Canillas <javier@osg.samsung.com>,
	linux-usb@vger.kernel.org, linux-samsung-soc@vger.kernel.org,
	linux-kernel@vger.kernel.org, Felipe Balbi <balbi@kernel.org>,
	Richard Genoud <richard.genoud@gmail.com>,
	Anand Moon <linux.amoon@gmail.com>,
	Marek Szyprowski <m.szyprowski@samsung.com>,
	Markus Reichl <m.reichl@fivetechno.de>
Subject: Exynos5422 EHCI (USB 2.0) - Odroid XU4 - port 1 resume error -110
Date: Sun, 29 Jan 2017 15:35:37 +0200	[thread overview]
Message-ID: <CAJKOXPdFuixraNh_aZt9OMU5bEjtS81dz-mBLfWRBE6ejjeWaQ@mail.gmail.com> (raw)

Hi,

On Odroid XU4 with an external usb2514 hub (evaluation board from SMSC
or TI) connected to the USB2.0 port of EHCI controller, whenever I
plug some USB device into the usb2514 hub I see errors like:
[   73.969179] exynos-ehci 12110000.usb: port 1 resume error -110
[   74.003259] usb 1-1: USB disconnect, device number 2
[   74.017432] usb usb1-port1: cannot reset (err = -32)
[   74.021141] usb usb1-port1: cannot reset (err = -32)
[   74.026832] usb usb1-port1: cannot reset (err = -32)
[   74.030974] usb usb1-port1: cannot reset (err = -32)
[   74.036677] usb usb1-port1: cannot reset (err = -32)
[   74.041919] usb usb1-port1: Cannot enable. Maybe the USB cable is bad?
[   74.140923] usb usb1-port1: unable to enumerate USB device

Flooding the console. USB device does not work.

Tested:
1. next-20170125,
2. mainline v4.10-rc5-393-g53cd1ad1a68f,
3. Hardkernel vendor kernel 3.10


It does not look like an issue of usb2514 but rather a combination of
usb2514 + Exynos EHCI because:
1. Happens only when usb2514 hub is directly connected to the USB2.0
port of EHCI controller.
2. If usb2514 is connected through other hub (like to other ports on
the board) - everything works fine.
3. I tested two different usb2514 hubs - one from TI, second from
SMSC. Both behave the same.
4. I had the same issue on DWC3 controller (USB 3.0 port) and in that
case helped ENABLING bits DWC3_GUSB2PHYCFG_SUSPHY and
DWC3_GUSB3PIPECTL_SUSPHY which is I think equal to disabling the
snps,dis_u3_susphy_quirk quirks.


It seems that issue is strictly related to Exynos5422 USB 2.0 driver
(phy?) and this hub. The drivers involved:
 - drivers/phy/phy-exynos5250-usb2.c
 - drivers/phy/phy-samsung-usb2.c
 - drivers/usb/host/ehci-exynos.c

Any ideas?

Best regards,
Krzysztof

             reply	other threads:[~2017-01-29 13:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-29 13:35 Krzysztof Kozlowski [this message]
2017-01-30  6:38 ` Exynos5422 EHCI (USB 2.0) - Odroid XU4 - port 1 resume error -110 Anand Moon

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=CAJKOXPdFuixraNh_aZt9OMU5bEjtS81dz-mBLfWRBE6ejjeWaQ@mail.gmail.com \
    --to=krzk@kernel.org \
    --cc=balbi@kernel.org \
    --cc=felipe.balbi@linux.intel.com \
    --cc=javier@osg.samsung.com \
    --cc=kamil@wypas.org \
    --cc=kgene@kernel.org \
    --cc=kishon@ti.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=linux.amoon@gmail.com \
    --cc=m.reichl@fivetechno.de \
    --cc=m.szyprowski@samsung.com \
    --cc=richard.genoud@gmail.com \
    --cc=s.nawrocki@samsung.com \
    /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).