From: Oliver Neukum <oneukum@suse.de>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Marcel Holtmann <marcel@holtmann.org>,
"Gustavo F. Padovan" <padovan@profusion.mobi>,
Alan Stern <stern@rowland.harvard.edu>,
"Greg Kroah-Hartman" <gregkh@suse.de>,
Jeff Chua <jeff.chua.linux@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: btusb autosuspend (was Re: Linux 2.6.38-rc6)
Date: Tue, 1 Mar 2011 11:22:13 +0100 [thread overview]
Message-ID: <201103011122.13759.oneukum@suse.de> (raw)
In-Reply-To: <20110224004333.GA22698@srcf.ucam.org>
Am Donnerstag, 24. Februar 2011, 01:43:33 schrieb Matthew Garrett:
> On Wed, Feb 23, 2011 at 04:25:23PM -0800, Linus Torvalds wrote:
> > It apparently had problems before too, and caused autosuspend to be
> > disabled entirely, judging at least by
> >
> > https://bugzilla.redhat.com/show_bug.cgi?id=528744
> >
> > but there's obviously the comment about "those should be fixed now".
> > Apparently there are more issues.
>
> Right, we were autosuspending even when there were active connections.
> Marcel told me that ought to be fixed and my testing seemed to agree...
It kind of negates any advantage of autosuspend while the device is actually
used. My tests showed that autosuspend on btusb either works well with
active connections or not at all.
> > I have no idea whether this is a USB-level issue, or a driver-level
> > one. There are no comments about exactly what fixed the input device
> > issues. So I'm adding both BT and USB people to the discussion.
>
> I'll try to get time to look at this this week. Marcel, any ideas?
Matthew, you can set the RESET_RESUME quirk for your test
device. If it works after that, it cansupport only a limited form
of autosuspend.
HTH
Oliver
next prev parent reply other threads:[~2011-03-01 10:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-24 0:25 btusb autosuspend (was Re: Linux 2.6.38-rc6) Linus Torvalds
2011-02-24 0:40 ` Greg KH
2011-02-24 0:43 ` Matthew Garrett
2011-02-24 14:55 ` Alan Stern
2011-03-01 10:22 ` Oliver Neukum [this message]
2011-02-24 2:42 ` Gustavo F. Padovan
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=201103011122.13759.oneukum@suse.de \
--to=oneukum@suse.de \
--cc=gregkh@suse.de \
--cc=jeff.chua.linux@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=mjg59@srcf.ucam.org \
--cc=padovan@profusion.mobi \
--cc=stern@rowland.harvard.edu \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox