From: bugzilla-daemon@bugzilla.kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 214875] USB 3.1 device cannot be detected
Date: Sat, 30 Oct 2021 05:49:16 +0000 [thread overview]
Message-ID: <bug-214875-208809-xCkhRpLge6@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-214875-208809@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=214875
--- Comment #1 from Walt Jr. Brake (mr.yming81@gmail.com) ---
Yesterday I try to fix it myself, and after I revert the patch [usb: core:
reduce power-on-good delay time of root
hub](https://lore.kernel.org/all/1618017645-12259-1-git-send-email-chunfeng.yun%40mediatek.com/),
compile the kernel and test, it works.
Here is the patch:
diff --git a/drivers/usb/core/hub.h b/drivers/usb/core/hub.h
index 22ea1f4f2d66..73f4482d833a 100644
--- a/drivers/usb/core/hub.h
+++ b/drivers/usb/core/hub.h
@@ -148,10 +148,8 @@ static inline unsigned hub_power_on_good_delay(struct
usb_hub *hub)
{
unsigned delay = hub->descriptor->bPwrOn2PwrGood * 2;
- if (!hub->hdev->parent) /* root hub */
- return delay;
- else /* Wait at least 100 msec for power to become stable */
- return max(delay, 100U);
+ /* Wait at least 100 msec for power to become stable */
+ return max(delay, 100U);
}
static inline int hub_port_debounce_be_connected(struct usb_hub *hub,
--
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 parent reply other threads:[~2021-10-30 5:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-214875-208809@https.bugzilla.kernel.org/>
2021-10-30 5:49 ` bugzilla-daemon [this message]
2021-10-30 5:57 ` [Bug 214875] USB 3.1 device cannot be detected bugzilla-daemon
2021-12-11 11:33 ` bugzilla-daemon
2022-04-02 15:47 ` bugzilla-daemon
2022-05-30 5:34 ` bugzilla-daemon
2022-05-30 6:09 ` 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-214875-208809-xCkhRpLge6@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox