Devicetree
 help / color / mirror / Atom feed
From: Manivannan Sadhasivam <manivannan.sadhasivam@oss.qualcomm.com>
To: "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>,
	"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>,
	"Jia Wang" <wangjia@ultrarisc.com>
Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
	linux-pci@vger.kernel.org, devicetree@vger.kernel.org,
	Conor Dooley <conor.dooley@microchip.com>,
	Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
Subject: Re: (subset) [PATCH v4 0/3] riscv: Add PCIe support for UltraRISC DP1000 SoC
Date: Mon, 11 May 2026 14:01:42 +0530	[thread overview]
Message-ID: <177848830296.12802.14978169328629266559.b4-ty@b4> (raw)
In-Reply-To: <20260427-ultrarisc-pcie-v4-0-98935f6cdfb5@ultrarisc.com>


On Mon, 27 Apr 2026 09:32:09 +0800, Jia Wang wrote:
> This patch series adds PCIe controller support for the UltraRISC DP1000 SoC.
> The DP1000 is an 8-core 64-bit RISC-V SoC based on UltraRISC CP100 cores,
> supporting RV64GCBHX ISA with Hardware Virtualization and RISC-V H(v1.0)
> Extension.
> 
> The PCIe controller is based on Synopsys DesignWare PCIe IP.
> This series adds:
> - Patch 1 adds the basic SoC family Kconfig support for UltraRISC platforms.
> - Patch 2 adds the device tree bindings documentation for the PCIe controller.
> - Patch 3 introduces the PCIe host controller driver.
> 
> [...]

Applied, thanks!

[2/3] dt-bindings: PCI: Add UltraRISC DP1000 PCIe controller
      commit: 09b78d6ec24624c2f5192dbf0c6e05cad61c529d
[3/3] PCI: ultrarisc: Add UltraRISC DP1000 PCIe Root Complex driver
      commit: 34f9bebe1cf573cf9735a71c1d484b57f65e5314

Best regards,
-- 
Manivannan Sadhasivam <mani@kernel.org>


      parent reply	other threads:[~2026-05-11  8:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-27  1:32 [PATCH v4 0/3] riscv: Add PCIe support for UltraRISC DP1000 SoC Jia Wang
2026-04-27  1:32 ` [PATCH v4 1/3] riscv: add UltraRISC SoC family Kconfig support Jia Wang
2026-04-27  1:32 ` [PATCH v4 2/3] dt-bindings: PCI: Add UltraRISC DP1000 PCIe controller Jia Wang
2026-04-27  1:32 ` [PATCH v4 3/3] PCI: ultrarisc: Add UltraRISC DP1000 PCIe Root Complex driver Jia Wang
2026-05-11  6:12   ` Jia Wang
2026-05-11  8:31 ` Manivannan Sadhasivam [this message]

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=177848830296.12802.14978169328629266559.b4-ty@b4 \
    --to=manivannan.sadhasivam@oss.qualcomm.com \
    --cc=alex@ghiti.fr \
    --cc=aou@eecs.berkeley.edu \
    --cc=bhelgaas@google.com \
    --cc=conor+dt@kernel.org \
    --cc=conor.dooley@microchip.com \
    --cc=devicetree@vger.kernel.org \
    --cc=jingoohan1@gmail.com \
    --cc=krzk+dt@kernel.org \
    --cc=krzysztof.kozlowski@oss.qualcomm.com \
    --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=palmer@dabbelt.com \
    --cc=pjw@kernel.org \
    --cc=robh@kernel.org \
    --cc=wangjia@ultrarisc.com \
    --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