From: bugzilla-daemon@bugzilla.kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 206435] New: dwc3 dwc3.3.auto: no usb2 phy configured
Date: Wed, 05 Feb 2020 20:09:29 +0000 [thread overview]
Message-ID: <bug-206435-208809@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=206435
Bug ID: 206435
Summary: dwc3 dwc3.3.auto: no usb2 phy configured
Product: Drivers
Version: 2.5
Kernel Version: 5.6
Hardware: x86-64
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: USB
Assignee: drivers_usb@kernel-bugs.kernel.org
Reporter: youling257@gmail.com
Regression: No
android_x86:/ $ dmesg | grep dwc
[ 8.956913] dwc3 dwc3.3.auto: failed to create device link to
dwc3.3.auto.ulpi
[ 8.979682] dwc3 dwc3.3.auto: no usb2 phy configured
[ 8.986984] dwc3 dwc3.3.auto: failed to initialize core: -22
[ 8.993597] dwc3: probe of dwc3.3.auto failed with error -22
android_x86:/ $
some Bay trail device has a phy_tusb1210 used for dwc3.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2020-02-05 20:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-05 20:09 bugzilla-daemon [this message]
2020-02-05 20:16 ` [Bug 206435] dwc3 dwc3.3.auto: no usb2 phy configured bugzilla-daemon
2020-02-06 6:24 ` Felipe Balbi
2020-02-06 6:25 ` bugzilla-daemon
2020-02-06 12:47 ` bugzilla-daemon
2020-02-06 18:32 ` Felipe Balbi
2020-02-06 18:33 ` Felipe Balbi
2020-02-07 8:52 ` Alexandre Torgue
2020-02-06 18:32 ` bugzilla-daemon
2020-02-06 18:33 ` bugzilla-daemon
2020-02-06 19:25 ` bugzilla-daemon
2020-02-07 8:52 ` bugzilla-daemon
2020-02-07 12:19 ` bugzilla-daemon
2020-02-13 22:15 ` bugzilla-daemon
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=bug-206435-208809@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-usb@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.