public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Oliver Neukum <oliver@neukum.org>
Cc: Alan Stern <stern@rowland.harvard.edu>,
	USB list <linux-usb@vger.kernel.org>,
	kernel list <linux-kernel@vger.kernel.org>,
	marcel@holtmann.org, linux-bluetooth@vger.kernel.org,
	"Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: -rc6: something (probably active usb bluetooth) blocks suspend
Date: Wed, 18 Nov 2009 18:22:11 +0100	[thread overview]
Message-ID: <20091118172211.GC25150@elf.ucw.cz> (raw)
In-Reply-To: <200911161447.51651.oliver@neukum.org>

Hi!

> > > Why is the device autoresumed here? Are you using autosuspend?
> > > This is odd, as the freezer should block the send path and remote
> > > wakeups should be deferred.
> > 
> > I believe I have it enabled in kconfig but not during runtime.
> 
> Please check.

CONFIG_USB_SUSPEND=y

I'm not aware of  boot scripts enabling anything.

> > (Another problem is that I need to turn the kill switch on/off to get
> > my bt usb after resume. That used not be the case long time ago.)
> 
> That is possibly another problem.

Yes, I guess so. With those many USB experts around, I thought I'd
mention it :-).
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  parent reply	other threads:[~2009-11-18 17:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-16 11:22 -rc6: something (probably active usb bluetooth) blocks suspend Pavel Machek
2009-11-16 11:48 ` Oliver Neukum
2009-11-14 11:10   ` Pavel Machek
2009-11-16 13:47     ` Oliver Neukum
2009-11-16 16:05       ` Alan Stern
2009-11-18 17:22       ` Pavel Machek [this message]
2009-11-16 13:43 ` Oliver Neukum
2009-11-16 14:22   ` Pavel Machek
2009-11-18 17:18   ` Pavel Machek

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=20091118172211.GC25150@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=marcel@holtmann.org \
    --cc=oliver@neukum.org \
    --cc=rjw@sisk.pl \
    --cc=stern@rowland.harvard.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