devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Romain Perier <romain.perier@gmail.com>
To: Michael Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@kernel.org>,
	linux-clk@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
	Daniel Palmer <daniel@0x0f.com>,
	Romain Perier <romain.perier@gmail.com>,
	Rob Herring <robh+dt@kernel.org>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, Willy Tarreau <w@1wt.eu>
Subject: [PATCH v3 6/9] ARM: mstar: Add OPP table for infinity
Date: Fri, 21 Jan 2022 20:35:41 +0100	[thread overview]
Message-ID: <20220121193544.23231-7-romain.perier@gmail.com> (raw)
In-Reply-To: <20220121193544.23231-1-romain.perier@gmail.com>

From: Daniel Palmer <daniel@0x0f.com>

Add an OPP table for the inifinity chips so
that cpu frequency scaling can happen.

Co-authored-by: Willy Tarreau <w@1wt.eu>
Signed-off-by: Daniel Palmer <daniel@0x0f.com>
---
 arch/arm/boot/dts/mstar-infinity.dtsi | 34 +++++++++++++++++++++++++++
 1 file changed, 34 insertions(+)

diff --git a/arch/arm/boot/dts/mstar-infinity.dtsi b/arch/arm/boot/dts/mstar-infinity.dtsi
index 0bee517797f4..441a917b88ba 100644
--- a/arch/arm/boot/dts/mstar-infinity.dtsi
+++ b/arch/arm/boot/dts/mstar-infinity.dtsi
@@ -8,6 +8,40 @@
 
 #include <dt-bindings/gpio/msc313-gpio.h>
 
+/ {
+	cpu0_opp_table: opp_table0 {
+		compatible = "operating-points-v2";
+		opp-shared;
+
+		opp-240000000 {
+			opp-hz = /bits/ 64 <240000000>;
+			opp-microvolt = <1000000>;
+			clock-latency-ns = <300000>;
+		};
+
+		opp-400000000 {
+			opp-hz = /bits/ 64 <400000000>;
+			opp-microvolt = <1000000>;
+			clock-latency-ns = <300000>;
+		};
+		opp-600000000 {
+			opp-hz = /bits/ 64 <600000000>;
+			opp-microvolt = <1000000>;
+			clock-latency-ns = <300000>;
+		};
+
+		opp-800000000 {
+			opp-hz = /bits/ 64 <800000000>;
+			opp-microvolt = <1000000>;
+			clock-latency-ns = <300000>;
+		};
+	};
+};
+
+&cpu0 {
+	operating-points-v2 = <&cpu0_opp_table>;
+};
+
 &imi {
 	reg = <0xa0000000 0x16000>;
 };
-- 
2.34.1


  parent reply	other threads:[~2022-01-21 19:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-21 19:35 [PATCH v3 0/9] ARM: mstar: cpupll Romain Perier
2022-01-21 19:35 ` [PATCH v3 1/9] dt-bindings: clk: mstar msc313 cpupll binding description Romain Perier
2022-01-21 19:35 ` [PATCH v3 2/9] clk: mstar: msc313 cpupll clk driver Romain Perier
2022-01-21 19:35 ` [PATCH v3 3/9] ARM: mstar: Add cpupll to base dtsi Romain Perier
2022-01-23  5:10   ` Daniel Palmer
2022-01-21 19:35 ` [PATCH v3 4/9] ARM: mstar: Link cpupll to cpu Romain Perier
2022-01-21 19:35 ` [PATCH v3 5/9] ARM: mstar: Link cpupll to second core Romain Perier
2022-01-21 19:35 ` Romain Perier [this message]
2022-01-21 19:35 ` [PATCH v3 7/9] ARM: mstar: Add OPP table for infinity3 Romain Perier
2022-01-21 19:35 ` [PATCH v3 8/9] ARM: mstar: Add OPP table for mercury5 Romain Perier
2022-01-23  5:12   ` Daniel Palmer
2022-01-21 19:35 ` [PATCH v3 9/9] ARM: mstar: Extend opp_table for infinity2m Romain Perier

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=20220121193544.23231-7-romain.perier@gmail.com \
    --to=romain.perier@gmail.com \
    --cc=arnd@arndb.de \
    --cc=daniel@0x0f.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=robh+dt@kernel.org \
    --cc=sboyd@kernel.org \
    --cc=w@1wt.eu \
    /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).