public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Oliver Neukum <oliver@neukum.org>,
	Jean Delvare <khali@linux-fr.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: CONFIG_SUSPEND and power consumption
Date: Mon, 20 Aug 2007 22:19:10 +0200	[thread overview]
Message-ID: <20070820201910.GA5877@elf.ucw.cz> (raw)
In-Reply-To: <200708202108.35674.rjw@sisk.pl>

Hi!

> > > > If I rmmod "ehci-hcd" then the power consumption is back to 69 W. This
> > > > confirms that this is really USB-related. I have to admit that I did
> > > > not expect an external drive to eat that much power from the system,
> > > > especially when not used. I am told that VIA chips are notoriously bad
> > > > at this kind of things. I'll try the same external drive on an Intel
> > > > system later today.
> > > > 
> > > > The last mystery remaining is how USB "activity" can cause my CPU to
> > > > heat. I would expect the south bridge to heat, not the CPU.
> > > 
> > > USB, or strictly speaking EHCI, OHCI and UHCI, use DMA. To allow
> > > that the cache coherency logic has to be active. Therefore your CPU
> > > cannot go to C3. Therefore it draws more power. The problem we are
> > > facing in USB is that to get great savings, our coverage has to be perfect.
> > > One device that cannot be autosuspended and we lose most savings.
> > 
> > Ok.. but CONFIG_USB_SUSPEND should not really have anything to do with
> > CONFIG_SUSPEND (= s2ram). Perhaps it should depend on CONFIG_PM
> > instead?
> 
> CONFIG_USB_SUSPEND doesn't depend on CONFIG_SUSPEND.

Strange... what is going on here, then?

config USB_SUSPEND
        bool "USB selective suspend/resume and wakeup (EXPERIMENTAL)"
        depends on USB && PM && EXPERIMENTAL
        help
          If you say Y here, you can use driver calls or the sysfs
          "power/state" file to suspend or resume individual USB
          peripherals.

          Also, USB "remote wakeup" signaling is supported, whereby
some
          USB devices (like keyboards and network adapters) can wake
up
          their parent hub.  That wakeup cascades up the USB tree, and
          could wake the system from states like suspend-to-RAM.

          If you are unsure about this, say N here.

config USB_OTG
        bool
        depends on USB && EXPERIMENTAL
        select USB_SUSPEND
        default n

hmmm, it looks like USB_OTG can be selected without CONFIG_PM, but it
selects USB_SUSPEND. Is that okay?
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  reply	other threads:[~2007-08-20 20:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20070819153259.2c96b904@hyperion.delvare>
2007-08-19 20:42 ` CONFIG_SUSPEND and power consumption Rafael J. Wysocki
2007-08-20 10:02   ` Jean Delvare
2007-08-20 10:11     ` Oliver Neukum
2007-08-20 15:34       ` Jean Delvare
2007-08-20 17:29       ` Pavel Machek
2007-08-20 19:08         ` Rafael J. Wysocki
2007-08-20 20:19           ` Pavel Machek [this message]
2007-08-20 21:48             ` Rafael J. Wysocki

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=20070820201910.GA5877@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=khali@linux-fr.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oliver@neukum.org \
    --cc=rjw@sisk.pl \
    /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