From: Jia Wang <wangjia@ultrarisc.com>
To: Conor Dooley <conor@kernel.org>
Cc: "Jia Wang" <wangjia@ultrarisc.com>,
"Paul Walmsley" <pjw@kernel.org>,
"Palmer Dabbelt" <palmer@dabbelt.com>,
"Albert Ou" <aou@eecs.berkeley.edu>,
"Alexandre Ghiti" <alex@ghiti.fr>,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Krzysztof Wilczyński" <kwilczynski@kernel.org>,
"Manivannan Sadhasivam" <mani@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Jingoo Han" <jingoohan1@gmail.com>,
"Xincheng Zhang" <zhangxincheng@ultrarisc.com>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-pci@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 1/4] riscv: add UltraRISC SoC family Kconfig support
Date: Tue, 17 Mar 2026 14:46:24 +0800 [thread overview]
Message-ID: <177372998464.49340.13796019002628537253.b4-reply@b4> (raw)
In-Reply-To: <20260316-powdery-unbundle-b1166d13f53b@spud>
On 2026-03-16 14:39 +0000, Conor Dooley wrote:
> On Mon, Mar 16, 2026 at 03:06:57PM +0800, Jia Wang wrote:
> > The first SoC in the UltraRISC series is UR-DP1000, containing octa
> > UltraRISC C100 cores.
> >
> > Signed-off-by: Jia Wang <wangjia@ultrarisc.com>
> > ---
> > arch/riscv/Kconfig.socs | 10 ++++++++++
> > 1 file changed, 10 insertions(+)
> >
> > diff --git a/arch/riscv/Kconfig.socs b/arch/riscv/Kconfig.socs
> > index d621b85dd63b..f49d3ccaacde 100644
> > --- a/arch/riscv/Kconfig.socs
> > +++ b/arch/riscv/Kconfig.socs
> > @@ -84,6 +84,16 @@ config ARCH_THEAD
> > help
> > This enables support for the RISC-V based T-HEAD SoCs.
> >
> > +config ARCH_ULTRARISC
> > + bool "UltraRISC RISC-V SoCs"
> > + depends on MMU && !XIP_KERNEL
>
> Why do you depend on "MMU && !XIP_KERNEL"?
>
Hi Conor,
Thanks for the review.
The dependency on "MMU" was added conservatively, but the DP1000 hardware
does not strictly require MMU. I will remove this dependency in the
next version of the patch.
The "!XIP_KERNEL" dependency is retained because the platform does not
support executing the kernel directly from storage, so the kernel
must be loaded into RAM before execution.
Best regards,
Jia
> > + help
> > + This enables support for UltraRISC SoC platform hardware,
> > + including boards based on the UR-DP1000.
> > + UR-DP1000 is an 8-core 64-bit RISC-V SoC that supports
> > + the RV64GCBHX ISA. It supports Hardware Virtualization
> > + and RISC-V RV64 ISA H(v1.0) Extension.
> > +
> > config ARCH_VIRT
> > bool "QEMU Virt Machine"
> > select POWER_RESET
> >
> > --
> > 2.34.1
> >
next prev parent reply other threads:[~2026-03-17 6:46 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-16 7:06 [PATCH 0/4] riscv: Add PCIe support for UltraRISC DP1000 SoC Jia Wang via B4 Relay
2026-03-16 7:06 ` [PATCH 1/4] riscv: add UltraRISC SoC family Kconfig support Jia Wang via B4 Relay
2026-03-16 14:39 ` Conor Dooley
2026-03-17 6:46 ` Jia Wang [this message]
2026-03-17 13:02 ` Conor Dooley
2026-03-19 9:28 ` Jia Wang
2026-03-16 7:06 ` [PATCH 2/4] MAINTAINERS: Add entry for the UltraRISC DP1000 PCIe controller driver and its DT binding Jia Wang via B4 Relay
2026-03-16 7:06 ` [PATCH 3/4] dt-bindings: PCI: Add UltraRISC DP1000 PCIe controller Jia Wang via B4 Relay
2026-03-16 8:21 ` Rob Herring (Arm)
2026-03-19 10:09 ` Jia Wang
2026-03-16 10:05 ` Krzysztof Kozlowski
2026-03-20 6:15 ` Jia Wang
2026-03-17 4:56 ` Yao Zi
2026-03-20 6:18 ` Jia Wang
2026-03-16 7:07 ` [PATCH 4/4] PCI: dwc: Add UltraRISC DP1000 PCIe rc driver Jia Wang via B4 Relay
2026-03-16 20:49 ` Bjorn Helgaas
2026-03-20 9:33 ` Jia Wang
2026-03-17 5:32 ` Yao Zi
2026-03-20 9:37 ` Jia Wang
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=177372998464.49340.13796019002628537253.b4-reply@b4 \
--to=wangjia@ultrarisc.com \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=bhelgaas@google.com \
--cc=conor+dt@kernel.org \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jingoohan1@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=kwilczynski@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=lpieralisi@kernel.org \
--cc=mani@kernel.org \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=robh@kernel.org \
--cc=zhangxincheng@ultrarisc.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