From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 216706] New: USBC resume callback takes far too long, between 650ms and 1200ms
Date: Fri, 18 Nov 2022 20:24:14 +0000 [thread overview]
Message-ID: <bug-216706-208809@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=216706
Bug ID: 216706
Summary: USBC resume callback takes far too long, between 650ms
and 1200ms
Product: Drivers
Version: 2.5
Kernel Version: 6.1.0-rc2
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: USB
Assignee: drivers_usb@kernel-bugs.kernel.org
Reporter: todd.e.brandt@intel.com
Blocks: 178231
Regression: No
Created attachment 303218
--> https://bugzilla.kernel.org/attachment.cgi?id=303218&action=edit
lenb-Dell-XPS-13-9310_freeze.html
The new USBC resume callback is taking far too long in the resume phase. I
bisected the behavior to this commit:
[10402] 4e3a50293c2b21961f02e1afa2f17d3a1a90c7c8 is the first bad commit
[10402] commit 4e3a50293c2b21961f02e1afa2f17d3a1a90c7c8
[10402] Author: Heikki Krogerus <heikki.krogerus@linux.intel.com>
[10402] Date: Fri Oct 7 13:09:51 2022 +0300
[10402]
[10402] usb: typec: ucsi: acpi: Implement resume callback
[10402]
[10402] The ACPI driver needs to resume the interface by calling
[10402] ucsi_resume(). Otherwise we may fail to detect connections
[10402] and disconnections that happen while the system is
[10402] suspended.
[10402]
[10402] Link: https://bugzilla.kernel.org/show_bug.cgi?id=210425
[10402] Fixes: a94ecde41f7e ("usb: typec: ucsi: ccg: enable runtime pm
support")
[10402] Cc: <stable@vger.kernel.org>
[10402] Signed-off-by: Heikki Krogerus <heikki.krogerus@linux.intel.com>
[10402] Link:
https://lore.kernel.org/r/20221007100951.43798-3-heikki.krogerus@linux.intel.com
[10402] Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
I have timelines from 7 separate machines that are now affected but this
behavior. We have a guidline that neither suspend or resume should take longer
than a second, and this is causing us problems.
Referenced Bugs:
https://bugzilla.kernel.org/show_bug.cgi?id=178231
[Bug 178231] Meta-bug: Linux suspend-to-mem and freeze performance optimization
--
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 reply other threads:[~2022-11-18 20:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-18 20:24 bugzilla-daemon [this message]
2022-11-18 20:24 ` [Bug 216706] USBC resume callback takes far too long, between 650ms and 1200ms bugzilla-daemon
2022-11-18 20:25 ` bugzilla-daemon
2022-11-18 20:25 ` bugzilla-daemon
2022-11-18 20:26 ` bugzilla-daemon
2022-11-18 20:26 ` bugzilla-daemon
2022-11-18 20:26 ` bugzilla-daemon
2022-11-19 8:53 ` [Bug 216706] New: " 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=bug-216706-208809@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 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.