From: Rob Herring <robh@kernel.org>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Rafael Wysocki <rjw@rjwysocki.net>,
robh+dt@kernel.org, sboyd@codeaurora.org, lee.jones@linaro.org,
linaro-kernel@lists.linaro.org, linux-pm@vger.kernel.org,
mark.rutland@arm.com, pawel.moll@arm.com,
ijc+devicetree@hellion.org.uk, galak@codeaurora.org, nm@ti.com,
devicetree@vger.kernel.org, b.zolnierkie@samsung.com,
m.szyprowski@samsung.com,
open list <linux-kernel@vger.kernel.org>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>
Subject: Re: [PATCH V2 4/5] PM / OPP: Rename OPP nodes as opp@<opp-hz>
Date: Wed, 4 Nov 2015 21:18:41 -0600 [thread overview]
Message-ID: <20151105031841.GA27985@rob-hp-laptop> (raw)
In-Reply-To: <5d5f139d334d5e503932c06694b47f0c3477caed.1446687367.git.viresh.kumar@linaro.org>
On Thu, Nov 05, 2015 at 07:11:55AM +0530, Viresh Kumar wrote:
> It would be better to name OPP nodes as opp@<opp-hz> as that will ensure
> that multiple DT nodes don't contain the same frequency. Of course we
> expect the writer to name the node with its opp-hz frequency and not any
> other frequency.
>
> And that will let the compile error out if multiple nodes are using the
> same opp-hz frequency.
>
> Suggested-by: Stephen Boyd <sboyd@codeaurora.org>
> Reviewed-by: Stephen Boyd <sboyd@codeaurora.org>
> Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
Acked-by: Rob Herring <robh@kernel.org>
> ---
> Documentation/devicetree/bindings/opp/opp.txt | 38 +++++++++++++--------------
> 1 file changed, 19 insertions(+), 19 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/opp/opp.txt b/Documentation/devicetree/bindings/opp/opp.txt
> index 30c4bb3718bc..10ef08dc1b4c 100644
> --- a/Documentation/devicetree/bindings/opp/opp.txt
> +++ b/Documentation/devicetree/bindings/opp/opp.txt
> @@ -183,20 +183,20 @@ Example 1: Single cluster Dual-core ARM cortex A9, switch DVFS states together.
> compatible = "operating-points-v2";
> opp-shared;
>
> - opp00 {
> + opp@1000000000 {
> opp-hz = /bits/ 64 <1000000000>;
> opp-microvolt = <970000 975000 985000>;
> opp-microamp = <70000>;
> clock-latency-ns = <300000>;
> opp-suspend;
> };
> - opp01 {
> + opp@1100000000 {
> opp-hz = /bits/ 64 <1100000000>;
> opp-microvolt = <980000 1000000 1010000>;
> opp-microamp = <80000>;
> clock-latency-ns = <310000>;
> };
> - opp02 {
> + opp@1200000000 {
> opp-hz = /bits/ 64 <1200000000>;
> opp-microvolt = <1025000>;
> clock-latency-ns = <290000>;
> @@ -262,20 +262,20 @@ independently.
> * independently.
> */
>
> - opp00 {
> + opp@1000000000 {
> opp-hz = /bits/ 64 <1000000000>;
> opp-microvolt = <970000 975000 985000>;
> opp-microamp = <70000>;
> clock-latency-ns = <300000>;
> opp-suspend;
> };
> - opp01 {
> + opp@1100000000 {
> opp-hz = /bits/ 64 <1100000000>;
> opp-microvolt = <980000 1000000 1010000>;
> opp-microamp = <80000>;
> clock-latency-ns = <310000>;
> };
> - opp02 {
> + opp@1200000000 {
> opp-hz = /bits/ 64 <1200000000>;
> opp-microvolt = <1025000>;
> opp-microamp = <90000;
> @@ -338,20 +338,20 @@ DVFS state together.
> compatible = "operating-points-v2";
> opp-shared;
>
> - opp00 {
> + opp@1000000000 {
> opp-hz = /bits/ 64 <1000000000>;
> opp-microvolt = <970000 975000 985000>;
> opp-microamp = <70000>;
> clock-latency-ns = <300000>;
> opp-suspend;
> };
> - opp01 {
> + opp@1100000000 {
> opp-hz = /bits/ 64 <1100000000>;
> opp-microvolt = <980000 1000000 1010000>;
> opp-microamp = <80000>;
> clock-latency-ns = <310000>;
> };
> - opp02 {
> + opp@1200000000 {
> opp-hz = /bits/ 64 <1200000000>;
> opp-microvolt = <1025000>;
> opp-microamp = <90000>;
> @@ -364,20 +364,20 @@ DVFS state together.
> compatible = "operating-points-v2";
> opp-shared;
>
> - opp10 {
> + opp@1300000000 {
> opp-hz = /bits/ 64 <1300000000>;
> opp-microvolt = <1045000 1050000 1055000>;
> opp-microamp = <95000>;
> clock-latency-ns = <400000>;
> opp-suspend;
> };
> - opp11 {
> + opp@1400000000 {
> opp-hz = /bits/ 64 <1400000000>;
> opp-microvolt = <1075000>;
> opp-microamp = <100000>;
> clock-latency-ns = <400000>;
> };
> - opp12 {
> + opp@1500000000 {
> opp-hz = /bits/ 64 <1500000000>;
> opp-microvolt = <1010000 1100000 1110000>;
> opp-microamp = <95000>;
> @@ -404,7 +404,7 @@ Example 4: Handling multiple regulators
> compatible = "operating-points-v2";
> opp-shared;
>
> - opp00 {
> + opp@1000000000 {
> opp-hz = /bits/ 64 <1000000000>;
> opp-microvolt = <970000>, /* Supply 0 */
> <960000>, /* Supply 1 */
> @@ -417,7 +417,7 @@ Example 4: Handling multiple regulators
>
> /* OR */
>
> - opp00 {
> + opp@1000000000 {
> opp-hz = /bits/ 64 <1000000000>;
> opp-microvolt = <970000 975000 985000>, /* Supply 0 */
> <960000 965000 975000>, /* Supply 1 */
> @@ -430,7 +430,7 @@ Example 4: Handling multiple regulators
>
> /* OR */
>
> - opp00 {
> + opp@1000000000 {
> opp-hz = /bits/ 64 <1000000000>;
> opp-microvolt = <970000 975000 985000>, /* Supply 0 */
> <960000 965000 975000>, /* Supply 1 */
> @@ -462,7 +462,7 @@ Example 5: opp-supported-hw
> status = "okay";
> opp-shared;
>
> - opp00 {
> + opp@600000000 {
> /*
> * Supports all substrate and process versions for 0xF
> * cuts, i.e. only first four cuts.
> @@ -473,7 +473,7 @@ Example 5: opp-supported-hw
> ...
> };
>
> - opp01 {
> + opp@800000000 {
> /*
> * Supports:
> * - cuts: only one, 6th cut (represented by 6th bit).
> @@ -506,7 +506,7 @@ Example 6: opp-microvolt-<name>, opp-microamp-<name>, turbo-mode-<name>,
> compatible = "operating-points-v2";
> opp-shared;
>
> - opp00 {
> + opp@1000000000 {
> opp-hz = /bits/ 64 <1000000000>;
> opp-microvolt-slow = <900000 915000 925000>;
> opp-microvolt-fast = <970000 975000 985000>;
> @@ -516,7 +516,7 @@ Example 6: opp-microvolt-<name>, opp-microamp-<name>, turbo-mode-<name>,
> opp-suspend-slow; /* Will be used as suspend-opp only if 'slow' is chosen */
> };
>
> - opp01 {
> + opp@1200000000 {
> opp-hz = /bits/ 64 <1200000000>;
> opp-microvolt-slow = <900000 915000 925000>, /* Supply vcc0 */
> <910000 925000 935000>; /* Supply vcc1 */
> --
> 2.6.2.198.g614a2ac
>
next prev parent reply other threads:[~2015-11-05 3:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-05 1:41 [PATCH V2 0/5] PM / OPP: opp-supported-hw and <prop>-name bindings Viresh Kumar
2015-11-05 1:41 ` [PATCH V2 1/5] PM / OPP: Add "opp-supported-hw" binding Viresh Kumar
2015-11-05 2:57 ` Rob Herring
2015-11-05 1:41 ` [PATCH V2 2/5] PM / OPP: Add {opp-microvolt|opp-microamp|turbo-mode|opp-suspend}-<name> binding Viresh Kumar
2015-11-05 3:02 ` Rob Herring
2015-11-05 3:19 ` Viresh Kumar
2015-11-05 23:33 ` Rob Herring
2015-11-06 1:53 ` Viresh Kumar
2015-11-10 14:55 ` Viresh Kumar
2015-11-10 15:37 ` Rob Herring
2015-11-05 1:41 ` [PATCH V2 3/5] PM / OPP: Remove 'operating-points-names' binding Viresh Kumar
[not found] ` <c4070eeceb0fdf6a6ab56fcaef1769d01dd01c7e.1446687367.git.viresh.kumar-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2015-11-05 3:09 ` Rob Herring
2015-11-05 1:41 ` [PATCH V2 4/5] PM / OPP: Rename OPP nodes as opp@<opp-hz> Viresh Kumar
2015-11-05 3:18 ` Rob Herring [this message]
2015-11-05 1:41 ` [PATCH V2 5/5] ARM: dts: exynos4412: " Viresh Kumar
2015-11-05 1:51 ` Krzysztof Kozlowski
2015-11-05 1:57 ` Viresh Kumar
2015-11-05 22:31 ` [PATCH V2 0/5] PM / OPP: opp-supported-hw and <prop>-name bindings Rafael J. Wysocki
2015-11-06 1:45 ` 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=20151105031841.GA27985@rob-hp-laptop \
--to=robh@kernel.org \
--cc=b.zolnierkie@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=lee.jones@linaro.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=mark.rutland@arm.com \
--cc=nm@ti.com \
--cc=pawel.moll@arm.com \
--cc=rafael.j.wysocki@intel.com \
--cc=rjw@rjwysocki.net \
--cc=robh+dt@kernel.org \
--cc=sboyd@codeaurora.org \
--cc=viresh.kumar@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