public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: Andreas Mohr <andi@lisas.de>
Cc: Alan Stern <stern@rowland.harvard.edu>,
	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 12:00:45 -0700	[thread overview]
Message-ID: <20090915190045.GA734@suse.de> (raw)
In-Reply-To: <20090915185145.GA31490@rhlx01.hs-esslingen.de>

On Tue, Sep 15, 2009 at 08:51:45PM +0200, Andreas Mohr wrote:
> Hi,
> 
> currently running 2.6.31, and what I've been suspecting for quite some
> time (several weeks) is actually true: after S2R resume
> all friendly USB autosuspend settings are history and we're back
> to the dreaded old 100% activity (powertop -d):
> 
> Recent USB suspend statistics
> Active  Device name
> 100.0%  USB device  5-5 : Acer Crystal Eye webcam (SuYin)
> 100.0%  USB device usb5 : EHCI Host Controller (Linux 2.6.31 ehci_hcd)
>   0.0%  USB device usb4 : UHCI Host Controller (Linux 2.6.31 uhci_hcd)
>   0.0%  USB device usb3 : UHCI Host Controller (Linux 2.6.31 uhci_hcd)
>   0.0%  USB device usb2 : UHCI Host Controller (Linux 2.6.31 uhci_hcd)
>   0.0%  USB device usb1 : UHCI Host Controller (Linux 2.6.31 uhci_hcd)
> 
> Is there any fix planned for this? This is possibly even more important
> (power wasted due to wakeups, I'd judge it to be up to 1.5W on this 8.5W
> Aspire One machine) than any other runtime PM implementation...
> 
> OTOH this problem is probably isolated to uvc devices, since:
> # lsusb -t
> /:  Bus 05.Port 1: Dev 1, Class=root_hub, Driver=ehci_hcd/8p, 480M
>     |__ Port 5: Dev 7, If 0, Class='bInterfaceClass 0x0e not yet handled', Driver=uvcvideo, 480M
>     |__ Port 5: Dev 7, If 1, Class='bInterfaceClass 0x0e not yet handled', Driver=uvcvideo, 480M
> /:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
> /:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
> /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
> /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
> 
> So, does the uvc driver need a bit of handholding here?
> It likely shouldn't simply forget about its autosuspend status after
> resume...
> 
> Or would Matthew's uvc autosuspend patch
> http://osdir.com/ml/fedora-extras-commits/2009-07/msg06079.html

Could you try that?  A certian hardware manufacturer is insisting that
this patch solves problems, which I have not been able to validate, and
it would be good to get some independant tests.

thanks,

greg k-h

  reply	other threads:[~2009-09-15 19:08 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 [this message]
2009-09-15 19:10   ` Matthew Garrett
2009-09-15 19:48 ` Oliver Neukum
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=20090915190045.GA734@suse.de \
    --to=gregkh@suse.de \
    --cc=andi@lisas.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