From: <Conor.Dooley@microchip.com>
To: <icenowy@aosc.io>, <kernel@esmil.dk>, <robh+dt@kernel.org>,
<krzysztof.kozlowski+dt@linaro.org>, <paul.walmsley@sifive.com>,
<palmer@dabbelt.com>, <aou@eecs.berkeley.edu>,
<anup@brainfault.org>, <Conor.Dooley@microchip.com>
Cc: <devicetree@vger.kernel.org>, <linux-riscv@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v1 2/2] riscv: dts: starfive: add the missing monitor core
Date: Wed, 13 Jul 2022 15:16:45 +0000 [thread overview]
Message-ID: <224a7ec2-62ca-a8a5-ff36-37de4186e05e@microchip.com> (raw)
In-Reply-To: <2303fc91e5110f22fc9ea6008fa4bbc77c1bdb13.camel@aosc.io>
On 13/07/2022 16:15, Icenowy Zheng wrote:
> 在 2022-07-11星期一的 19:43 +0100,Conor Dooley写道:
>> From: Conor Dooley <conor.dooley@microchip.com>
>>
>> The JH7100 has a 32 bit monitor core that is missing from the device
>> tree. Add it (and its cpu-map entry) to more accurately reflect the
>> actual topology of the SoC.
>>
>> Signed-off-by: Conor Dooley <conor.dooley@microchip.com>
>> ---
>> arch/riscv/boot/dts/starfive/jh7100.dtsi | 21 +++++++++++++++++++++
>> 1 file changed, 21 insertions(+)
>>
>> diff --git a/arch/riscv/boot/dts/starfive/jh7100.dtsi
>> b/arch/riscv/boot/dts/starfive/jh7100.dtsi
>> index c617a61e26e2..92fce5b66d3d 100644
>> --- a/arch/riscv/boot/dts/starfive/jh7100.dtsi
>> +++ b/arch/riscv/boot/dts/starfive/jh7100.dtsi
>> @@ -67,6 +67,23 @@ cpu1_intc: interrupt-controller {
>> };
>> };
>>
>> + E24: cpu@2 {
>> + compatible = "sifive,e24", "riscv";
>
> Oh, by the way "sifive,e24" is not a documented compatible in the DT
> binding.
>
> If you really want to add it here, you need to add the compatible
> string to the DT binding first.
Check patch 1/2.
>
>> + reg = <2>;
>> + device_type = "cpu";
>> + i-cache-block-size = <32>;
>> + i-cache-sets = <256>;
>> + i-cache-size = <16384>;
>> + riscv,isa = "rv32imafc";
>> + status = "disabled";
>> +
>> + cpu2_intc: interrupt-controller {
>> + compatible = "riscv,cpu-intc";
>> + interrupt-controller;
>> + #interrupt-cells = <1>;
>> + };
>> + };
>> +
>> cpu-map {
>> cluster0 {
>> core0 {
>> @@ -76,6 +93,10 @@ core0 {
>> core1 {
>> cpu = <&U74_1>;
>> };
>> +
>> + core2 {
>> + cpu = <&E24>;
>> + };
>> };
>> };
>> };
>
>
next prev parent reply other threads:[~2022-07-13 15:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-11 18:43 [PATCH v1 0/2] Add the JH7100's Monitor Core Conor Dooley
2022-07-11 18:43 ` [PATCH v1 1/2] dt-bindings: riscv: document the sifive e24 Conor Dooley
2022-07-12 8:08 ` Krzysztof Kozlowski
2022-07-11 18:43 ` [PATCH v1 2/2] riscv: dts: starfive: add the missing monitor core Conor Dooley
2022-07-12 10:06 ` Emil Renner Berthing
2022-07-13 14:26 ` Icenowy Zheng
2022-07-13 14:55 ` Conor.Dooley
2022-07-13 15:02 ` Icenowy Zheng
2022-07-13 15:09 ` Conor.Dooley
2022-07-13 15:12 ` Icenowy Zheng
2022-07-13 15:21 ` Conor.Dooley
2022-07-13 15:26 ` Icenowy Zheng
2022-07-13 15:36 ` Conor.Dooley
2022-07-13 15:15 ` Icenowy Zheng
2022-07-13 15:16 ` Conor.Dooley [this message]
2022-07-13 15:20 ` Icenowy Zheng
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=224a7ec2-62ca-a8a5-ff36-37de4186e05e@microchip.com \
--to=conor.dooley@microchip.com \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=devicetree@vger.kernel.org \
--cc=icenowy@aosc.io \
--cc=kernel@esmil.dk \
--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).