[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAORVsuW7rFEN8u7RCpmWJamtG2iUbA_zz3ax4hgBjGAZW9vU=A@mail.gmail.com>
Date: Thu, 1 Sep 2011 17:17:51 +0200
From: Jean Pihet <jean.pihet@...oldbits.com>
To: "Rafael J. Wysocki" <rjw@...k.pl>
Cc: Linux PM mailing list <linux-pm@...ts.linux-foundation.org>,
LKML <linux-kernel@...r.kernel.org>,
Linux-sh list <linux-sh@...r.kernel.org>,
Magnus Damm <magnus.damm@...il.com>,
Kevin Hilman <khilman@...com>
Subject: Re: [RFC][PATCH 5/5] PM / Domains: Add default power off governor function
Rafael,
On Wed, Aug 31, 2011 at 12:22 AM, Rafael J. Wysocki <rjw@...k.pl> wrote:
> From: Rafael J. Wysocki <rjw@...k.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? Is there a mechanism that dynamically
updates the values?
> };
>
> static inline struct generic_pm_domain *pd_to_genpd(struct dev_pm_domain *pd)
> @@ -64,6 +68,9 @@ struct gpd_link {
> };
>
> struct gpd_gov_dev_data {
> + ktime_t start_latency;
> + ktime_t suspend_latency;
> + ktime_t resume_latency;
Same question here.
> s64 break_even_ns;
> };
>
...
Regards,
Jean
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists