public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Oliver Neukum <oliver@neukum.org>
To: Andreas Mohr <andi@lisas.de>
Cc: Alan Stern <stern@rowland.harvard.edu>,
	"Greg Kroah-Hartman" <gregkh@suse.de>,
	laurent.pinchart@skynet.be, Matthew Garrett <mjg59@srcf.ucam.org>,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: usb autosuspend is history after S2R (also on 2.6.31; UVC?)
Date: Tue, 15 Sep 2009 21:48:28 +0200	[thread overview]
Message-ID: <200909152148.29662.oliver@neukum.org> (raw)
In-Reply-To: <20090915185145.GA31490@rhlx01.hs-esslingen.de>

Am Dienstag, 15. September 2009 20:51:45 schrieb Andreas Mohr:

> So, does the uvc driver need a bit of handholding here?
> It likely shouldn't simply forget about its autosuspend status after
> resume...

Can you please provide what you get when you read the "level" file
of the device's power directory?

Secondly, please verify, that it works before the STR cycle and post
a syslog of a suspend/resume cycle with CONFIG_USB_DEBUG and
only this device attached if possible. Thirdly, please verify that only
uvc is affected.

> Or would Matthew's uvc autosuspend patch
> http://osdir.com/ml/fedora-extras-commits/2009-07/msg06079.html
> help here?

Please test it. It shouldn't work, but if it works there's a fundamental
flaw.

	Regards
		Oliver


  parent reply	other threads:[~2009-09-15 19:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-15 18:51 usb autosuspend is history after S2R (also on 2.6.31; UVC?) Andreas Mohr
2009-09-15 19:00 ` Greg KH
2009-09-15 19:10   ` Matthew Garrett
2009-09-15 19:48 ` Oliver Neukum [this message]
2009-09-16 18:19   ` Andreas Mohr
2009-09-16 19:51     ` Francois Romieu
2009-09-16 19:54       ` Andreas Mohr
2009-09-16 20:43         ` Francois Romieu

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=200909152148.29662.oliver@neukum.org \
    --to=oliver@neukum.org \
    --cc=andi@lisas.de \
    --cc=gregkh@suse.de \
    --cc=laurent.pinchart@skynet.be \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mjg59@srcf.ucam.org \
    --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