From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Jean Pihet <jean.pihet@newoldbits.com>
Cc: Linux PM mailing list <linux-pm@lists.linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
"Linux-sh list" <linux-sh@vger.kernel.org>,
Magnus Damm <magnus.damm@gmail.com>,
Kevin Hilman <khilman@ti.com>
Subject: Re: [RFC][PATCH 5/5] PM / Domains: Add default power off governor function
Date: Fri, 2 Sep 2011 00:11:12 +0200 [thread overview]
Message-ID: <201109020011.12264.rjw@sisk.pl> (raw)
In-Reply-To: <CAORVsuW7rFEN8u7RCpmWJamtG2iUbA_zz3ax4hgBjGAZW9vU=A@mail.gmail.com>
Hi,
On Thursday, September 01, 2011, Jean Pihet wrote:
> Rafael,
>
> On Wed, Aug 31, 2011 at 12:22 AM, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> > From: Rafael J. Wysocki <rjw@sisk.pl>
> >
> > Add a function deciding whether or not a given PM domain should
> > be powered off on the basis of that domain's devices' PM QoS
> > constraints.
> >
> > ---
> > drivers/base/power/domain_governor.c | 96 +++++++++++++++++++++++++++++++++++
> > include/linux/pm_domain.h | 7 ++
> > 2 files changed, 103 insertions(+)
> >
> > Index: linux/include/linux/pm_domain.h
> > ===================================================================
> > --- linux.orig/include/linux/pm_domain.h
> > +++ linux/include/linux/pm_domain.h
> > @@ -49,6 +49,10 @@ struct generic_pm_domain {
> > int (*start_device)(struct device *dev);
> > int (*stop_device)(struct device *dev);
> > bool (*active_wakeup)(struct device *dev);
> > + ktime_t power_off_latency;
> > + ktime_t power_on_latency;
> > + s64 break_even_ns;
> > + s64 min_delta_ns;
> How are those values populated?
I'm not sure. There are a few possible ways to do that, but I simply
don't know which one is going to be the most useful. That's one of
the reasons why patches [4-5/5] are RFCs.
> Is there a mechanism that dynamically updates the values?
Obviously not at the moment.
Thanks,
Rafael
next prev parent reply other threads:[~2011-09-01 22:09 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-30 22:17 [PATCH 0/5] PM: Generic PM domains and device PM QoS Rafael J. Wysocki
2011-08-30 22:18 ` [PATCH 1/5] PM / Domains: Split device PM domain data into base and need_restore Rafael J. Wysocki
2011-08-30 22:20 ` [PATCH 2/5] PM / Runtime: Do not run callbacks under lock for power.irq_safe set Rafael J. Wysocki
2011-09-12 8:26 ` Ming Lei
2011-09-12 21:52 ` Rafael J. Wysocki
[not found] ` <201109122344.02386.rjw@sisk.pl>
2011-09-13 1:22 ` Ming Lei
2011-09-13 16:06 ` Rafael J. Wysocki
2011-09-14 1:12 ` Ming Lei
2011-09-14 20:45 ` Rafael J. Wysocki
2011-09-15 10:55 ` Ming Lei
2011-08-30 22:21 ` [PATCH 3/5] PM / QoS: Add function dev_pm_qos_read_value() Rafael J. Wysocki
2011-09-01 15:13 ` Jean Pihet
2011-09-01 22:07 ` Rafael J. Wysocki
2011-09-02 6:49 ` Jean Pihet
2011-09-02 23:55 ` Rafael J. Wysocki
2011-09-03 8:02 ` Rafael J. Wysocki
2011-09-05 7:51 ` Jean Pihet
2011-09-05 15:30 ` Rafael J. Wysocki
2011-09-05 7:44 ` Jean Pihet
2011-08-30 22:21 ` [RFC][PATCH 4/5] PM / Domains: Add device stop governor function Rafael J. Wysocki
2011-08-30 22:22 ` [RFC][PATCH 5/5] PM / Domains: Add default power off " Rafael J. Wysocki
2011-09-01 15:17 ` Jean Pihet
2011-09-01 22:11 ` Rafael J. Wysocki [this message]
2011-09-01 15:28 ` [PATCH 0/5] PM: Generic PM domains and device PM QoS Jean Pihet
2011-09-01 22:14 ` Rafael J. Wysocki
2011-09-24 21:23 ` [PATCH 0/3] PM: Runtime PM and device PM QoS refinements Rafael J. Wysocki
2011-09-24 21:24 ` [PATCH 1/3] PM / Domains: Split device PM domain data into base and need_restore Rafael J. Wysocki
2011-09-24 21:25 ` [PATCH 2/3] PM / Runtime: Don't run callbacks under lock for power.irq_safe set Rafael J. Wysocki
2011-09-25 8:24 ` Ming Lei
2011-09-26 23:59 ` Kevin Hilman
2011-09-27 17:16 ` Rafael J. Wysocki
2011-09-27 19:50 ` Rafael J. Wysocki
2011-09-29 0:17 ` Kevin Hilman
2011-09-24 21:26 ` [PATCH 3/3] PM / QoS: Add function dev_pm_qos_read_value() (v2) Rafael J. Wysocki
2011-09-29 8:11 ` Jean Pihet
2011-09-29 20:33 ` Rafael J. Wysocki
2011-09-30 8:08 ` Jean Pihet
2011-09-30 16:46 ` 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=201109020011.12264.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=jean.pihet@newoldbits.com \
--cc=khilman@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
/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
all inboxes | Powered by JetHome®