From: Conor Dooley <conor@kernel.org>
To: Junhui Liu <junhui.liu@pigmoral.tech>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Alexandre Ghiti <alex@ghiti.fr>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Thomas Gleixner <tglx@linutronix.de>,
Samuel Holland <samuel.holland@sifive.com>,
Anup Patel <anup@brainfault.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jirislaby@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Palmer Dabbelt <palmer@sifive.com>,
linux-riscv@lists.infradead.org, linux-serial@vger.kernel.org
Subject: Re: [PATCH RFC 08/10] riscv: dts: Add initial Anlogic DR1V90 SoC device tree
Date: Tue, 22 Jul 2025 16:21:21 +0100 [thread overview]
Message-ID: <20250722-proposal-gothic-e0c3725e0874@spud> (raw)
In-Reply-To: <20250721-dr1v90-basic-dt-v1-8-5740c5199c47@pigmoral.tech>
[-- Attachment #1: Type: text/plain, Size: 1009 bytes --]
On Mon, Jul 21, 2025 at 11:46:14PM +0800, Junhui Liu wrote:
> + cpus {
> + #address-cells = <1>;
> + #size-cells = <0>;
> + timebase-frequency = <800000000>;
> +
> + cpu@0 {
> + compatible = "nuclei,ux900", "riscv";
> + device_type = "cpu";
> + reg = <0>;
> + riscv,isa = "rv64imafdc";
> + riscv,isa-base = "rv64i";
> + riscv,isa-extensions = "i", "m", "a", "f", "d", "c", "zba", "zbb", "zbc",
> + "zbkc", "zbs", "zicntr", "zicsr", "zifencei",
> + "zihintpause", "zihpm";
Why do riscv,isa and riscv,isa-extensions differ?
If riscv,isa is not even accurate, why not just remove it entirely?
> + i-cache-block-size = <64>;
> + i-cache-size = <32768>;
> + i-cache-sets = <256>;
> + d-cache-block-size = <64>;
> + d-cache-size = <32768>;
> + d-cache-sets = <256>;
> + mmu-type = "riscv,sv39";
> +
> + cpu0_intc: interrupt-controller {
> + compatible = "riscv,cpu-intc";
> + interrupt-controller;
> + #interrupt-cells = <1>;
> + };
> + };
> + };
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2025-07-22 15:21 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-21 15:46 [PATCH RFC 00/10] riscv: Add initial support for Anlogic DR1V90 Junhui Liu
2025-07-21 15:46 ` [PATCH RFC 01/10] dt-bindings: vendor-prefixes: Add Anlogic, Milianke and Nuclei Junhui Liu
2025-07-22 7:27 ` Krzysztof Kozlowski
2025-07-21 15:46 ` [PATCH RFC 02/10] dt-bindings: riscv: Add Nuclei UX900 compatibles Junhui Liu
2025-07-21 15:46 ` [PATCH RFC 03/10] dt-bindings: riscv: Add Anlogic DR1V90 Junhui Liu
2025-07-22 7:28 ` Krzysztof Kozlowski
2025-07-21 15:46 ` [PATCH RFC 04/10] dt-bindings: timer: Add Anlogic DR1V90 CLINT Junhui Liu
2025-07-25 22:29 ` Rob Herring (Arm)
2025-07-21 15:46 ` [PATCH RFC 05/10] dt-bindings: interrupt-controller: Add Anlogic DR1V90 PLIC Junhui Liu
2025-07-21 15:46 ` [PATCH RFC 06/10] dt-bindings: serial: snps-dw-apb-uart: Add Anlogic DR1V90 uart Junhui Liu
2025-07-25 22:30 ` Rob Herring (Arm)
2025-07-21 15:46 ` [PATCH RFC 07/10] riscv: Add Anlogic SoC famly Kconfig support Junhui Liu
2025-07-22 7:29 ` Krzysztof Kozlowski
2025-07-22 11:27 ` Junhui Liu
2025-07-21 15:46 ` [PATCH RFC 08/10] riscv: dts: Add initial Anlogic DR1V90 SoC device tree Junhui Liu
2025-07-22 15:21 ` Conor Dooley [this message]
2025-07-23 2:37 ` Junhui Liu
2025-07-21 15:46 ` [PATCH RFC 09/10] riscv: dts: anlogic: Add Milianke MLKPAI FS01 board Junhui Liu
2025-07-22 7:31 ` Krzysztof Kozlowski
2025-07-22 11:46 ` Junhui Liu
2025-07-21 15:46 ` [PATCH RFC 10/10] riscv: defconfig: Enable Anlogic SoC Junhui Liu
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=20250722-proposal-gothic-e0c3725e0874@spud \
--to=conor@kernel.org \
--cc=alex@ghiti.fr \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=conor+dt@kernel.org \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=junhui.liu@pigmoral.tech \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-serial@vger.kernel.org \
--cc=palmer@dabbelt.com \
--cc=palmer@sifive.com \
--cc=paul.walmsley@sifive.com \
--cc=robh@kernel.org \
--cc=samuel.holland@sifive.com \
--cc=tglx@linutronix.de \
/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