From: Daniel Palmer <daniel@0x0f.com> To: devicetree@vger.kernel.org, linux-clk@vger.kernel.org, soc@kernel.org, sboyd@kernel.org Cc: linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, w@1wt.eu, Daniel Palmer <daniel@0x0f.com> Subject: [PATCH 8/8] ARM: mstar: Add OPP table for mercury5 Date: Tue, 23 Feb 2021 15:18:30 +0900 [thread overview] Message-ID: <20210223061830.1913700-9-daniel@0x0f.com> (raw) In-Reply-To: <20210223061830.1913700-1-daniel@0x0f.com> Add an OPP table for mercury5 so that cpu frequency scaling can happen. Signed-off-by: Daniel Palmer <daniel@0x0f.com> --- arch/arm/boot/dts/mstar-mercury5.dtsi | 36 +++++++++++++++++++++++++++ 1 file changed, 36 insertions(+) diff --git a/arch/arm/boot/dts/mstar-mercury5.dtsi b/arch/arm/boot/dts/mstar-mercury5.dtsi index a7d0dd9d6132..80a19bd23c9c 100644 --- a/arch/arm/boot/dts/mstar-mercury5.dtsi +++ b/arch/arm/boot/dts/mstar-mercury5.dtsi @@ -6,6 +6,42 @@ #include "mstar-v7.dtsi" +/ { + cpu0_opp_table: opp_table0 { + compatible = "operating-points-v2"; + opp-shared; + + opp-100000000 { + opp-hz = /bits/ 64 <100000000>; + opp-microvolt = <800000 800000 850000>; + clock-latency-ns = <300000>; + }; + + opp-200000000 { + opp-hz = /bits/ 64 <200000000>; + opp-microvolt = <850000 850000 880000>; + clock-latency-ns = <300000>; + }; + + opp-400000000 { + opp-hz = /bits/ 64 <400000000>; + opp-microvolt = <880000 880000 890000>; + clock-latency-ns = <300000>; + }; + opp-600000000 { + opp-hz = /bits/ 64 <600000000>; + opp-microvolt = <900000 900000 1000000>; + clock-latency-ns = <300000>; + }; + + opp-800000000 { + opp-hz = /bits/ 64 <800000000>; + opp-microvolt = <900000 900000 1000000>; + clock-latency-ns = <300000>; + }; + }; +}; + &imi { reg = <0xa0000000 0x20000>; }; -- 2.30.0.rc2
WARNING: multiple messages have this Message-ID (diff)
From: Daniel Palmer <daniel@0x0f.com> To: devicetree@vger.kernel.org, linux-clk@vger.kernel.org, soc@kernel.org, sboyd@kernel.org Cc: Daniel Palmer <daniel@0x0f.com>, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, w@1wt.eu Subject: [PATCH 8/8] ARM: mstar: Add OPP table for mercury5 Date: Tue, 23 Feb 2021 15:18:30 +0900 [thread overview] Message-ID: <20210223061830.1913700-9-daniel@0x0f.com> (raw) Message-ID: <20210223061830.ygo3b-C2s5XcKY66d-q3fuQlR_IwQ0-Xeu4T47xPC0w@z> (raw) In-Reply-To: <20210223061830.1913700-1-daniel@0x0f.com> Add an OPP table for mercury5 so that cpu frequency scaling can happen. Signed-off-by: Daniel Palmer <daniel@0x0f.com> --- arch/arm/boot/dts/mstar-mercury5.dtsi | 36 +++++++++++++++++++++++++++ 1 file changed, 36 insertions(+) diff --git a/arch/arm/boot/dts/mstar-mercury5.dtsi b/arch/arm/boot/dts/mstar-mercury5.dtsi index a7d0dd9d6132..80a19bd23c9c 100644 --- a/arch/arm/boot/dts/mstar-mercury5.dtsi +++ b/arch/arm/boot/dts/mstar-mercury5.dtsi @@ -6,6 +6,42 @@ #include "mstar-v7.dtsi" +/ { + cpu0_opp_table: opp_table0 { + compatible = "operating-points-v2"; + opp-shared; + + opp-100000000 { + opp-hz = /bits/ 64 <100000000>; + opp-microvolt = <800000 800000 850000>; + clock-latency-ns = <300000>; + }; + + opp-200000000 { + opp-hz = /bits/ 64 <200000000>; + opp-microvolt = <850000 850000 880000>; + clock-latency-ns = <300000>; + }; + + opp-400000000 { + opp-hz = /bits/ 64 <400000000>; + opp-microvolt = <880000 880000 890000>; + clock-latency-ns = <300000>; + }; + opp-600000000 { + opp-hz = /bits/ 64 <600000000>; + opp-microvolt = <900000 900000 1000000>; + clock-latency-ns = <300000>; + }; + + opp-800000000 { + opp-hz = /bits/ 64 <800000000>; + opp-microvolt = <900000 900000 1000000>; + clock-latency-ns = <300000>; + }; + }; +}; + &imi { reg = <0xa0000000 0x20000>; }; -- 2.30.0.rc2 _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-02-23 6:25 UTC|newest] Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-02-23 6:18 [PATCH 0/8] ARM: mstar: cpupll Daniel Palmer 2021-02-23 6:18 ` Daniel Palmer 2021-02-23 6:18 ` [PATCH 1/8] dt-bindings: clk: mstar msc313 cpupll binding description Daniel Palmer 2021-02-23 6:18 ` Daniel Palmer 2021-02-23 19:34 ` Rob Herring 2021-02-23 19:34 ` Rob Herring 2021-02-26 11:31 ` Daniel Palmer 2021-02-26 11:31 ` Daniel Palmer 2021-02-26 11:31 ` Daniel Palmer 2021-04-01 11:03 ` Arnd Bergmann 2021-04-01 11:03 ` Arnd Bergmann 2021-04-01 11:03 ` Arnd Bergmann 2021-04-01 11:07 ` Daniel Palmer 2021-04-01 11:07 ` Daniel Palmer 2021-04-01 11:07 ` Daniel Palmer 2021-02-23 6:18 ` [PATCH 2/8] clk: mstar: msc313 cpupll clk driver Daniel Palmer 2021-02-23 6:18 ` Daniel Palmer 2021-02-23 6:18 ` [PATCH 3/8] ARM: mstar: Add cpupll to base dtsi Daniel Palmer 2021-02-23 6:18 ` Daniel Palmer 2021-02-23 6:18 ` [PATCH 4/8] ARM: mstar: Link cpupll to cpu Daniel Palmer 2021-02-23 6:18 ` Daniel Palmer 2021-02-23 6:18 ` [PATCH 5/8] ARM: mstar: Link cpupll to second core Daniel Palmer 2021-02-23 6:18 ` Daniel Palmer 2021-02-23 6:18 ` [PATCH 6/8] ARM: mstar: Add OPP table for infinity Daniel Palmer 2021-02-23 6:18 ` Daniel Palmer 2021-02-23 6:18 ` [PATCH 7/8] ARM: mstar: Add OPP table for infinity3 Daniel Palmer 2021-02-23 6:18 ` Daniel Palmer 2021-02-23 6:18 ` Daniel Palmer [this message] 2021-02-23 6:18 ` [PATCH 8/8] ARM: mstar: Add OPP table for mercury5 Daniel Palmer
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=20210223061830.1913700-9-daniel@0x0f.com \ --to=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=sboyd@kernel.org \ --cc=soc@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: 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.