From: <Padmarao.Begari@microchip.com>
To: <conor@kernel.org>, <Conor.Dooley@microchip.com>
Cc: <linux-riscv@lists.infradead.org>, <devicetree@vger.kernel.org>,
<paul.walmsley@sifive.com>, <palmer@dabbelt.com>,
<aou@eecs.berkeley.edu>, <linux-kernel@vger.kernel.org>,
<Daire.McNamara@microchip.com>, <robh+dt@kernel.org>,
<krzysztof.kozlowski+dt@linaro.org>
Subject: Re: [RFC] riscv: dts: microchip: add OPPs to mpfs
Date: Wed, 26 Oct 2022 05:54:16 +0000 [thread overview]
Message-ID: <bf68f00675b5cbc6ba8099496ddb68ed20e84f05.camel@microchip.com> (raw)
In-Reply-To: <20221024193647.1089769-1-conor@kernel.org>
Hi Conor,
> On Mon, 2022-10-24 at 20:36 +0100, Conor Dooley wrote:
>
> From: Conor Dooley <conor.dooley@microchip.com>
>
> The U-Boot dts for mpfs defines three OPPs which are missing from the
> Linux dts. For ease of synchronisation of the two, add the missing
> OPPs
> to the Linux dt too.
>
> CC: Padmarao Begari <padmarao.begari@microchip.com>
> Signed-off-by: Conor Dooley <conor.dooley@microchip.com>
> ---
>
> Hey Padmarao,
> I've been trying to pick off the bits that're different between the
> Linux
> & U-Boot dts. Do you remember why we added OPPs to the U-Boot dts but
> didn't propagate them elsewhere?
>
Initially We added OPPs to the Linux dts for the CPU Frequency and
Voltage scaling while bringing up the Linux on an Emulation Platform
and the Icicle Kit for PolarFire SoC and same dts used for the U-Boot
but the U-Boot dts upstreamed first.
Regards
Padmarao
> arch/riscv/boot/dts/microchip/mpfs.dtsi | 23 +++++++++++++++++++++++
> 1 file changed, 23 insertions(+)
>
> diff --git a/arch/riscv/boot/dts/microchip/mpfs.dtsi
> b/arch/riscv/boot/dts/microchip/mpfs.dtsi
> index 0a9bb84af438..9d9ff7174341 100644
> --- a/arch/riscv/boot/dts/microchip/mpfs.dtsi
> +++ b/arch/riscv/boot/dts/microchip/mpfs.dtsi
> @@ -23,6 +23,7 @@ cpu0: cpu@0 {
> reg = <0>;
> riscv,isa = "rv64imac";
> clocks = <&clkcfg CLK_CPU>;
> + operating-points-v2 = <&cluster0_opps>;
> status = "disabled";
>
> cpu0_intc: interrupt-controller {
> @@ -51,6 +52,7 @@ cpu1: cpu@1 {
> clocks = <&clkcfg CLK_CPU>;
> tlb-split;
> next-level-cache = <&cctrllr>;
> + operating-points-v2 = <&cluster0_opps>;
> status = "okay";
>
> cpu1_intc: interrupt-controller {
> @@ -79,6 +81,7 @@ cpu2: cpu@2 {
> clocks = <&clkcfg CLK_CPU>;
> tlb-split;
> next-level-cache = <&cctrllr>;
> + operating-points-v2 = <&cluster0_opps>;
> status = "okay";
>
> cpu2_intc: interrupt-controller {
> @@ -107,6 +110,7 @@ cpu3: cpu@3 {
> clocks = <&clkcfg CLK_CPU>;
> tlb-split;
> next-level-cache = <&cctrllr>;
> + operating-points-v2 = <&cluster0_opps>;
> status = "okay";
>
> cpu3_intc: interrupt-controller {
> @@ -136,6 +140,7 @@ cpu4: cpu@4 {
> tlb-split;
> next-level-cache = <&cctrllr>;
> status = "okay";
> + operating-points-v2 = <&cluster0_opps>;
> cpu4_intc: interrupt-controller {
> #interrupt-cells = <1>;
> compatible = "riscv,cpu-intc";
> @@ -166,6 +171,24 @@ core4 {
> };
> };
> };
> +
> + cluster0_opps: opp-table {
> + compatible = "operating-points-v2";
> + opp-shared;
> +
> + opp-600000000 {
> + opp-hz = /bits/ 64 <600000000>;
> + opp-microvolt = <1100000>;
> + };
> + opp-300000000 {
> + opp-hz = /bits/ 64 <300000000>;
> + opp-microvolt = <950000>;
> + };
> + opp-150000000 {
> + opp-hz = /bits/ 64 <150000000>;
> + opp-microvolt = <750000>;
> + };
> + };
> };
>
> refclk: mssrefclk {
> --
> 2.38.0
>
next prev parent reply other threads:[~2022-10-26 5:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-24 19:36 [RFC] riscv: dts: microchip: add OPPs to mpfs Conor Dooley
2022-10-26 5:54 ` Padmarao.Begari [this message]
2022-10-26 6:33 ` Conor Dooley
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=bf68f00675b5cbc6ba8099496ddb68ed20e84f05.camel@microchip.com \
--to=padmarao.begari@microchip.com \
--cc=Conor.Dooley@microchip.com \
--cc=Daire.McNamara@microchip.com \
--cc=aou@eecs.berkeley.edu \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=robh+dt@kernel.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).