From: k.kozlowski@samsung•com (Krzysztof Kozlowski)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH v4 3/8] ARM: dts: Exynos5420: add CPU OPP properties
Date: Tue, 08 Dec 2015 16:17:00 +0900 [thread overview]
Message-ID: <566683EC.9050806@samsung.com> (raw)
In-Reply-To: <1449512300-17230-4-git-send-email-b.zolnierkie@samsung.com>
On 08.12.2015 03:18, Bartlomiej Zolnierkiewicz wrote:
> From: Thomas Abraham <thomas.ab@samsung•com>
>
> For Exynos5420 platforms, add CPU operating points for
> migrating from Exynos specific cpufreq driver to using
> generic cpufreq driver.
>
> Changes by Bartlomiej:
> - split Exynos5420 support from the original patch
>
> Changes by Ben Gamari:
> - Port to operating-points-v2
>
> Cc: Kukjin Kim <kgene.kim@samsung•com>
> Cc: Doug Anderson <dianders@chromium•org>
> Cc: Javier Martinez Canillas <javier.martinez@collabora•co.uk>
> Cc: Andreas Faerber <afaerber@suse•de>
> Cc: Sachin Kamat <sachin.kamat@linaro•org>
Sachin's address does not work neither.
> Cc: Thomas Abraham <thomas.ab@samsung•com>
Thomas' SoB disappeared.
I see that you directly re-used Thomas' values for voltages and
frequencies. For Exynos5420 we could go down to 200 MHz (for both cores)
but this can be fine-tuned per-board later.
Best regards,
Krzysztof
> Signed-off-by: Ben Gamari <ben@smart-cactus•org>
> Signed-off-by: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung•com>
> ---
> arch/arm/boot/dts/exynos5420.dtsi | 122 ++++++++++++++++++++++++++++++++++++++
> 1 file changed, 122 insertions(+)
>
> diff --git a/arch/arm/boot/dts/exynos5420.dtsi b/arch/arm/boot/dts/exynos5420.dtsi
> index 48a0a55..f8f70a5 100644
> --- a/arch/arm/boot/dts/exynos5420.dtsi
> +++ b/arch/arm/boot/dts/exynos5420.dtsi
> @@ -50,6 +50,116 @@
> usbdrdphy1 = &usbdrd_phy1;
> };
>
> + cpu0_opp_table: opp_table0 {
> + compatible = "operating-points-v2";
> + opp-shared;
> + opp00 at 1800000000 {
> + opp-hz = /bits/ 64 <1800000000>;
> + opp-microvolt = <1250000>;
> + clock-latency-ns = <140000>;
> + };
> + opp01 at 1700000000 {
> + opp-hz = /bits/ 64 <1700000000>;
> + opp-microvolt = <1212500>;
> + clock-latency-ns = <140000>;
> + };
> + opp02 at 1600000000 {
> + opp-hz = /bits/ 64 <1600000000>;
> + opp-microvolt = <1175000>;
> + clock-latency-ns = <140000>;
> + };
> + opp03 at 1500000000 {
> + opp-hz = /bits/ 64 <1500000000>;
> + opp-microvolt = <1137500>;
> + clock-latency-ns = <140000>;
> + };
> + opp04 at 1400000000 {
> + opp-hz = /bits/ 64 <1400000000>;
> + opp-microvolt = <1112500>;
> + clock-latency-ns = <140000>;
> + };
> + opp05 at 1300000000 {
> + opp-hz = /bits/ 64 <1300000000>;
> + opp-microvolt = <1062500>;
> + clock-latency-ns = <140000>;
> + };
> + opp06 at 1200000000 {
> + opp-hz = /bits/ 64 <1200000000>;
> + opp-microvolt = <1037500>;
> + clock-latency-ns = <140000>;
> + };
> + opp07 at 1100000000 {
> + opp-hz = /bits/ 64 <1100000000>;
> + opp-microvolt = <1012500>;
> + clock-latency-ns = <140000>;
> + };
> + opp08 at 1000000000 {
> + opp-hz = /bits/ 64 <1000000000>;
> + opp-microvolt = < 987500>;
> + clock-latency-ns = <140000>;
> + };
> + opp09 at 900000000 {
> + opp-hz = /bits/ 64 <900000000>;
> + opp-microvolt = < 962500>;
> + clock-latency-ns = <140000>;
> + };
> + opp10 at 800000000 {
> + opp-hz = /bits/ 64 <800000000>;
> + opp-microvolt = < 937500>;
> + clock-latency-ns = <140000>;
> + };
> + opp11 at 700000000 {
> + opp-hz = /bits/ 64 <700000000>;
> + opp-microvolt = < 912500>;
> + clock-latency-ns = <140000>;
> + };
> + };
> +
> + cpu1_opp_table: opp_table1 {
> + compatible = "operating-points-v2";
> + opp-shared;
> + opp00 at 1300000000 {
> + opp-hz = /bits/ 64 <1300000000>;
> + opp-microvolt = <1275000>;
> + clock-latency-ns = <140000>;
> + };
> + opp01 at 1200000000 {
> + opp-hz = /bits/ 64 <1200000000>;
> + opp-microvolt = <1212500>;
> + clock-latency-ns = <140000>;
> + };
> + opp02 at 1100000000 {
> + opp-hz = /bits/ 64 <1100000000>;
> + opp-microvolt = <1162500>;
> + clock-latency-ns = <140000>;
> + };
> + opp03 at 1000000000 {
> + opp-hz = /bits/ 64 <1000000000>;
> + opp-microvolt = <1112500>;
> + clock-latency-ns = <140000>;
> + };
> + opp04 at 900000000 {
> + opp-hz = /bits/ 64 <900000000>;
> + opp-microvolt = <1062500>;
> + clock-latency-ns = <140000>;
> + };
> + opp05 at 800000000 {
> + opp-hz = /bits/ 64 <800000000>;
> + opp-microvolt = <1025000>;
> + clock-latency-ns = <140000>;
> + };
> + opp06 at 700000000 {
> + opp-hz = /bits/ 64 <700000000>;
> + opp-microvolt = <975000>;
> + clock-latency-ns = <140000>;
> + };
> + opp07 at 600000000 {
> + opp-hz = /bits/ 64 <600000000>;
> + opp-microvolt = <937500>;
> + clock-latency-ns = <140000>;
> + };
> + };
> +
> cpus {
> #address-cells = <1>;
> #size-cells = <0>;
> @@ -58,8 +168,11 @@
> device_type = "cpu";
> compatible = "arm,cortex-a15";
> reg = <0x0>;
> + clocks = <&clock CLK_ARM_CLK>;
> + clock-names = "cpu-cluster.0";
> clock-frequency = <1800000000>;
> cci-control-port = <&cci_control1>;
> + operating-points-v2 = <&cpu0_opp_table>;
> };
>
> cpu1: cpu at 1 {
> @@ -68,6 +181,7 @@
> reg = <0x1>;
> clock-frequency = <1800000000>;
> cci-control-port = <&cci_control1>;
> + operating-points-v2 = <&cpu0_opp_table>;
> };
>
> cpu2: cpu at 2 {
> @@ -76,6 +190,7 @@
> reg = <0x2>;
> clock-frequency = <1800000000>;
> cci-control-port = <&cci_control1>;
> + operating-points-v2 = <&cpu0_opp_table>;
> };
>
> cpu3: cpu at 3 {
> @@ -84,14 +199,18 @@
> reg = <0x3>;
> clock-frequency = <1800000000>;
> cci-control-port = <&cci_control1>;
> + operating-points-v2 = <&cpu0_opp_table>;
> };
>
> cpu4: cpu at 100 {
> device_type = "cpu";
> compatible = "arm,cortex-a7";
> reg = <0x100>;
> + clocks = <&clock CLK_KFC_CLK>;
> + clock-names = "cpu-cluster.1";
> clock-frequency = <1000000000>;
> cci-control-port = <&cci_control0>;
> + operating-points-v2 = <&cpu1_opp_table>;
> };
>
> cpu5: cpu at 101 {
> @@ -100,6 +219,7 @@
> reg = <0x101>;
> clock-frequency = <1000000000>;
> cci-control-port = <&cci_control0>;
> + operating-points-v2 = <&cpu1_opp_table>;
> };
>
> cpu6: cpu at 102 {
> @@ -108,6 +228,7 @@
> reg = <0x102>;
> clock-frequency = <1000000000>;
> cci-control-port = <&cci_control0>;
> + operating-points-v2 = <&cpu1_opp_table>;
> };
>
> cpu7: cpu at 103 {
> @@ -116,6 +237,7 @@
> reg = <0x103>;
> clock-frequency = <1000000000>;
> cci-control-port = <&cci_control0>;
> + operating-points-v2 = <&cpu1_opp_table>;
> };
> };
>
>
next prev parent reply other threads:[~2015-12-08 7:17 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-07 18:18 [PATCH v4 0/8] cpufreq: add generic cpufreq driver support for Exynos542x/5800 platforms Bartlomiej Zolnierkiewicz
2015-12-07 18:18 ` [PATCH v4 1/8] ARM: dts: Exynos542x/5800: add cluster regulator supply properties Bartlomiej Zolnierkiewicz
2015-12-08 6:48 ` Krzysztof Kozlowski
2015-12-08 10:16 ` Markus Reichl
2015-12-07 18:18 ` [PATCH v4 2/8] clk: samsung: exynos5420: add cpu clock configuration data and instantiate cpu clock Bartlomiej Zolnierkiewicz
2015-12-07 18:18 ` [PATCH v4 3/8] ARM: dts: Exynos5420: add CPU OPP properties Bartlomiej Zolnierkiewicz
2015-12-08 6:28 ` Viresh Kumar
2015-12-08 7:17 ` Krzysztof Kozlowski [this message]
2015-12-07 18:18 ` [PATCH v4 4/8] ARM: Exynos: use generic cpufreq driver for Exynos5420 Bartlomiej Zolnierkiewicz
2015-12-08 7:36 ` Krzysztof Kozlowski
2015-12-10 14:18 ` Bartlomiej Zolnierkiewicz
2015-12-11 1:13 ` Krzysztof Kozlowski
2015-12-07 18:18 ` [PATCH v4 5/8] clk: samsung: exynos5422/5800: fix cpu clock configuration data Bartlomiej Zolnierkiewicz
2015-12-07 18:18 ` [PATCH v4 6/8] ARM: dts: Exynos5800: fix CPU OPP Bartlomiej Zolnierkiewicz
2015-12-08 8:07 ` Krzysztof Kozlowski
2015-12-07 18:18 ` [PATCH v4 7/8] ARM: dts: Exynos5422: fix OPP tables Bartlomiej Zolnierkiewicz
2015-12-08 8:13 ` Krzysztof Kozlowski
2015-12-08 13:41 ` Javier Martinez Canillas
2015-12-09 0:34 ` Krzysztof Kozlowski
2015-12-09 2:19 ` Javier Martinez Canillas
2015-12-10 15:57 ` Bartlomiej Zolnierkiewicz
2015-12-07 18:18 ` [PATCH v4 8/8] ARM: Exynos: use generic cpufreq driver for Exynos5422/5800 Bartlomiej Zolnierkiewicz
2015-12-08 6:17 ` [PATCH v4 0/8] cpufreq: add generic cpufreq driver support for Exynos542x/5800 platforms Viresh Kumar
2015-12-08 6:29 ` Viresh Kumar
2015-12-09 13:13 ` Javier Martinez Canillas
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=566683EC.9050806@samsung.com \
--to=k.kozlowski@samsung$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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