From: Michael Turquette <mturquette@baylibre.com>
To: Pi-Cheng Chen <pi-cheng.chen@linaro.org>,
Viresh Kumar <viresh.kumar@linaro.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
Mark Rutland <mark.rutland@arm.com>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
linaro-kernel@lists.linaro.org,
linux-mediatek@lists.infradead.org
Subject: Re: [PATCH v6 1/4] dt-bindings: mediatek: Add MT8173 CPU DVFS clock bindings
Date: Thu, 09 Jul 2015 07:55:51 -0700 [thread overview]
Message-ID: <20150709145551.9112.35610@quantum> (raw)
In-Reply-To: <1436437661-17606-2-git-send-email-pi-cheng.chen@linaro.org>
Quoting Pi-Cheng Chen (2015-07-09 03:27:38)
> This patch adds the clock and regulator consumer properties part of
> document for CPU DVFS clocks on Mediatek MT8173 SoC.
>
> Signed-off-by: Pi-Cheng Chen <pi-cheng.chen@linaro.org>
Acked-by: Michael Turquette <mturquette@baylibre.com>
Regards,
Mike
> ---
> .../devicetree/bindings/clock/mt8173-cpu-dvfs.txt | 83 ++++++++++++++++++++++
> 1 file changed, 83 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/clock/mt8173-cpu-dvfs.txt
>
> diff --git a/Documentation/devicetree/bindings/clock/mt8173-cpu-dvfs.txt b/Documentation/devicetree/bindings/clock/mt8173-cpu-dvfs.txt
> new file mode 100644
> index 0000000..27b3521
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/clock/mt8173-cpu-dvfs.txt
> @@ -0,0 +1,83 @@
> +Device Tree Clock bindings for CPU DVFS clock of Mediatek MT8173 SoC
> +
> +Required properties:
> +- clocks: A list of phandle + clock-specifier pairs for the clocks listed in clock names.
> +- clock-names: Should contain the following:
> + "cpu" - The multiplexer for clock input of CPU cluster.
> + "intermediate" - A parent of "cpu" clock which is used as "intermediate" clock
> + source (usually MAINPLL) when the original CPU PLL is under
> + transition and not stable yet.
> + Please refer to Documentation/devicetree/bindings/clk/clock-bindings.txt for
> + generic clock consumer properties.
> +- proc-supply: Regulator for Vproc of CPU cluster.
> +
> +Optional properties:
> +- sram-supply: Regulator for Vsram of CPU cluster. When present, the cpufreq driver
> + needs to do "voltage tracking" to step by step scale up/down Vproc and
> + Vsram to fit SoC specific needs. When absent, the voltage scaling
> + flow is handled by hardware, hence no software "voltage tracking" is
> + needed.
> +
> +Example:
> +--------
> + cpu0: cpu@0 {
> + device_type = "cpu";
> + compatible = "arm,cortex-a53";
> + reg = <0x000>;
> + enable-method = "psci";
> + cpu-idle-states = <&CPU_SLEEP_0>;
> + clocks = <&infracfg CLK_INFRA_CA53SEL>,
> + <&apmixedsys CLK_APMIXED_MAINPLL>;
> + clock-names = "cpu", "intermediate";
> + };
> +
> + cpu1: cpu@1 {
> + device_type = "cpu";
> + compatible = "arm,cortex-a53";
> + reg = <0x001>;
> + enable-method = "psci";
> + cpu-idle-states = <&CPU_SLEEP_0>;
> + clocks = <&infracfg CLK_INFRA_CA53SEL>,
> + <&apmixedsys CLK_APMIXED_MAINPLL>;
> + clock-names = "cpu", "intermediate";
> + };
> +
> + cpu2: cpu@100 {
> + device_type = "cpu";
> + compatible = "arm,cortex-a57";
> + reg = <0x100>;
> + enable-method = "psci";
> + cpu-idle-states = <&CPU_SLEEP_0>;
> + clocks = <&infracfg CLK_INFRA_CA57SEL>,
> + <&apmixedsys CLK_APMIXED_MAINPLL>;
> + clock-names = "cpu", "intermediate";
> + };
> +
> + cpu3: cpu@101 {
> + device_type = "cpu";
> + compatible = "arm,cortex-a57";
> + reg = <0x101>;
> + enable-method = "psci";
> + cpu-idle-states = <&CPU_SLEEP_0>;
> + clocks = <&infracfg CLK_INFRA_CA57SEL>,
> + <&apmixedsys CLK_APMIXED_MAINPLL>;
> + clock-names = "cpu", "intermediate";
> + };
> +
> + &cpu0 {
> + proc-supply = <&mt6397_vpca15_reg>;
> + };
> +
> + &cpu1 {
> + proc-supply = <&mt6397_vpca15_reg>;
> + };
> +
> + &cpu2 {
> + proc-supply = <&da9211_vcpu_reg>;
> + sram-supply = <&mt6397_vsramca7_reg>;
> + };
> +
> + &cpu3 {
> + proc-supply = <&da9211_vcpu_reg>;
> + sram-supply = <&mt6397_vsramca7_reg>;
> + };
> --
> 1.9.1
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-pm" 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-07-09 14:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-09 10:27 [PATCH v6 0/4] Add Mediatek MT8173 cpufreq driver Pi-Cheng Chen
2015-07-09 10:27 ` [PATCH v6 1/4] dt-bindings: mediatek: Add MT8173 CPU DVFS clock bindings Pi-Cheng Chen
2015-07-09 14:55 ` Michael Turquette [this message]
2015-07-09 10:27 ` [PATCH v6 3/4] cpufreq: mediatek: Add MT8173 cpufreq driver Pi-Cheng Chen
[not found] ` <1436437661-17606-1-git-send-email-pi-cheng.chen-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2015-07-09 10:27 ` [PATCH v6 2/4] dt-bindings: mediatek: Add MT8173 cpufreq driver bindings Pi-Cheng Chen
2015-07-09 10:32 ` Viresh Kumar
2015-07-09 10:27 ` [PATCH v6 4/4] arm64: dts: mt8173: Add mt8173 cpufreq driver support Pi-Cheng Chen
2015-07-09 10:34 ` [PATCH v6 0/4] Add Mediatek MT8173 cpufreq driver Viresh Kumar
2015-08-02 7:27 ` 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=20150709145551.9112.35610@quantum \
--to=mturquette@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=matthias.bgg@gmail.com \
--cc=pi-cheng.chen@linaro.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;
as well as URLs for NNTP newsgroup(s).