Linux bluetooth development
 help / color / mirror / Atom feed
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 13:39:49 +0100	[thread overview]
Message-ID: <20170228123949.GA32116@kroah.com> (raw)
In-Reply-To: <6fdd4378-fd7b-497f-6c1e-3681020bcd49@molgen.mpg.de>

On Tue, Feb 28, 2017 at 12:06:38PM +0100, Paul Menzel wrote:
> Dear Greg,
> 
> 
> On 02/28/17 12:00, Greg KH wrote:
> > 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?
> 
> Sorry, for being ambiguous. I don’t know if there are Google Chromebooks
> using that USB device, and I wouldn’t have access to it.

Then perhaps the hardware itself just can't do this type of "quick"
suspend/resume?  Have you tried it in MacBook and measured it there?

> I just meant, that it would be great to get fast resume times.

I agree, but sometimes hardware just sucks :)

thanks,

greg k-h

  reply	other threads:[~2017-02-28 12:39 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
2017-02-28 11:06   ` Paul Menzel
2017-02-28 12:39     ` Greg KH [this message]
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=20170228123949.GA32116@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