From: Conor Dooley <conor@kernel.org>
To: Inochi Amaoto <inochiama@outlook.com>
Cc: Chen Wang <unicorn_wang@outlook.com>,
Chao Wei <chao.wei@sophgo.com>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Jisheng Zhang <jszhang@kernel.org>,
devicetree@vger.kernel.org, linux-riscv@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 6/7] riscv: dts: sophgo: add initial CV1812H SoC device tree
Date: Thu, 12 Oct 2023 10:41:45 +0100 [thread overview]
Message-ID: <20231012-gratuity-siesta-b9e06b11be43@spud> (raw)
In-Reply-To: <IA1PR20MB4953AD81686694CEA4F5FC6ABBCDA@IA1PR20MB4953.namprd20.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 2422 bytes --]
On Tue, Oct 10, 2023 at 03:53:54PM +0800, Inochi Amaoto wrote:
> >On 2023/10/9 19:26, Inochi Amaoto wrote:
> >> Add initial device tree for the CV1812H RISC-V SoC by SOPHGO.
> >>
> >> Signed-off-by: Inochi Amaoto <inochiama@outlook.com>
> >> ---
> >> arch/riscv/boot/dts/sophgo/cv1812h.dtsi | 36 +++++++++++++++++++++++++
> >> 1 file changed, 36 insertions(+)
> >> create mode 100644 arch/riscv/boot/dts/sophgo/cv1812h.dtsi
> >>
> >> diff --git a/arch/riscv/boot/dts/sophgo/cv1812h.dtsi b/arch/riscv/boot/dts/sophgo/cv1812h.dtsi
> >> new file mode 100644
> >> index 000000000000..3864d34b0100
> >> --- /dev/null
> >> +++ b/arch/riscv/boot/dts/sophgo/cv1812h.dtsi
> >> @@ -0,0 +1,36 @@
> >> +// SPDX-License-Identifier: (GPL-2.0 OR MIT)
> >> +/*
> >> + * Copyright (C) 2023 Inochi Amaoto <inochiama@outlook.com>
> >> + */
> >> +
> >> +#include <dt-bindings/interrupt-controller/irq.h>
> >This include is not required.
>
> Thx.
I can drop this include on application. Is the rest of the series okay
with you Chen Wang?
Thanks,
Conor.
>
> >> +#include "cv180x.dtsi"
> >> +
> >> +/ {
> >> + compatible = "sophgo,cv1812h";
> >> +
> >> + memory@80000000 {
> >> + device_type = "memory";
> >> + reg = <0x80000000 0x10000000>;
> >> + };
> >What's this defined for , I see this is different against cv1800b.
>
> CV1812h have a embedded 256MB RAM. The cv1800b is 64MB, This is why the
> size is different. I write this node here because the RAM is embedded
> and fixed size, and leave it in the board DT is unnecessary.
>
> >> +
> >> + soc {
> >> + interrupt-parent = <&plic>;
> >> +
> >> + plic: interrupt-controller@70000000 {
> >> + compatible = "sophgo,cv1812h-plic", "thead,c900-plic";
> >> + reg = <0x70000000 0x4000000>;
> >> + interrupts-extended = <&cpu0_intc 11>, <&cpu0_intc 9>;
> >> + interrupt-controller;
> >> + #address-cells = <0>;
> >> + #interrupt-cells = <2>;
> >> + riscv,ndev = <101>;
> >> + };
> >> +
> >> + clint: timer@74000000 {
> >> + compatible = "sophgo,cv1812h-clint", "thead,c900-clint";
> >> + reg = <0x74000000 0x10000>;
> >> + interrupts-extended = <&cpu0_intc 3>, <&cpu0_intc 7>;
> >> + };
> >> + };
> >> +};
> >> --
> >> 2.42.0
> >>
> >
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-10-12 9:41 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-09 11:25 [PATCH v2 0/7] Add Huashan Pi board support Inochi Amaoto
2023-10-09 11:26 ` [PATCH v2 1/7] dt-bindings: interrupt-controller: Add SOPHGO CV1812H plic Inochi Amaoto
2023-10-09 11:30 ` Krzysztof Kozlowski
[not found] ` <20231009112642.477337-1-inochiama@outlook.com>
2023-10-09 11:26 ` [PATCH v2 2/7] dt-bindings: timer: Add SOPHGO CV1812H clint Inochi Amaoto
2023-10-09 11:30 ` Krzysztof Kozlowski
2023-10-09 11:26 ` [PATCH v2 3/7] dt-bindings: riscv: Add SOPHGO Huashan Pi board compatibles Inochi Amaoto
2023-10-09 11:30 ` Krzysztof Kozlowski
2023-10-09 11:26 ` [PATCH v2 4/7] riscv: dts: sophgo: Separate common devices from cv1800b soc Inochi Amaoto
2023-10-12 10:46 ` Chen Wang
2023-10-12 12:50 ` Chen Wang
2023-10-13 9:08 ` Conor Dooley
2023-10-13 9:50 ` [PATCH v2 6/7] riscv: dts: sophgo: add initial CV1812H SoC device tree Inochi Amaoto
2023-10-13 9:52 ` [PATCH v2 6/7] riscv: dts: sophgo: Separate common devices from cv1800b soc Inochi Amaoto
2023-10-13 13:27 ` Conor Dooley
2023-10-13 22:36 ` [PATCH v2 4/7] " Inochi Amaoto
2023-10-14 9:04 ` Jisheng Zhang
2023-10-14 9:28 ` Conor Dooley
2023-10-09 11:26 ` [PATCH v2 5/7] riscv: dts: sophgo: cv180x: Add gpio devices Inochi Amaoto
2023-10-12 12:52 ` Chen Wang
2023-10-09 11:26 ` [PATCH v2 6/7] riscv: dts: sophgo: add initial CV1812H SoC device tree Inochi Amaoto
2023-10-10 7:21 ` Chen Wang
2023-10-10 7:53 ` Inochi Amaoto
2023-10-12 9:41 ` Conor Dooley [this message]
2023-10-12 13:02 ` Chen Wang
2023-10-09 11:26 ` [PATCH v2 7/7] riscv: dts: sophgo: add Huashan Pi board " Inochi Amaoto
2023-10-12 12:53 ` Chen Wang
2023-10-12 13:20 ` [PATCH v2 0/7] Add Huashan Pi board support Jisheng Zhang
2023-10-13 8:48 ` Krzysztof Kozlowski
2023-10-13 8:55 ` Inochi Amaoto
2023-10-13 9:00 ` Inochi Amaoto
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=20231012-gratuity-siesta-b9e06b11be43@spud \
--to=conor@kernel.org \
--cc=aou@eecs.berkeley.edu \
--cc=chao.wei@sophgo.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=inochiama@outlook.com \
--cc=jszhang@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 \
--cc=unicorn_wang@outlook.com \
/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