From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: Greg KH <gregkh@suse.de>,
linux-pci@vger.kernel.org, linux-usb@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
Linux-pm mailing list <linux-pm@lists.linux-foundation.org>
Subject: Re: [RFC] PCI: Runtime power management
Date: Sat, 15 Aug 2009 23:21:53 +0200 [thread overview]
Message-ID: <200908152321.53283.rjw@sisk.pl> (raw)
In-Reply-To: <20090815205817.GA30254@srcf.ucam.org>
On Saturday 15 August 2009, Matthew Garrett wrote:
> On Sat, Aug 15, 2009 at 10:54:23PM +0200, Rafael J. Wysocki wrote:
>
> > runtime_wakeup - if set, the device is allowed to do remote wakeup at run time
> > That could be represented as 'runtime_wakeup' under 'power' with the
> > following values:
> > * no value (empty file) is 'runtime' is 'disabled'
> > * 'enabled'
> > * 'disabled'
> > To set/unset the user space writes 'enabled'/'disabled' to it, respectively.
> > The default is set.
>
> Why would you ever want runtime_wakeup to be false unless
> runtime_forbidden is true? Surely the point of runtime power management
> is to be transparent to the user, in which case remote wakeup is
> required?
Well, this was exactly my point previously. :-)
Still, although for the majority of devices 'runtime_wakeup' disabled would
mean no runtime PM at all IMO, there may be devices that actually work without
remote wakeup, although they support it in general.
I can even imagine a scenario where this setting might be useful, like when
we don't want a network adapter to be woken up from the outside.
Thanks,
Rafael
next prev parent reply other threads:[~2009-08-15 21:21 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.44L0.0908151143560.18415-100000@netrider.rowland.org>
2009-08-15 20:54 ` [RFC] PCI: Runtime power management Rafael J. Wysocki
[not found] ` <200908152254.23227.rjw@sisk.pl>
2009-08-15 20:58 ` Matthew Garrett
[not found] ` <20090815205817.GA30254@srcf.ucam.org>
2009-08-15 21:21 ` Rafael J. Wysocki [this message]
2009-08-15 21:27 ` Matthew Garrett
[not found] ` <20090815212756.GA31784@srcf.ucam.org>
2009-08-15 21:44 ` Rafael J. Wysocki
2009-08-16 15:57 ` Alan Stern
[not found] ` <Pine.LNX.4.44L0.0908161151020.6522-100000@netrider.rowland.org>
2009-08-16 16:04 ` Matthew Garrett
2009-08-16 15:50 ` Alan Stern
[not found] <200908152344.46898.rjw@sisk.pl>
2009-08-16 16:09 ` Alan Stern
[not found] <200908151618.10169.rjw@sisk.pl>
2009-08-15 15:53 ` Alan Stern
[not found] <Pine.LNX.4.44L0.0908141032070.2987-100000@iolanthe.rowland.org>
2009-08-14 17:05 ` Rafael J. Wysocki
[not found] ` <200908141905.32766.rjw@sisk.pl>
2009-08-14 17:13 ` Rafael J. Wysocki
2009-08-14 20:05 ` Rafael J. Wysocki
[not found] ` <200908142205.20093.rjw@sisk.pl>
2009-08-14 22:21 ` Matthew Garrett
[not found] ` <20090814222157.GA20015@srcf.ucam.org>
2009-08-15 14:18 ` Rafael J. Wysocki
[not found] <200908141913.56884.rjw@sisk.pl>
2009-08-14 19:01 ` Alan Stern
[not found] <20090814123059.GA27995@srcf.ucam.org>
2009-08-14 14:43 ` Alan Stern
[not found] <200908081625.57333.rjw@sisk.pl>
[not found] ` <200908092313.05541.rjw@sisk.pl>
2009-08-13 0:29 ` Matthew Garrett
[not found] ` <20090813002925.GA2532@srcf.ucam.org>
2009-08-13 15:17 ` Alan Stern
[not found] ` <Pine.LNX.4.44L0.0908131100440.2940-100000@iolanthe.rowland.org>
2009-08-13 21:47 ` Matthew Garrett
[not found] ` <20090813214701.GC14532@srcf.ucam.org>
2009-08-14 12:30 ` Matthew Garrett
2009-08-14 17:37 ` Jesse Barnes
[not found] ` <20090814103719.79e99d91@jbarnes-g45>
2009-08-14 19:15 ` Rafael J. Wysocki
2009-08-14 21:22 ` Rafael J. Wysocki
[not found] ` <200908142322.27544.rjw@sisk.pl>
2009-08-14 22:30 ` Matthew Garrett
[not found] ` <20090814223013.GB20015@srcf.ucam.org>
2009-08-15 14:41 ` Rafael J. Wysocki
[not found] ` <200908151641.56571.rjw@sisk.pl>
2009-08-15 15:24 ` 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=200908152321.53283.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=linux-usb@vger.kernel.org \
--cc=mjg59@srcf.ucam.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