public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthew Garrett <mjg59@srcf.ucam.org>
To: "Jeffrey W. Baker" <jwbaker@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Put unused PCI devices in D3
Date: Tue, 30 Sep 2008 02:06:13 +0100	[thread overview]
Message-ID: <20080930010613.GA30375@srcf.ucam.org> (raw)
In-Reply-To: <1222736147.21516.12.camel@stinkpad>

On Mon, Sep 29, 2008 at 05:55:47PM -0700, Jeffrey W. Baker wrote:

> No, you couldn't, but that isn't really the point.  If I have my laptop
> on a transoceanic flight it may be useful for me to be able to set a
> power policy turning off all the extraneous junk on my machine, because
> I know /a priori/ that no hotplug events will happen.  There's no way
> the kernel could know that, but userspace can tell the kernel to turn
> off an unneeded device.

The majority (though it's not universal) of modern hardware can be put 
into a state where you get most of the power savings of the entire part 
being in D3 but with little functional regression. While I'm not averse 
to adding features that aid the power user who's happy to poke around 
with individual drivers, this shouldn't be at the expense of 
implementing good runtime power management for the more common case.

Not that I'm suggesting you're doing that, I just want to emphasise that 
you're working on a slightly more niche concern :)
-- 
Matthew Garrett | mjg59@srcf.ucam.org

  reply	other threads:[~2008-09-30  1:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-29 20:11 Put unused PCI devices in D3 Jeffrey W. Baker
2008-09-30  0:09 ` Matthew Garrett
2008-09-30  0:55   ` Jeffrey W. Baker
2008-09-30  1:06     ` Matthew Garrett [this message]
2008-10-03 19:40     ` Pavel Machek
2008-10-03 19:37 ` 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=20080930010613.GA30375@srcf.ucam.org \
    --to=mjg59@srcf.ucam.org \
    --cc=jwbaker@gmail.com \
    --cc=linux-kernel@vger.kernel.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