From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 218118] USB3 port does not work on Chromebook XE303C12 with Linux kernel 6.5.11
Date: Thu, 09 Nov 2023 14:52:49 +0000 [thread overview]
Message-ID: <bug-218118-208809-vA3pMbODiI@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-218118-208809@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=218118
Mathias Nyman (mathias.nyman@linux.intel.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mathias.nyman@linux.intel.c
| |om
--- Comment #1 from Mathias Nyman (mathias.nyman@linux.intel.com) ---
Can you try git bisect to find the offending commit?
looks like xHC host does see something on port 3-1, but can't get
it enumerated properly.
dmesg shows some issues with phy and regulators:
samsung-usb2-phy 12130000.phy: supply vbus not found, using dummy regulator
exynos5_usb3drd_phy 12100000.phy: supply vbus-boost not found, using dummy
regulator
Maybe there is an issue in turning on regulators, supplying ports with power?
Enabling dynamic debug for usbcore and xhci at boot could show more info, can
be done by adding:
usbcore.dyndbg=+p xhci_hcd.dyndbg=+p
to the kernel cmdline.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2023-11-09 14:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-08 21:38 [Bug 218118] New: USB3 port does not work on Chromebook XE303C12 with Linux kernel 6.5.11 bugzilla-daemon
2023-11-09 14:52 ` bugzilla-daemon [this message]
2023-11-09 19:06 ` [Bug 218118] " bugzilla-daemon
2023-11-09 19:07 ` bugzilla-daemon
2023-11-09 19:10 ` bugzilla-daemon
2023-11-10 9:24 ` bugzilla-daemon
2023-11-10 9:26 ` bugzilla-daemon
2023-11-10 9:27 ` bugzilla-daemon
2023-11-10 14:37 ` 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-218118-208809-vA3pMbODiI@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox