From: "Limonciello, Mario" <Mario.Limonciello@dell.com>
To: "Theodore Y. Ts'o" <tytso@mit.edu>
Cc: Greg KH <gregkh@linuxfoundation.org>,
Bastien Nocera <hadess@hadess.net>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Linux PM <linux-pm@vger.kernel.org>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
Hans de Goede <hdegoede@redhat.com>
Subject: RE: How to enable auto-suspend by default
Date: Tue, 10 Nov 2020 20:45:16 +0000 [thread overview]
Message-ID: <DM6PR19MB26360A123E3BFA4741853AF5FAE90@DM6PR19MB2636.namprd19.prod.outlook.com> (raw)
In-Reply-To: <20201110195536.GD2951190@mit.edu>
> One note... I'll double check, but on my XPS 13 9380, as I recall, I
> have to manually disable autosuspend on all of the XHCI controllers
> and internal hubs after running "powertop --auto-tune", or else any
> external mouse attached to said USB device will be dead to the world
> for 2-3 seconds if the autosuspend timeout has kicked in, which was
> ***super*** annoying.
>
> - Ted
Perhaps this was not XHCI controller in the system, but maybe external
one provided by ASMedia? I've not heard anything similar for host system
yet.
next prev parent reply other threads:[~2020-11-10 20:45 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-10 10:57 How to enable auto-suspend by default Bastien Nocera
2020-11-10 11:34 ` Greg KH
2020-11-10 16:02 ` Limonciello, Mario
2020-11-10 17:18 ` Greg KH
2020-11-10 17:45 ` Limonciello, Mario
2020-11-10 18:00 ` Greg KH
2020-11-10 18:08 ` Limonciello, Mario
2020-11-10 19:55 ` Theodore Y. Ts'o
2020-11-10 20:45 ` Limonciello, Mario [this message]
2020-11-10 17:25 ` Mika Westerberg
2020-11-11 11:27 ` Hans de Goede
2020-11-11 14:31 ` Mika Westerberg
2020-11-23 13:54 ` Hans de Goede
2020-11-23 14:01 ` Mika Westerberg
2020-11-24 12:37 ` Mathias Nyman
2020-11-24 12:38 ` Hans de Goede
2020-11-24 15:53 ` Bastien Nocera
2020-11-11 16:03 ` Limonciello, Mario
2020-11-11 16:32 ` Greg KH
2020-11-24 16:02 ` Bastien Nocera
2020-11-24 16:35 ` 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=DM6PR19MB26360A123E3BFA4741853AF5FAE90@DM6PR19MB2636.namprd19.prod.outlook.com \
--to=mario.limonciello@dell.com \
--cc=gregkh@linuxfoundation.org \
--cc=hadess@hadess.net \
--cc=hdegoede@redhat.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=tytso@mit.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).