devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Viresh Kumar <viresh.kumar@linaro.org>
To: Rafael Wysocki <rjw@rjwysocki.net>,
	ulf.hansson@linaro.org, Kevin Hilman <khilman@linaro.org>
Cc: linaro-kernel@lists.linaro.org, linux-pm@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Vincent Guittot <vincent.guittot@linaro.org>,
	Stephen Boyd <sboyd@codeaurora.org>, Nishanth Menon <nm@ti.com>,
	robh+dt@kernel.org, lina.iyer@linaro.org, rnayak@codeaurora.org,
	Viresh Kumar <viresh.kumar@linaro.org>,
	devicetree@vger.kernel.org
Subject: [PATCH V4 2/9] PM / Domains: Use OPP tables for power-domains
Date: Mon, 20 Mar 2017 15:02:14 +0530	[thread overview]
Message-ID: <5619ac7777689f282f8aafabbde22d71b46a979b.1490001099.git.viresh.kumar@linaro.org> (raw)
In-Reply-To: <cover.1490001099.git.viresh.kumar@linaro.org>
In-Reply-To: <cover.1490001099.git.viresh.kumar@linaro.org>

The OPP table bindings contains all the necessary fields to support
power-domains now. Update the power-domain bindings to allow
"operating-points-v2" to be present within the power-domain node.

Also allow consumer devices, that don't use OPP tables, to specify the
parent power-domain's performance level using the
"domain-performance-state" property.

Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
---
 .../devicetree/bindings/power/power_domain.txt     | 42 ++++++++++++++++++++++
 1 file changed, 42 insertions(+)

diff --git a/Documentation/devicetree/bindings/power/power_domain.txt b/Documentation/devicetree/bindings/power/power_domain.txt
index 723e1ad937da..5db112fa5d7c 100644
--- a/Documentation/devicetree/bindings/power/power_domain.txt
+++ b/Documentation/devicetree/bindings/power/power_domain.txt
@@ -38,6 +38,9 @@ phandle arguments (so called PM domain specifiers) of length specified by the
   domain's idle states. In the absence of this property, the domain would be
   considered as capable of being powered-on or powered-off.
 
+- operating-points-v2 : This describes the performance states of a PM domain.
+  Refer to ../opp/opp.txt for more information.
+
 Example:
 
 	power: power-controller@12340000 {
@@ -118,4 +121,43 @@ The node above defines a typical PM domain consumer device, which is located
 inside a PM domain with index 0 of a power controller represented by a node
 with the label "power".
 
+Optional properties:
+- domain-performance-state: A positive integer value representing the minimum
+  power-domain performance level required by the consumer device. The integer
+  value '0' represents the lowest performance level and the higher values
+  represent higher performance levels. The value of "domain-performance-state"
+  field should match the "domain-performance-state" field of one of the OPP
+  nodes in the parent power-domain's OPP table.
+
+
+
+Example:
+
+	domain_opp_table: opp_table {
+		compatible = "operating-points-v2";
+
+		opp@1 {
+			domain-performance-state = <1>;
+			opp-microvolt = <975000 970000 985000>;
+		};
+		opp@2 {
+			domain-performance-state = <2>;
+			opp-microvolt = <1075000 1000000 1085000>;
+		};
+	};
+
+	parent: power-controller@12340000 {
+		compatible = "foo,power-controller";
+		reg = <0x12340000 0x1000>;
+		#power-domain-cells = <0>;
+		operating-points-v2 = <&domain_opp_table>;
+	};
+
+	leaky-device@12350000 {
+		compatible = "foo,i-leak-current";
+		reg = <0x12350000 0x1000>;
+		power-domains = <&power 0>;
+		domain-performance-state = <2>;
+	};
+
 [1]. Documentation/devicetree/bindings/power/domain-idle-state.txt
-- 
2.12.0.432.g71c3a4f4ba37

  parent reply	other threads:[~2017-03-20  9:32 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cover.1490001099.git.viresh.kumar@linaro.org>
2017-03-20  9:32 ` [PATCH V4 1/9] PM / OPP: Allow OPP table to be used for power-domains Viresh Kumar
2017-03-24 15:44   ` Rob Herring
2017-04-10  9:25     ` Viresh Kumar
2017-04-10  9:50       ` Viresh Kumar
2017-04-12 16:49   ` Sudeep Holla
     [not found]     ` <0a7146f9-72f1-317c-3aab-770a72462968-5wv7dgnIgG8@public.gmane.org>
2017-04-13  5:37       ` Viresh Kumar
2017-04-13 13:42         ` Sudeep Holla
     [not found]           ` <3adbef6a-7b43-528f-e88f-c2121d30a5d3-5wv7dgnIgG8@public.gmane.org>
2017-04-17  5:27             ` Viresh Kumar
2017-04-18 16:01               ` Sudeep Holla
2017-04-19 11:47                 ` Viresh Kumar
2017-04-19 13:58                   ` Sudeep Holla
     [not found]                     ` <9dee7c0d-e5f4-9fcd-3c92-bf7ec9d43a3b-5wv7dgnIgG8@public.gmane.org>
2017-04-20  5:25                       ` Viresh Kumar
2017-04-20  8:23                         ` Ulf Hansson
2017-04-20  9:33                           ` Viresh Kumar
2017-04-20  9:51                           ` Sudeep Holla
2017-04-20  9:43                         ` Sudeep Holla
2017-04-20  9:52                           ` Viresh Kumar
2017-04-23 22:07                             ` Kevin Hilman
     [not found]                 ` <95aa4b97-4e1a-13bb-f4d8-982b778012ba-5wv7dgnIgG8@public.gmane.org>
2017-04-19 10:11                   ` Viresh Kumar
2017-04-26  4:32                   ` Rajendra Nayak
2017-04-26 13:55                     ` Mark Brown
2017-04-27  9:42                       ` Sudeep Holla
2017-04-27 10:50                         ` Rajendra Nayak
2017-04-28  5:00                           ` Viresh Kumar
2017-04-28  9:44                             ` Sudeep Holla
     [not found]                               ` <b3f5b62c-9423-98e4-d366-78186ab02fb9-5wv7dgnIgG8@public.gmane.org>
2017-04-28 11:12                                 ` Viresh Kumar
2017-04-30 12:49                         ` Mark Brown
2017-05-03 11:21                           ` Sudeep Holla
2017-05-14  9:55                             ` Mark Brown
     [not found]   ` <e772e67a5445319bb8e0f312846ace666adc097f.1490001099.git.viresh.kumar-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2017-04-12 17:05     ` Sudeep Holla
2017-04-13  5:50       ` Viresh Kumar
2017-04-13 13:43         ` Sudeep Holla
2017-04-17  5:33           ` Viresh Kumar
2017-04-18 16:03             ` Sudeep Holla
2017-04-19 10:12               ` Viresh Kumar
2017-03-20  9:32 ` Viresh Kumar [this message]
     [not found]   ` <5619ac7777689f282f8aafabbde22d71b46a979b.1490001099.git.viresh.kumar-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2017-04-12 16:58     ` [PATCH V4 2/9] PM / Domains: Use OPP tables " Sudeep Holla
2017-04-13  6:03       ` Viresh Kumar
2017-04-13 13:45         ` Sudeep Holla

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=5619ac7777689f282f8aafabbde22d71b46a979b.1490001099.git.viresh.kumar@linaro.org \
    --to=viresh.kumar@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=khilman@linaro.org \
    --cc=lina.iyer@linaro.org \
    --cc=linaro-kernel@lists.linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=nm@ti.com \
    --cc=rjw@rjwysocki.net \
    --cc=rnayak@codeaurora.org \
    --cc=robh+dt@kernel.org \
    --cc=sboyd@codeaurora.org \
    --cc=ulf.hansson@linaro.org \
    --cc=vincent.guittot@linaro.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).