From: Oliver Neukum <oliver@neukum.org>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: Alan Stern <stern@rowland.harvard.edu>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
linux-acpi@vger.kernel.org, USB list <linux-usb@vger.kernel.org>
Subject: Re: [PATCH] usb: Add support for runtime power management of the hcd
Date: Thu, 12 Nov 2009 08:41:11 +0100 [thread overview]
Message-ID: <200911120841.11263.oliver@neukum.org> (raw)
In-Reply-To: <20091112003312.GA27572@srcf.ucam.org>
Am Donnerstag, 12. November 2009 01:33:12 schrieb Matthew Garrett:
> On Wed, Nov 11, 2009 at 06:09:24PM -0500, Alan Stern wrote:
> > That's okay. There's no harm in trying to enable remote wakeup on a
> > device which doesn't support it.
>
> There's harm if we're using the ability to generate remote waleups as a
> condition for whether we can perform runtime pm on the device...
That I would consider backwards. If the user enables runtime power management
of a device, he has to live with remote wakeup being enabled. At most
the kernel might resume and switch off remote wakeup on the device,
but we might also leave this to user space.
Regards
Oliver
next prev parent reply other threads:[~2009-11-12 7:38 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-09 22:43 [PATCH] usb: Add support for runtime power management of the hcd Matthew Garrett
2009-11-10 8:20 ` Oliver Neukum
[not found] ` <200911100920.03361.oliver-GvhC2dPhHPQdnm+yROfE0A@public.gmane.org>
2009-11-10 12:41 ` Matthew Garrett
[not found] ` <20091110124109.GA18631-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org>
2009-11-10 13:08 ` Oliver Neukum
[not found] ` <200911101408.01867.oliver-GvhC2dPhHPQdnm+yROfE0A@public.gmane.org>
2009-11-10 14:12 ` Matthew Garrett
[not found] ` <20091110141259.GA19792-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org>
2009-11-10 15:04 ` Alan Stern
[not found] ` <Pine.LNX.4.44L0.0911100949500.2888-100000-IYeN2dnnYyZXsRXLowluHWD2FQJk+8+b@public.gmane.org>
2009-11-11 11:34 ` Oliver Neukum
[not found] ` <200911111234.43867.oliver-GvhC2dPhHPQdnm+yROfE0A@public.gmane.org>
2009-11-11 17:08 ` Alan Stern
2009-11-11 17:27 ` Oliver Neukum
2009-11-11 19:06 ` Alan Stern
[not found] ` <Pine.LNX.4.44L0.0911111400370.6882-100000-pYrvlCTfrz9XsRXLowluHWD2FQJk+8+b@public.gmane.org>
2009-11-11 22:24 ` Rafael J. Wysocki
2009-11-11 23:09 ` Alan Stern
2009-11-12 0:33 ` Matthew Garrett
2009-11-12 7:41 ` Oliver Neukum [this message]
2009-11-12 14:51 ` Matthew Garrett
2009-11-12 16:50 ` Alan Stern
[not found] ` <20091112145121.GB6709-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org>
2009-11-12 17:00 ` Oliver Neukum
2009-11-12 16:59 ` Matthew Garrett
[not found] ` <20091112165958.GA9389-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org>
2009-11-16 21:26 ` Oliver Neukum
2009-11-16 22:26 ` Rafael J. Wysocki
[not found] ` <20091112003312.GA27572-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org>
2009-11-12 16:22 ` Alan Stern
2009-11-12 14:44 ` Oliver Neukum
[not found] ` <200911121544.19313.oliver-GvhC2dPhHPQdnm+yROfE0A@public.gmane.org>
2009-11-12 16:47 ` Alan Stern
2009-11-12 10:31 ` Oliver Neukum
2009-11-12 14:50 ` Matthew Garrett
2009-11-11 22:15 ` Rafael J. Wysocki
2009-11-11 23:05 ` Alan Stern
2009-11-11 21:36 ` 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=200911120841.11263.oliver@neukum.org \
--to=oliver@neukum.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
--cc=rjw@sisk.pl \
--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