From: Nishanth Menon <nm@ti.com>
To: Viresh Kumar <viresh.kumar@linaro.org>,
Rafael Wysocki <rjw@rjwysocki.net>,
rob.herring@linaro.org, arnd.bergmann@linaro.org,
broonie@kernel.org, mike.turquette@linaro.org,
sboyd@codeaurora.org
Cc: linaro-kernel@lists.linaro.org, linux-pm@vger.kernel.org,
grant.likely@linaro.org, olof@lixom.net, Sudeep.Holla@arm.com,
devicetree@vger.kernel.org, viswanath.puttagunta@linaro.org,
l.stach@pengutronix.de, thomas.petazzoni@free-electrons.com,
linux-arm-kernel@lists.infradead.org, ta.omasab@gmail.com,
kesavan.abhilash@gmail.com, khilman@linaro.org,
santosh.shilimkar@oracle.com
Subject: Re: [PATCH V5 3/3] OPP: Add binding for 'opp-suspend'
Date: Thu, 21 May 2015 00:32:03 -0500 [thread overview]
Message-ID: <555D6DD3.7000404@ti.com> (raw)
In-Reply-To: <618b02107af650bcb3246e165095bbca207d511a.1432091956.git.viresh.kumar@linaro.org>
On 05/19/2015 10:41 PM, Viresh Kumar wrote:
> On few platforms, for power efficiency, we want the device to be
> configured for a specific OPP while we put the device in suspend state.
>
> Add an optional property in operating-points-v2 bindings for that.
Why not just mark it as a property of an OPP rather than a phandle? just
thinking that this might setup a precedence for future needs like
"shutdown OPP" or "Reboot OPP" or something different that some other
SoC might have..
>
> Suggested-by: Nishanth Menon <nm@ti.com>
> Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
> ---
> Documentation/devicetree/bindings/power/opp.txt | 14 ++++++++++----
> 1 file changed, 10 insertions(+), 4 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/power/opp.txt b/Documentation/devicetree/bindings/power/opp.txt
> index 7f30d9b07db7..880f5e14b6e2 100644
> --- a/Documentation/devicetree/bindings/power/opp.txt
> +++ b/Documentation/devicetree/bindings/power/opp.txt
> @@ -72,6 +72,8 @@ This describes the OPPs belonging to a device. This node can have following
> Missing property means devices have independent clock/voltage/current lines,
> but they share OPP tables.
>
> +- opp-suspend: Phandle of the OPP to set while device is suspended.
> +
>
> * OPP Node
>
> @@ -143,9 +145,10 @@ Example 1: Single cluster Dual-core ARM cortex A9, switch DVFS states together.
>
> cpu0_opp: opp0 {
> compatible = "operating-points-v2";
> + opp-suspend = <&suspend_opp>;
> opp-shared;
>
> - entry00 {
> + suspend-opp: entry00 {
> opp-hz = <1000000000>;
> opp-microvolt = <970000 975000 985000>;
> opp-microamp = <70000>;
> @@ -217,13 +220,14 @@ independently.
>
> cpu0_opp: opp0 {
> compatible = "operating-points-v2";
> + opp-suspend = <&suspend_opp>;
>
> /*
> * Missing opp-shared property means CPUs switch DVFS states
> * independently.
> */
>
> - entry00 {
> + suspend-opp: entry00 {
> opp-hz = <1000000000>;
> opp-microvolt = <970000 975000 985000>;
> opp-microamp = <70000>;
> @@ -296,9 +300,10 @@ DVFS state together.
>
> cluster0_opp: opp0 {
> compatible = "operating-points-v2";
> + opp-suspend = <&suspend_opp0>;
> opp-shared;
>
> - entry00 {
> + suspend-opp0: entry00 {
> opp-hz = <1000000000>;
> opp-microvolt = <970000 975000 985000>;
> opp-microamp = <70000>;
> @@ -321,9 +326,10 @@ DVFS state together.
>
> cluster1_opp: opp1 {
> compatible = "operating-points-v2";
> + opp-suspend = <&suspend_opp1>;
> opp-shared;
>
> - entry10 {
> + suspend-opp1: entry10 {
> opp-hz = <1300000000>;
> opp-microvolt = <1045000 1050000 1055000>;
> opp-microamp = <95000>;
>
--
Regards,
Nishanth Menon
WARNING: multiple messages have this Message-ID (diff)
From: nm@ti.com (Nishanth Menon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V5 3/3] OPP: Add binding for 'opp-suspend'
Date: Thu, 21 May 2015 00:32:03 -0500 [thread overview]
Message-ID: <555D6DD3.7000404@ti.com> (raw)
In-Reply-To: <618b02107af650bcb3246e165095bbca207d511a.1432091956.git.viresh.kumar@linaro.org>
On 05/19/2015 10:41 PM, Viresh Kumar wrote:
> On few platforms, for power efficiency, we want the device to be
> configured for a specific OPP while we put the device in suspend state.
>
> Add an optional property in operating-points-v2 bindings for that.
Why not just mark it as a property of an OPP rather than a phandle? just
thinking that this might setup a precedence for future needs like
"shutdown OPP" or "Reboot OPP" or something different that some other
SoC might have..
>
> Suggested-by: Nishanth Menon <nm@ti.com>
> Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
> ---
> Documentation/devicetree/bindings/power/opp.txt | 14 ++++++++++----
> 1 file changed, 10 insertions(+), 4 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/power/opp.txt b/Documentation/devicetree/bindings/power/opp.txt
> index 7f30d9b07db7..880f5e14b6e2 100644
> --- a/Documentation/devicetree/bindings/power/opp.txt
> +++ b/Documentation/devicetree/bindings/power/opp.txt
> @@ -72,6 +72,8 @@ This describes the OPPs belonging to a device. This node can have following
> Missing property means devices have independent clock/voltage/current lines,
> but they share OPP tables.
>
> +- opp-suspend: Phandle of the OPP to set while device is suspended.
> +
>
> * OPP Node
>
> @@ -143,9 +145,10 @@ Example 1: Single cluster Dual-core ARM cortex A9, switch DVFS states together.
>
> cpu0_opp: opp0 {
> compatible = "operating-points-v2";
> + opp-suspend = <&suspend_opp>;
> opp-shared;
>
> - entry00 {
> + suspend-opp: entry00 {
> opp-hz = <1000000000>;
> opp-microvolt = <970000 975000 985000>;
> opp-microamp = <70000>;
> @@ -217,13 +220,14 @@ independently.
>
> cpu0_opp: opp0 {
> compatible = "operating-points-v2";
> + opp-suspend = <&suspend_opp>;
>
> /*
> * Missing opp-shared property means CPUs switch DVFS states
> * independently.
> */
>
> - entry00 {
> + suspend-opp: entry00 {
> opp-hz = <1000000000>;
> opp-microvolt = <970000 975000 985000>;
> opp-microamp = <70000>;
> @@ -296,9 +300,10 @@ DVFS state together.
>
> cluster0_opp: opp0 {
> compatible = "operating-points-v2";
> + opp-suspend = <&suspend_opp0>;
> opp-shared;
>
> - entry00 {
> + suspend-opp0: entry00 {
> opp-hz = <1000000000>;
> opp-microvolt = <970000 975000 985000>;
> opp-microamp = <70000>;
> @@ -321,9 +326,10 @@ DVFS state together.
>
> cluster1_opp: opp1 {
> compatible = "operating-points-v2";
> + opp-suspend = <&suspend_opp1>;
> opp-shared;
>
> - entry10 {
> + suspend-opp1: entry10 {
> opp-hz = <1300000000>;
> opp-microvolt = <1045000 1050000 1055000>;
> opp-microamp = <95000>;
>
--
Regards,
Nishanth Menon
next prev parent reply other threads:[~2015-05-21 5:33 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-20 3:41 [PATCH V5 0/3] OPP: Introduce OPP (V2) bindings Viresh Kumar
2015-05-20 3:41 ` Viresh Kumar
2015-05-20 3:41 ` [PATCH V5 1/3] OPP: Redefine bindings to overcome shortcomings Viresh Kumar
2015-05-20 3:41 ` Viresh Kumar
2015-05-20 13:27 ` Rob Herring
2015-05-20 13:27 ` Rob Herring
[not found] ` <CAL_JsqKR0-TcBjCnoaLBR9M2wGHCOuO2KSyL+4U+dpTvHGzubQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-05-20 13:35 ` Viresh Kumar
2015-05-20 13:35 ` Viresh Kumar
2015-05-21 5:27 ` Nishanth Menon
2015-05-21 5:27 ` Nishanth Menon
2015-05-21 5:46 ` Viresh Kumar
2015-05-21 5:46 ` Viresh Kumar
2015-05-21 5:58 ` Nishanth Menon
2015-05-21 5:58 ` Nishanth Menon
2015-05-21 6:06 ` Viresh Kumar
2015-05-21 6:06 ` Viresh Kumar
2015-05-22 15:55 ` Rob Herring
2015-05-22 15:55 ` Rob Herring
[not found] ` <CAL_JsqKhpyLgh5_1jZ_u0OP7=Piw=pgqZdQJ0K4Rm7DQ5ve+gA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-05-26 5:20 ` Viresh Kumar
2015-05-26 5:20 ` Viresh Kumar
2015-05-26 5:14 ` Viresh Kumar
2015-05-26 5:14 ` Viresh Kumar
2015-05-20 3:41 ` [PATCH V5 2/3] OPP: Allow multiple OPP tables to be passed via DT Viresh Kumar
2015-05-20 3:41 ` Viresh Kumar
2015-05-21 5:34 ` Nishanth Menon
2015-05-21 5:34 ` Nishanth Menon
2015-05-21 5:50 ` Viresh Kumar
2015-05-21 5:50 ` Viresh Kumar
2015-05-26 4:51 ` Viresh Kumar
2015-05-26 4:51 ` Viresh Kumar
2015-05-20 3:41 ` [PATCH V5 3/3] OPP: Add binding for 'opp-suspend' Viresh Kumar
2015-05-20 3:41 ` Viresh Kumar
2015-05-21 5:32 ` Nishanth Menon [this message]
2015-05-21 5:32 ` Nishanth Menon
2015-05-21 5:49 ` Viresh Kumar
2015-05-21 5:49 ` Viresh Kumar
2015-05-21 6:04 ` Nishanth Menon
2015-05-21 6:04 ` Nishanth Menon
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=555D6DD3.7000404@ti.com \
--to=nm@ti.com \
--cc=Sudeep.Holla@arm.com \
--cc=arnd.bergmann@linaro.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=grant.likely@linaro.org \
--cc=kesavan.abhilash@gmail.com \
--cc=khilman@linaro.org \
--cc=l.stach@pengutronix.de \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=mike.turquette@linaro.org \
--cc=olof@lixom.net \
--cc=rjw@rjwysocki.net \
--cc=rob.herring@linaro.org \
--cc=santosh.shilimkar@oracle.com \
--cc=sboyd@codeaurora.org \
--cc=ta.omasab@gmail.com \
--cc=thomas.petazzoni@free-electrons.com \
--cc=viresh.kumar@linaro.org \
--cc=viswanath.puttagunta@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.