From: Viresh Kumar <viresh.kumar@linaro.org> To: Rafael Wysocki <rjw@rjwysocki.net>, rob.herring@linaro.org, arnd.bergmann@linaro.org, nm@ti.com, 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, Viresh Kumar <viresh.kumar@linaro.org> Subject: [PATCH V5 2/3] OPP: Allow multiple OPP tables to be passed via DT Date: Wed, 20 May 2015 09:11:39 +0530 [thread overview] Message-ID: <4690ad854263d6553debab67d65d230105c206ec.1432091956.git.viresh.kumar@linaro.org> (raw) In-Reply-To: <cover.1432091956.git.viresh.kumar@linaro.org> In-Reply-To: <cover.1432091956.git.viresh.kumar@linaro.org> On some platforms (Like Qualcomm's SoCs), it is not decided until runtime on what OPPs to use. The OPP tables can be fixed at compile time, but which table to use is found out only after reading some efuses (sort of an prom) and knowing characteristics of the SoC. To support such platform we need to pass multiple OPP tables per device and hardware should be able to choose one and only one table out of those. Update OPP-v2 bindings to support that. Acked-by: Nishanth Menon <nm@ti.com> Reviewed-by: Stephen Boyd <sboyd@codeaurora.org> Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org> --- Documentation/devicetree/bindings/power/opp.txt | 52 +++++++++++++++++++++++++ 1 file changed, 52 insertions(+) diff --git a/Documentation/devicetree/bindings/power/opp.txt b/Documentation/devicetree/bindings/power/opp.txt index d132e2927b21..7f30d9b07db7 100644 --- a/Documentation/devicetree/bindings/power/opp.txt +++ b/Documentation/devicetree/bindings/power/opp.txt @@ -46,6 +46,9 @@ Devices supporting OPPs must set their "operating-points-v2" property with phandle to a OPP descriptor in their DT node. The OPP core will use this phandle to find the operating points for the device. +Devices may want to choose OPP tables at runtime and so can provide a list of +phandles here. But only *one* of them should be chosen at runtime. + * OPP Descriptor Node @@ -61,6 +64,9 @@ This describes the OPPs belonging to a device. This node can have following reference an OPP. Optional properties: +- opp-name: Name of the OPP table, to uniquely identify it if more than one OPP + table is supplied in "operating-points-v2" property of device. + - opp-shared: Indicates that device nodes using this OPP descriptor's phandle switch their DVFS state together, i.e. they share clock/voltage/current lines. Missing property means devices have independent clock/voltage/current lines, @@ -394,3 +400,49 @@ Example 4: Handling multiple regulators }; }; }; + +Example 5: Multiple OPP tables + +/ { + cpus { + cpu@0 { + compatible = "arm,cortex-a7"; + ... + + opp-supply = <&cpu_supply> + operating-points-v2 = <&cpu0_opp0>, <&cpu0_opp1>; + }; + }; + + cpu0_opp0: opp0 { + compatible = "operating-points-v2"; + opp-name = "opp-slow"; + opp-shared; + + entry00 { + opp-hz = <600000000>; + ... + }; + + entry01 { + opp-hz = <800000000>; + ... + }; + }; + + cpu0_opp1: opp1 { + compatible = "operating-points-v2"; + opp-name = "opp-fast"; + opp-shared; + + entry10 { + opp-hz = <1000000000>; + ... + }; + + entry11 { + opp-hz = <1100000000>; + ... + }; + }; +}; -- 2.4.0
WARNING: multiple messages have this Message-ID (diff)
From: viresh.kumar@linaro.org (Viresh Kumar) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH V5 2/3] OPP: Allow multiple OPP tables to be passed via DT Date: Wed, 20 May 2015 09:11:39 +0530 [thread overview] Message-ID: <4690ad854263d6553debab67d65d230105c206ec.1432091956.git.viresh.kumar@linaro.org> (raw) In-Reply-To: <cover.1432091956.git.viresh.kumar@linaro.org> On some platforms (Like Qualcomm's SoCs), it is not decided until runtime on what OPPs to use. The OPP tables can be fixed at compile time, but which table to use is found out only after reading some efuses (sort of an prom) and knowing characteristics of the SoC. To support such platform we need to pass multiple OPP tables per device and hardware should be able to choose one and only one table out of those. Update OPP-v2 bindings to support that. Acked-by: Nishanth Menon <nm@ti.com> Reviewed-by: Stephen Boyd <sboyd@codeaurora.org> Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org> --- Documentation/devicetree/bindings/power/opp.txt | 52 +++++++++++++++++++++++++ 1 file changed, 52 insertions(+) diff --git a/Documentation/devicetree/bindings/power/opp.txt b/Documentation/devicetree/bindings/power/opp.txt index d132e2927b21..7f30d9b07db7 100644 --- a/Documentation/devicetree/bindings/power/opp.txt +++ b/Documentation/devicetree/bindings/power/opp.txt @@ -46,6 +46,9 @@ Devices supporting OPPs must set their "operating-points-v2" property with phandle to a OPP descriptor in their DT node. The OPP core will use this phandle to find the operating points for the device. +Devices may want to choose OPP tables at runtime and so can provide a list of +phandles here. But only *one* of them should be chosen at runtime. + * OPP Descriptor Node @@ -61,6 +64,9 @@ This describes the OPPs belonging to a device. This node can have following reference an OPP. Optional properties: +- opp-name: Name of the OPP table, to uniquely identify it if more than one OPP + table is supplied in "operating-points-v2" property of device. + - opp-shared: Indicates that device nodes using this OPP descriptor's phandle switch their DVFS state together, i.e. they share clock/voltage/current lines. Missing property means devices have independent clock/voltage/current lines, @@ -394,3 +400,49 @@ Example 4: Handling multiple regulators }; }; }; + +Example 5: Multiple OPP tables + +/ { + cpus { + cpu at 0 { + compatible = "arm,cortex-a7"; + ... + + opp-supply = <&cpu_supply> + operating-points-v2 = <&cpu0_opp0>, <&cpu0_opp1>; + }; + }; + + cpu0_opp0: opp0 { + compatible = "operating-points-v2"; + opp-name = "opp-slow"; + opp-shared; + + entry00 { + opp-hz = <600000000>; + ... + }; + + entry01 { + opp-hz = <800000000>; + ... + }; + }; + + cpu0_opp1: opp1 { + compatible = "operating-points-v2"; + opp-name = "opp-fast"; + opp-shared; + + entry10 { + opp-hz = <1000000000>; + ... + }; + + entry11 { + opp-hz = <1100000000>; + ... + }; + }; +}; -- 2.4.0
next prev parent reply other threads:[~2015-05-20 3:41 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 ` Viresh Kumar [this message] 2015-05-20 3:41 ` [PATCH V5 2/3] OPP: Allow multiple OPP tables to be passed via DT 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 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=4690ad854263d6553debab67d65d230105c206ec.1432091956.git.viresh.kumar@linaro.org \ --to=viresh.kumar@linaro.org \ --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=nm@ti.com \ --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=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: linkBe 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.