From: Paul Walmsley <pjw@kernel.org>
To: Guodong Xu <guodong@riscstar.com>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Paul Walmsley <pjw@kernel.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Alexandre Ghiti <alex@ghiti.fr>, Yixun Lan <dlan@gentoo.org>,
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>,
Lubomir Rintel <lkundrak@v3.sk>, Yangyu Chen <cyy@cyyself.name>,
Paul Walmsley <paul.walmsley@sifive.com>,
Conor Dooley <conor@kernel.org>,
Heinrich Schuchardt <xypron.glpk@gmx.de>,
Kevin Meng Zhang <zhangmeng.kevin@linux.spacemit.com>,
Andrew Jones <ajones@ventanamicro.com>,
devicetree@vger.kernel.org, linux-riscv@lists.infradead.org,
linux-kernel@vger.kernel.org, spacemit@lists.linux.dev,
linux-serial@vger.kernel.org,
Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>,
Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
Subject: Re: [PATCH v4 01/11] dt-bindings: riscv: add SpacemiT X100 CPU compatible
Date: Wed, 14 Jan 2026 16:27:56 -0700 (MST) [thread overview]
Message-ID: <006317ae-dec7-a893-372b-c68afe35863e@kernel.org> (raw)
In-Reply-To: <20260110-k3-basic-dt-v4-1-d492f3a30ffa@riscstar.com>
On Sat, 10 Jan 2026, Guodong Xu wrote:
> Add compatible string for the SpacemiT X100 core. [1]
>
> The X100 is a 64-bit RVA23-compliant RISC-V core from SpacemiT. X100
> supports the RISC-V vector and hypervisor extensions and all mandatory
> extersions as required by the RVA23U64 and RVA23S64 profiles, per the
> definition in 'RVA23 Profile, Version 1.0'. [2]
>
> >From a microarchieture viewpoint, the X100 features a 4-issue
> out-of-order pipeline.
>
> X100 is used in SpacemiT K3 SoC.
>
> Link: https://www.spacemit.com/en/spacemit-x100-core/ [1]
> Link: https://docs.riscv.org/reference/profiles/rva23/_attachments/rva23-profile.pdf [2]
> Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
> Reviewed-by: Yixun Lan <dlan@gentoo.org>
> Reviewed-by: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
> Signed-off-by: Guodong Xu <guodong@riscstar.com>
(just for completeness, since I acked the older version)
Acked-by: Paul Walmsley <pjw@kernel.org>
- Paul
next prev parent reply other threads:[~2026-01-14 23:28 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-10 5:18 [PATCH v4 00/11] riscv: spacemit: Add SpacemiT K3 SoC and K3 Pico-ITX board Guodong Xu
2026-01-10 5:18 ` [PATCH v4 01/11] dt-bindings: riscv: add SpacemiT X100 CPU compatible Guodong Xu
2026-01-14 23:27 ` Paul Walmsley [this message]
2026-01-10 5:18 ` [PATCH v4 02/11] dt-bindings: timer: add SpacemiT K3 CLINT Guodong Xu
2026-01-10 5:18 ` [PATCH v4 03/11] dt-bindings: interrupt-controller: add SpacemiT K3 APLIC Guodong Xu
2026-01-10 5:18 ` [PATCH v4 04/11] dt-bindings: interrupt-controller: add SpacemiT K3 IMSIC Guodong Xu
2026-01-10 5:18 ` [PATCH v4 05/11] dt-bindings: riscv: spacemit: add K3 and Pico-ITX board bindings Guodong Xu
2026-01-10 11:55 ` Yixun Lan
2026-01-12 21:37 ` Conor Dooley
2026-01-10 5:18 ` [PATCH v4 06/11] dt-bindings: riscv: Add B ISA extension description Guodong Xu
2026-01-12 21:41 ` Conor Dooley
2026-01-13 2:44 ` Guodong Xu
2026-01-10 5:18 ` [PATCH v4 07/11] dt-bindings: riscv: Add descriptions for Za64rs, Ziccamoa, Ziccif, and Zicclsm Guodong Xu
2026-01-12 21:38 ` Conor Dooley
2026-01-10 5:18 ` [PATCH v4 08/11] dt-bindings: riscv: Add Ssccptr, Sscounterenw, Sstvala, Sstvecd, Ssu64xl Guodong Xu
2026-01-12 21:39 ` Conor Dooley
2026-01-10 5:18 ` [PATCH v4 09/11] dt-bindings: riscv: Add Sha and its comprised extensions Guodong Xu
2026-01-12 21:40 ` Conor Dooley
2026-01-10 5:18 ` [PATCH v4 10/11] riscv: dts: spacemit: add initial device tree of SpacemiT K3 SoC Guodong Xu
2026-01-10 10:00 ` Inochi Amaoto
2026-01-10 11:05 ` Yixun Lan
2026-01-12 8:14 ` Guodong Xu
2026-01-12 7:42 ` Maud Spierings
2026-01-12 7:59 ` Guodong Xu
2026-01-10 5:18 ` [PATCH v4 11/11] riscv: dts: spacemit: add SpacemiT K3 Pico-ITX board device tree Guodong Xu
2026-01-10 9:57 ` Yixun Lan
2026-01-12 8:57 ` Guodong Xu
2026-01-12 21:45 ` [PATCH v4 00/11] riscv: spacemit: Add SpacemiT K3 SoC and K3 Pico-ITX board Conor Dooley
2026-01-13 0:21 ` Yixun Lan
2026-01-13 22:17 ` Conor Dooley
2026-01-14 2:14 ` Yixun Lan
2026-01-14 20:26 ` Rob Herring
2026-01-13 2:51 ` Guodong Xu
2026-01-13 22:25 ` (subset) " 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=006317ae-dec7-a893-372b-c68afe35863e@kernel.org \
--to=pjw@kernel.org \
--cc=ajones@ventanamicro.com \
--cc=alex@ghiti.fr \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=conor+dt@kernel.org \
--cc=conor@kernel.org \
--cc=cyy@cyyself.name \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=dlan@gentoo.org \
--cc=gregkh@linuxfoundation.org \
--cc=guodong@riscstar.com \
--cc=heinrich.schuchardt@canonical.com \
--cc=jirislaby@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski@oss.qualcomm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-serial@vger.kernel.org \
--cc=lkundrak@v3.sk \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=robh@kernel.org \
--cc=samuel.holland@sifive.com \
--cc=spacemit@lists.linux.dev \
--cc=tglx@linutronix.de \
--cc=xypron.glpk@gmx.de \
--cc=zhangmeng.kevin@linux.spacemit.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