From: "Walt Jr. Brake" <mr.yming81@gmail.com>
To: chunfeng.yun@mediatek.com
Cc: eddie.hung@mediatek.com, gregkh@linuxfoundation.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org,
linux-usb@vger.kernel.org, matthias.bgg@gmail.com,
nishadkamdar@gmail.com, stern@rowland.harvard.edu
Subject: Re: [PATCH v2] usb: core: reduce power-on-good delay time of root hub
Date: Mon, 1 Nov 2021 11:33:16 +0800 [thread overview]
Message-ID: <c639c965-5231-b745-7b59-476877202e0c@gmail.com> (raw)
In-Reply-To: <1618017645-12259-1-git-send-email-chunfeng.yun@mediatek.com>
Three month ago, My USB 3.1 device cannot be detected after upgrade
kernel from version 5.10.41 to 5.10.42.
And I found some other people ran into the same issue:
https://forum.manjaro.org/t/kernel-5-10-59-doesnt-detect-a-connected-usb-external-disk/79320
https://forum.manjaro.org/t/how-to-make-active-usb-hub-work-in-manjaro/84548
Two days ago, I try to fix the issue myself, and I found out that it was
cause by this patch. After revert this patch, my USB 3.1 device can be
detect again.
I have already file a bug on here:
https://bugzilla.kernel.org/show_bug.cgi?id=214875.
next prev parent reply other threads:[~2021-11-01 3:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-10 1:20 [PATCH v2] usb: core: reduce power-on-good delay time of root hub Chunfeng Yun
2021-11-01 3:33 ` Walt Jr. Brake [this message]
[not found] ` <5e907ccd-40bb-2ece-fe05-1a65a74f3aa2@gmail.com>
2021-11-01 14:06 ` Alan Stern
2021-11-02 9:05 ` Mathias Nyman
2021-11-02 20:29 ` Walt Jr. Brake
2021-11-03 20:37 ` Mathias Nyman
2021-11-05 10:00 ` Greg Kroah-Hartman
2021-11-05 13:30 ` Alan Stern
2021-11-05 16:00 ` [PATCH] xhci: Fix USB 3.1 enumeration issues by increasing roothub power-on-good delay Mathias Nyman
2021-11-05 16:09 ` Mathias Nyman
2021-11-05 17:32 ` Walt Jr. Brake
2021-11-05 19:41 ` Mathias Nyman
2021-11-05 16:15 ` Greg KH
2021-11-05 19:56 ` Mathias Nyman
2021-11-06 14:41 ` Greg KH
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=c639c965-5231-b745-7b59-476877202e0c@gmail.com \
--to=mr.yming81@gmail.com \
--cc=chunfeng.yun@mediatek.com \
--cc=eddie.hung@mediatek.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-usb@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=nishadkamdar@gmail.com \
--cc=stern@rowland.harvard.edu \
/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).