From: Rob Herring <robh@kernel.org>
To: Lee Jones <lee.jones@linaro.org>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, kernel@stlinux.com,
maxime.coquelin@st.com, viresh.kumar@linaro.org,
linux-pm@vger.kernel.org, rjw@rjwysocki.net,
devicetree@vger.kernel.org, ajitpal.singh@st.com
Subject: Re: [PATCH v5 10/11] dt: cpufreq: st: Provide bindings for ST's CPUFreq implementation
Date: Tue, 8 Dec 2015 21:52:40 -0600 [thread overview]
Message-ID: <20151209035240.GA25250@rob-hp-laptop> (raw)
In-Reply-To: <1449585124-15596-11-git-send-email-lee.jones@linaro.org>
On Tue, Dec 08, 2015 at 02:32:03PM +0000, Lee Jones wrote:
> Cc: devicetree@vger.kernel.org
> Signed-off-by: Lee Jones <lee.jones@linaro.org>
Acked-by: Rob Herring <robh@kernel.org>
> ---
> .../devicetree/bindings/cpufreq/cpufreq-st.txt | 91 ++++++++++++++++++++++
> 1 file changed, 91 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/cpufreq/cpufreq-st.txt
>
> diff --git a/Documentation/devicetree/bindings/cpufreq/cpufreq-st.txt b/Documentation/devicetree/bindings/cpufreq/cpufreq-st.txt
> new file mode 100644
> index 0000000..d91a02a
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/cpufreq/cpufreq-st.txt
> @@ -0,0 +1,91 @@
> +Binding for ST's CPUFreq driver
> +===============================
> +
> +ST's CPUFreq driver attempts to read 'process' and 'version' attributes
> +from the SoC, then supplies the OPP framework with 'prop' and 'supported
> +hardware' information respectively. The framework is then able to read
> +the DT and operate in the usual way.
> +
> +For more information about the expected DT format [See: ../opp/opp.txt].
> +
> +Frequency Scaling only
> +----------------------
> +
> +No vendor specific driver required for this.
> +
> +Located in CPU's node:
> +
> +- operating-points : [See: ../power/opp.txt]
> +
> +Example [safe]
> +--------------
> +
> +cpus {
> + cpu@0 {
> + /* kHz uV */
> + operating-points = <1500000 0
> + 1200000 0
> + 800000 0
> + 500000 0>;
> + };
> +};
> +
> +Dynamic Voltage and Frequency Scaling (DVFS)
> +--------------------------------------------
> +
> +This requires the ST CPUFreq driver to supply 'process' and 'version' info.
> +
> +Located in CPU's node:
> +
> +- operating-points-v2 : [See ../power/opp.txt]
> +
> +Example [unsafe]
> +----------------
> +
> +cpus {
> + cpu@0 {
> + operating-points-v2 = <&cpu0_opp_table>;
> + };
> +};
> +
> +cpu0_opp_table: opp_table {
> + compatible = "operating-points-v2";
> +
> + /* ############################################################### */
> + /* # WARNING: Do not attempt to copy/replicate these nodes, # */
> + /* # they are only to be supplied by the bootloader !!! # */
> + /* ############################################################### */
> + opp0 {
> + /* Major Minor Substrate */
> + /* 2 all all */
> + opp-supported-hw = <0x00000004 0xffffffff 0xffffffff>;
> + opp-hz = /bits/ 64 <1500000000>;
> + clock-latency-ns = <10000000>;
> +
> + opp-microvolt-pcode0 = <1200000>;
> + opp-microvolt-pcode1 = <1200000>;
> + opp-microvolt-pcode2 = <1200000>;
> + opp-microvolt-pcode3 = <1200000>;
> + opp-microvolt-pcode4 = <1170000>;
> + opp-microvolt-pcode5 = <1140000>;
> + opp-microvolt-pcode6 = <1100000>;
> + opp-microvolt-pcode7 = <1070000>;
> + };
> +
> + opp1 {
> + /* Major Minor Substrate */
> + /* all all all */
> + opp-supported-hw = <0xffffffff 0xffffffff 0xffffffff>;
> + opp-hz = /bits/ 64 <1200000000>;
> + clock-latency-ns = <10000000>;
> +
> + opp-microvolt-pcode0 = <1110000>;
> + opp-microvolt-pcode1 = <1150000>;
> + opp-microvolt-pcode2 = <1100000>;
> + opp-microvolt-pcode3 = <1080000>;
> + opp-microvolt-pcode4 = <1040000>;
> + opp-microvolt-pcode5 = <1020000>;
> + opp-microvolt-pcode6 = <980000>;
> + opp-microvolt-pcode7 = <930000>;
> + };
> +};
> --
> 1.9.1
>
> --
> To unsubscribe from this list: send the line "unsubscribe devicetree" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-12-09 3:52 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-08 14:31 [PATCH v5 00/11] cpufreq: Introduce ST's CPUFreq driver Lee Jones
2015-12-08 14:31 ` [PATCH v5 01/11] ARM: multi_v7_defconfig: Enable ST's PWM driver Lee Jones
2015-12-08 14:31 ` [PATCH v5 02/11] ARM: multi_v7_defconfig: Enable ST's Power Reset driver Lee Jones
2015-12-08 14:31 ` [PATCH v5 03/11] ARM: multi_v7_defconfig: Enable support for PWM Regulators Lee Jones
2015-12-08 14:31 ` [PATCH v5 04/11] ARM: STi: STiH407: Provide generic (safe) DVFS configuration Lee Jones
2015-12-08 15:03 ` Viresh Kumar
2015-12-08 15:37 ` Lee Jones
2015-12-08 14:31 ` [PATCH v5 05/11] ARM: STi: STiH407: Provide CPU with clocking information Lee Jones
2015-12-08 14:31 ` [PATCH v5 06/11] ARM: STi: STiH407: Link CPU with its voltage supply Lee Jones
2015-12-08 14:32 ` [PATCH v5 07/11] ARM: STi: STiH407: Provide CPU with a means to look-up Major number Lee Jones
2015-12-08 14:32 ` [PATCH v5 08/11] ARM: STi: Register CPUFreq device Lee Jones
2015-12-09 2:39 ` Viresh Kumar
2015-12-09 9:15 ` Arnd Bergmann
2015-12-09 9:19 ` Viresh Kumar
2015-12-09 11:25 ` Lee Jones
2015-12-08 14:32 ` [PATCH v5 09/11] cpufreq: st: Provide runtime initialised driver for ST's platforms Lee Jones
2015-12-09 2:57 ` Viresh Kumar
2015-12-09 2:58 ` Viresh Kumar
2015-12-08 14:32 ` [PATCH v5 10/11] dt: cpufreq: st: Provide bindings for ST's CPUFreq implementation Lee Jones
2015-12-09 3:52 ` Rob Herring [this message]
2015-12-08 14:32 ` [PATCH v5 11/11] MAINTAINERS: Add ST's CPUFreq driver to the STI file list Lee Jones
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=20151209035240.GA25250@rob-hp-laptop \
--to=robh@kernel.org \
--cc=ajitpal.singh@st.com \
--cc=devicetree@vger.kernel.org \
--cc=kernel@stlinux.com \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=maxime.coquelin@st.com \
--cc=rjw@rjwysocki.net \
--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;
as well as URLs for NNTP newsgroup(s).