From: Mathias Nyman <mathias.nyman@linux.intel.com>
To: Oliver Neukum <oneukum@suse.com>,
Kai-Heng Feng <kai.heng.feng@canonical.com>,
mathias.nyman@intel.com
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] xhci: Disable connect, disconnect and over-current wakeup on system suspend
Date: Thu, 17 Aug 2023 15:53:17 +0300 [thread overview]
Message-ID: <ef189a18-98ba-52c9-13a3-ce8531fc18cf@linux.intel.com> (raw)
In-Reply-To: <cc271e17-6204-b610-b40e-5c882ad6be36@suse.com>
On 17.8.2023 14.18, Oliver Neukum wrote:
> On 17.08.23 11:33, Kai-Heng Feng wrote:
>
> Hi,
>
>> So for system-wide suspend, also disable connect, disconnect and
>> over-current wakeup to prevent spurious wakeup.
>
> isn't this breaking the ability to effectively use your root hub
> as a source of system wakeups? That is, even if you want the
> system to wake up if somebody attaches a new device, it no longer works?
>
I got the same concern about this.
-Mathias
next prev parent reply other threads:[~2023-08-17 12:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-17 9:33 [PATCH] xhci: Disable connect, disconnect and over-current wakeup on system suspend Kai-Heng Feng
2023-08-17 11:18 ` Oliver Neukum
2023-08-17 12:53 ` Mathias Nyman [this message]
2023-08-17 13:13 ` Kai-Heng Feng
2023-08-17 14:03 ` Alan Stern
2023-08-17 23:49 ` Kai-Heng Feng
2023-08-17 14:07 ` Alan Stern
2023-08-17 14:22 ` Alan Stern
2023-08-18 0:01 ` Kai-Heng Feng
2023-08-18 3:08 ` Alan Stern
2023-08-18 14:12 ` Kai-Heng Feng
2023-08-18 15:02 ` Alan Stern
2023-08-18 0:00 ` Kai-Heng Feng
2023-08-18 3:19 ` Alan Stern
2023-08-18 14:19 ` Kai-Heng Feng
2023-08-18 15:20 ` Alan Stern
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=ef189a18-98ba-52c9-13a3-ce8531fc18cf@linux.intel.com \
--to=mathias.nyman@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=kai.heng.feng@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@intel.com \
--cc=oneukum@suse.com \
/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