From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Alan Stern <stern@rowland.harvard.edu>,
Linux PM mailing list <linux-pm@lists.linux-foundation.org>,
linux-omap@vger.kernel.org, Jean Pihet <j-pihet@ti.com>,
markgross@thegnar.org
Subject: Re: [linux-pm] [PATCH 02/11] PM: extend PM QoS with per-device wake-up constraints
Date: Thu, 25 Aug 2011 11:38:48 +0100 [thread overview]
Message-ID: <20110825103847.GD31154@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <201108232331.54844.rjw@sisk.pl>
On Tue, Aug 23, 2011 at 11:31:54PM +0200, Rafael J. Wysocki wrote:
> Perhaps. Still, that requires some policy to be put into drivers,
> which I don't think is entirely correct.
So, I don't really have the bandwidth to discuss this properly for at
least the next week or so - is it possible to find some time in the
power track at LPC for this?
next prev parent reply other threads:[~2011-08-25 10:38 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-30 15:11 [PATCH v2 00/11] PM QoS: add a per-device wake-up latency constraint class jean.pihet
2011-06-30 15:11 ` [PATCH 01/11] PM: add a per-device wake-up latency constraints plist jean.pihet
2011-07-02 19:39 ` Rafael J. Wysocki
2011-07-20 8:57 ` Jean Pihet
2011-06-30 15:11 ` [PATCH 02/11] PM: extend PM QoS with per-device wake-up constraints jean.pihet
2011-07-02 21:10 ` Rafael J. Wysocki
2011-07-20 9:13 ` Jean Pihet
2011-08-02 17:49 ` Kevin Hilman
2011-08-02 20:19 ` Rafael J. Wysocki
2011-08-02 21:23 ` Kevin Hilman
2011-08-02 22:16 ` Rafael J. Wysocki
2011-08-04 13:24 ` [linux-pm] " Mark Brown
2011-08-04 19:15 ` Rafael J. Wysocki
2011-08-05 15:29 ` mark gross
2011-08-05 16:11 ` Mark Brown
2011-08-05 19:37 ` Rafael J. Wysocki
2011-08-06 3:37 ` Mark Brown
2011-08-06 19:46 ` Rafael J. Wysocki
2011-08-07 2:47 ` [linux-pm] " Mark Brown
2011-08-08 21:31 ` Rafael J. Wysocki
2011-08-19 3:11 ` Mark Brown
2011-08-19 20:42 ` Rafael J. Wysocki
2011-08-19 23:14 ` Mark Brown
2011-08-20 2:24 ` Alan Stern
2011-08-20 6:25 ` Mark Brown
2011-08-20 13:48 ` Alan Stern
2011-08-20 15:30 ` Mark Brown
2011-08-20 16:34 ` Rafael J. Wysocki
2011-08-20 17:04 ` Mark Brown
2011-08-20 19:14 ` Rafael J. Wysocki
2011-08-21 8:25 ` Mark Brown
2011-08-21 18:05 ` Rafael J. Wysocki
2011-08-23 9:21 ` Mark Brown
2011-08-23 21:31 ` Rafael J. Wysocki
2011-08-25 10:38 ` Mark Brown [this message]
2011-08-25 14:17 ` Rafael J. Wysocki
2011-08-25 14:41 ` Jean Pihet
2011-08-25 14:49 ` Rafael J. Wysocki
2011-08-26 16:40 ` mark gross
2011-08-20 9:35 ` Rafael J. Wysocki
2011-08-20 10:31 ` Mark Brown
2011-08-20 16:51 ` Rafael J. Wysocki
2011-08-20 17:22 ` Mark Brown
2011-08-20 19:18 ` Rafael J. Wysocki
2011-08-26 2:25 ` MyungJoo Ham
2011-08-26 16:54 ` mark gross
2011-08-26 20:56 ` Rafael J. Wysocki
2011-06-30 15:11 ` [PATCH 03/11] PM QoS: support the dynamic devices insertion and removal jean.pihet
2011-07-02 21:14 ` Rafael J. Wysocki
2011-07-20 9:16 ` Jean Pihet
2011-06-30 15:11 ` [PATCH 04/11] OMAP PM: create a PM layer plugin for per-device constraints jean.pihet
2011-06-30 15:11 ` [PATCH 05/11] OMAP PM: early init of the pwrdms states jean.pihet
2011-06-30 15:11 ` [PATCH 06/11] OMAP2+: powerdomain: control power domains next state jean.pihet
2011-06-30 15:11 ` [PATCH 07/11] OMAP3: powerdomain data: add wake-up latency figures jean.pihet
2011-06-30 15:11 ` [PATCH 08/11] OMAP4: " jean.pihet
2011-06-30 15:11 ` [PATCH 09/11] OMAP2+: omap_hwmod: manage the wake-up latency constraints jean.pihet
2011-06-30 15:11 ` [PATCH 10/11] OMAP: PM CONSTRAINTS: implement the devices " jean.pihet
2011-06-30 15:11 ` [PATCH 11/11] OMAP2+: cpuidle only influences the MPU state jean.pihet
2011-07-02 19:20 ` [PATCH v2 00/11] PM QoS: add a per-device wake-up latency constraint class Rafael J. Wysocki
2011-07-04 7:16 ` Vishwanath Sripathy
2011-07-04 8:38 ` Rafael J. Wysocki
2011-07-20 9:26 ` Jean Pihet
2011-07-20 13:22 ` mark gross
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=20110825103847.GD31154@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=j-pihet@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=markgross@thegnar.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;
as well as URLs for NNTP newsgroup(s).