linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: viresh.kumar@linaro.org (Viresh Kumar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2 09/11] OPP: Add support for opp-suspend
Date: Mon, 27 Jul 2015 10:32:39 +0530	[thread overview]
Message-ID: <ec715e6ab8c026340cad992a79eea34c64a3f05a.1437972635.git.viresh.kumar@linaro.org> (raw)
In-Reply-To: <cover.1437972635.git.viresh.kumar@linaro.org>

With "operating-points-v2" bindings, its possible to specify the OPP to
which the device must be switched, before suspending.

This patch adds support for getting that information.

Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
---
 drivers/base/power/opp.c | 11 +++++++++++
 1 file changed, 11 insertions(+)

diff --git a/drivers/base/power/opp.c b/drivers/base/power/opp.c
index d6ab6af7e847..22b1e6ae7a94 100644
--- a/drivers/base/power/opp.c
+++ b/drivers/base/power/opp.c
@@ -133,6 +133,7 @@ struct device_opp {
 	struct device_node *np;
 	unsigned long clock_latency_ns_max;
 	bool shared_opp;
+	struct dev_pm_opp *suspend_opp;
 };
 
 /*
@@ -909,6 +910,16 @@ static int _opp_add_static_v2(struct device *dev, struct device_node *np)
 	if (ret)
 		goto free_opp;
 
+	/* OPP to select on device suspend */
+	if (of_property_read_bool(np, "opp-suspend")) {
+		if (dev_opp->suspend_opp)
+			dev_warn(dev, "%s: Multiple suspend OPPs found (%lu %lu)\n",
+				 __func__, dev_opp->suspend_opp->rate,
+				 new_opp->rate);
+		else
+			dev_opp->suspend_opp = new_opp;
+	}
+
 	if (new_opp->clock_latency_ns > dev_opp->clock_latency_ns_max)
 		dev_opp->clock_latency_ns_max = new_opp->clock_latency_ns;
 
-- 
2.4.0

  parent reply	other threads:[~2015-07-27  5:02 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-27  5:02 [PATCH V2 00/11] OPP: Add code to support operating-points-v2 bindings Viresh Kumar
2015-07-27  5:02 ` [PATCH V2 01/11] opp: Create a directory for opp bindings Viresh Kumar
2015-07-27  5:02 ` [PATCH V2 02/11] opp: Relocate few routines Viresh Kumar
2015-07-27  5:02 ` [PATCH V2 03/11] OPP: Create _remove_device_opp() for freeing dev_opp Viresh Kumar
2015-07-27  5:02 ` [PATCH V2 04/11] OPP: Allocate dev_opp from _add_device_opp() Viresh Kumar
2015-07-27  5:02 ` [PATCH V2 05/11] OPP: Break _opp_add_dynamic() into smaller functions Viresh Kumar
2015-07-27  5:02 ` [PATCH V2 06/11] opp: Add support to parse "operating-points-v2" bindings Viresh Kumar
2015-07-27 14:23   ` Bartlomiej Zolnierkiewicz
2015-07-27  5:02 ` [PATCH V2 07/11] OPP: Add clock-latency-ns support Viresh Kumar
2015-07-27 14:27   ` Bartlomiej Zolnierkiewicz
2015-07-27  5:02 ` [PATCH V2 08/11] opp: Add OPP sharing information to OPP library Viresh Kumar
2015-07-27 14:48   ` Bartlomiej Zolnierkiewicz
2015-07-28  2:11     ` Viresh Kumar
2015-07-27  5:02 ` Viresh Kumar [this message]
2015-07-27 14:50   ` [PATCH V2 09/11] OPP: Add support for opp-suspend Bartlomiej Zolnierkiewicz
2015-07-27  5:02 ` [PATCH V2 10/11] opp: Add helpers for initializing CPU OPPs Viresh Kumar
2015-07-27 16:37   ` Bartlomiej Zolnierkiewicz
2015-07-27  5:02 ` [PATCH V2 11/11] cpufreq-dt: Add support for operating-points-v2 bindings Viresh Kumar
2015-07-27 16:50   ` Bartlomiej Zolnierkiewicz
2015-07-27 13:39 ` [PATCH V2 00/11] OPP: Add code to support " Rafael J. Wysocki
2015-07-27 14:34   ` Viresh Kumar

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=ec715e6ab8c026340cad992a79eea34c64a3f05a.1437972635.git.viresh.kumar@linaro.org \
    --to=viresh.kumar@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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).