From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: Alan Stern <stern@rowland.harvard.edu>,
linux-usb@vger.kernel.org, linux-pci@vger.kernel.org,
Greg KH <gregkh@suse.de>, LKML <linux-kernel@vger.kernel.org>,
"Linux-pm mailing list" <linux-pm@lists.linux-foundation.org>
Subject: Re: [linux-pm] [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
WARNING: multiple messages have this Message-ID (diff)
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: 89+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-08 14:25 [PATCH] PM: Introduce core framework for run-time PM of I/O devices (rev. 14) Rafael J. Wysocki
2009-08-09 21:13 ` [PATCH update] PM: Introduce core framework for run-time PM of I/O devices (rev. 15) Rafael J. Wysocki
2009-08-09 21:13 ` Rafael J. Wysocki
2009-08-12 10:37 ` Magnus Damm
2009-08-12 15:47 ` Alan Stern
2009-08-12 15:47 ` Alan Stern
2009-08-12 20:13 ` Rafael J. Wysocki
2009-08-12 20:13 ` Rafael J. Wysocki
2009-08-12 10:37 ` Magnus Damm
2009-08-13 0:29 ` [RFC] PCI: Runtime power management Matthew Garrett
2009-08-13 0:29 ` Matthew Garrett
2009-08-13 0:35 ` [RFC] usb: Add support for runtime power management of the hcd Matthew Garrett
2009-08-13 12:16 ` Oliver Neukum
2009-08-13 12:16 ` [linux-pm] " Oliver Neukum
2009-08-13 12:30 ` Matthew Garrett
2009-08-13 12:30 ` [linux-pm] " Matthew Garrett
2009-08-13 14:26 ` Oliver Neukum
2009-08-13 14:26 ` [linux-pm] " Oliver Neukum
2009-08-13 21:42 ` Matthew Garrett
2009-08-13 21:42 ` Matthew Garrett
2009-08-13 15:22 ` Alan Stern
2009-08-13 15:22 ` Alan Stern
2009-08-13 21:47 ` Matthew Garrett
2009-08-13 21:47 ` Matthew Garrett
2009-08-13 0:35 ` Matthew Garrett
2009-08-13 15:17 ` [RFC] PCI: Runtime power management Alan Stern
2009-08-13 21:47 ` Matthew Garrett
2009-08-14 12:30 ` Matthew Garrett
2009-08-14 12:30 ` [linux-pm] " Matthew Garrett
2009-08-14 14:43 ` Alan Stern
2009-08-14 14:43 ` [linux-pm] " Alan Stern
2009-08-14 17:05 ` Rafael J. Wysocki
2009-08-14 17:05 ` [linux-pm] " Rafael J. Wysocki
2009-08-14 17:13 ` Rafael J. Wysocki
2009-08-14 17:13 ` [linux-pm] " Rafael J. Wysocki
2009-08-14 19:01 ` Alan Stern
2009-08-14 19:01 ` Alan Stern
2009-08-14 20:05 ` [linux-pm] " Rafael J. Wysocki
2009-08-14 22:21 ` Matthew Garrett
2009-08-15 14:18 ` Rafael J. Wysocki
2009-08-15 14:18 ` [linux-pm] " Rafael J. Wysocki
2009-08-15 15:53 ` Alan Stern
2009-08-15 15:53 ` [linux-pm] " Alan Stern
2009-08-15 20:54 ` Rafael J. Wysocki
2009-08-15 20:54 ` [linux-pm] " Rafael J. Wysocki
2009-08-15 20:58 ` Matthew Garrett
2009-08-15 20:58 ` [linux-pm] " Matthew Garrett
2009-08-15 21:21 ` Rafael J. Wysocki [this message]
2009-08-15 21:21 ` Rafael J. Wysocki
2009-08-15 21:27 ` [linux-pm] " Matthew Garrett
2009-08-15 21:44 ` Rafael J. Wysocki
2009-08-15 21:44 ` [linux-pm] " Rafael J. Wysocki
2009-08-16 16:09 ` Alan Stern
2009-08-16 16:09 ` Alan Stern
2009-08-15 21:27 ` Matthew Garrett
2009-08-16 15:57 ` Alan Stern
2009-08-16 15:57 ` [linux-pm] " Alan Stern
2009-08-16 16:04 ` Matthew Garrett
2009-08-16 16:04 ` [linux-pm] " Matthew Garrett
2009-08-16 15:50 ` Alan Stern
2009-08-16 15:50 ` [linux-pm] " Alan Stern
2009-08-14 22:21 ` Matthew Garrett
2009-08-14 20:05 ` Rafael J. Wysocki
2009-08-13 21:47 ` Matthew Garrett
2009-08-13 15:17 ` Alan Stern
2009-08-14 17:37 ` Jesse Barnes
2009-08-14 17:37 ` Jesse Barnes
2009-08-14 19:15 ` Rafael J. Wysocki
2009-08-14 19:15 ` Rafael J. Wysocki
2009-08-14 21:22 ` Rafael J. Wysocki
2009-08-14 22:30 ` Matthew Garrett
2009-08-14 22:30 ` Matthew Garrett
2009-08-15 14:41 ` Rafael J. Wysocki
2009-08-15 15:24 ` Rafael J. Wysocki
2009-08-15 15:24 ` Rafael J. Wysocki
2009-08-15 14:41 ` Rafael J. Wysocki
2009-08-14 21:22 ` Rafael J. Wysocki
2009-08-13 20:56 ` [PATCH update 2x] PM: Introduce core framework for run-time PM of I/O devices (rev. 16) Rafael J. Wysocki
2009-08-13 21:03 ` Paul Mundt
2009-08-13 21:03 ` Paul Mundt
2009-08-13 21:14 ` Rafael J. Wysocki
2009-08-13 21:14 ` Rafael J. Wysocki
2009-08-14 9:08 ` Magnus Damm
2009-08-14 17:19 ` Rafael J. Wysocki
2009-08-14 17:19 ` Rafael J. Wysocki
2009-08-14 9:08 ` Magnus Damm
2009-08-14 17:25 ` [PATCH update 3x] PM: Introduce core framework for run-time PM of I/O devices (rev. 17) Rafael J. Wysocki
2009-08-14 17:25 ` Rafael J. Wysocki
2009-08-13 20:56 ` [PATCH update 2x] PM: Introduce core framework for run-time PM of I/O devices (rev. 16) 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 \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.