From: Krzysztof Kozlowski <krzk@kernel.org>
To: Jules Maselbas <jmaselbas@kalray.eu>
Cc: Minas Harutyunyan <hminas@synopsys.com>,
Felipe Balbi <felipe.balbi@linux.intel.com>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-samsung-soc@vger.kernel.org,
Marek Szyprowski <m.szyprowski@samsung.com>
Subject: [BUG BISECT] USB on Exynos4412 fails after usb: dwc2: gadget: Replace phyif with phy_utmi_width
Date: Fri, 3 May 2019 22:49:58 +0200 [thread overview]
Message-ID: <20190503204958.GA12532@kozik-lap> (raw)
Hi,
Bisect pointed commit 707d80f0a3c5 ("usb: dwc2: gadget: Replace phyif
with phy_utmi_width") as reason for failures of USB on Exynos4412,
Odroid U3 board (ARMv7, exynos_defconfig, TFTP boot with nfsroot from
NFSv4):
[ 4.333996] usb 1-2: new high-speed USB device number 3 using exynos-ehci
[ 4.503942] usb 1-2: device descriptor read/64, error -71
[ 4.793970] usb 1-2: device descriptor read/64, error -71
[ 4.914748] usb usb1-port2: attempt power cycle
[ 6.224267] usb 1-3: new high-speed USB device number 5 using exynos-ehci
[ 6.393983] usb 1-3: device descriptor read/64, error -71
[ 6.684243] usb 1-3: device descriptor read/64, error -71
[ 6.954259] usb 1-3: new high-speed USB device number 6 using exynos-ehci
[ 7.123980] usb 1-3: device descriptor read/64, error -71
[ 7.413969] usb 1-3: device descriptor read/64, error -71
[ 7.534778] usb usb1-port3: attempt power cycle
The boot failure is effect of lack of network adapter (USB, smsc95xx).
Expected:
[ 4.285831] usb 1-3: New USB device found, idVendor=0424, idProduct=3503, bcdDevice=a1.a0
[ 4.288986] usb 1-3: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 4.299596] hub 1-3:1.0: USB hub found
[ 4.300027] hub 1-3:1.0: 3 ports detected
[ 5.895541] smsc95xx 1-2:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1
Full kernel log is here:
https://krzk.eu/#/builders/25/builds/1330/steps/14/logs/serial0
https://krzk.eu/#/builders/25/builds/1330
Let me know if you need any more details.
Best regards,
Krzysztof
next reply other threads:[~2019-05-03 20:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-03 20:49 Krzysztof Kozlowski [this message]
[not found] ` <CGME20190506130052eucas1p25afd4e15648e9efc6fd011e46081fbea@eucas1p2.samsung.com>
2019-05-06 13:00 ` [PATCH] usb: dwc2: Force 8bit UTMI width for Samsung Exynos SoCs Marek Szyprowski
2019-05-06 13:40 ` Jules Maselbas
2019-05-07 6:22 ` Minas Harutyunyan
2019-05-07 8:12 ` Markus Reichl
2019-05-07 9:17 ` Marek Szyprowski
2019-05-07 12:03 ` Marek Szyprowski
2019-05-07 12:38 ` Markus Reichl
2019-06-05 8:57 ` Krzysztof Kozlowski
2019-05-07 6:21 ` [BUG BISECT] USB on Exynos4412 fails after usb: dwc2: gadget: Replace phyif with phy_utmi_width Minas Harutyunyan
2019-05-07 6:43 ` Marek Szyprowski
2019-05-07 10:08 ` [PATCH] usb: dwc2: Use generic PHY width in params setup Jules Maselbas
2019-05-07 10:08 ` Jules Maselbas
2019-05-07 10:54 ` Marek Szyprowski
2019-05-09 9:15 ` [PATCH v2] " Jules Maselbas
2019-05-31 12:22 ` Jules Maselbas
2019-05-31 12:44 ` Minas Harutyunyan
2019-06-06 10:13 ` Marek Szyprowski
2019-06-18 7:26 ` Felipe Balbi
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=20190503204958.GA12532@kozik-lap \
--to=krzk@kernel.org \
--cc=felipe.balbi@linux.intel.com \
--cc=hminas@synopsys.com \
--cc=jmaselbas@kalray.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=m.szyprowski@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).