From: Greg KH <greg@kroah.com>
To: Paul Menzel <pmenzel@molgen.mpg.de>
Cc: Marcel Holtmann <marcel@holtmann.org>,
Gustavo Padovan <gustavo@padovan.org>,
Johan Hedberg <johan.hedberg@gmail.com>,
linux-bluetooth@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: Decrease long resume time of Intel Bluetooth module
Date: Tue, 28 Feb 2017 12:00:17 +0100 [thread overview]
Message-ID: <20170228110017.GA30523@kroah.com> (raw)
In-Reply-To: <9dbb0c55-4aeb-633e-a4f8-ca3fa170e19b@molgen.mpg.de>
On Tue, Feb 28, 2017 at 11:20:11AM +0100, Paul Menzel wrote:
> Is there a way to debug and optimize that – besides taking the device out –
> to get resume times on par with other devices like Google Chromebooks or
> Apple MacBooks?
A Chromebook is running the same Linux kernel as your desktop, so
perhaps you can see if it really is doing something different here or
not?
thanks,
greg k-h
next prev parent reply other threads:[~2017-02-28 11:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-28 10:20 Decrease long resume time of Intel Bluetooth module Paul Menzel
2017-02-28 11:00 ` Greg KH [this message]
2017-02-28 11:06 ` Paul Menzel
2017-02-28 12:39 ` Greg KH
2017-02-28 12:46 ` Paul Menzel
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=20170228110017.GA30523@kroah.com \
--to=greg@kroah.com \
--cc=gustavo@padovan.org \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=pmenzel@molgen.mpg.de \
/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