From: Johannes Erdfelt <johannes@erdfelt.com>
To: Alex Elder <elder@riscstar.com>
Cc: dlan@gentoo.org, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, vkoul@kernel.org, kishon@kernel.org,
bhelgaas@google.com, lpieralisi@kernel.org,
kwilczynski@kernel.org, mani@kernel.org, ziyao@disroot.org,
aurelien@aurel32.net, mayank.rana@oss.qualcomm.com,
qiang.yu@oss.qualcomm.com, shradha.t@samsung.com,
inochiama@gmail.com, pjw@kernel.org, palmer@dabbelt.com,
aou@eecs.berkeley.edu, alex@ghiti.fr, p.zabel@pengutronix.de,
christian.bruel@foss.st.com, thippeswamy.havalige@amd.com,
krishna.chundru@oss.qualcomm.com, guodong@riscstar.com,
devicetree@vger.kernel.org, linux-pci@vger.kernel.org,
linux-phy@lists.infradead.org, spacemit@lists.linux.dev,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 0/7] Introduce SpacemiT K1 PCIe phy and host controller
Date: Thu, 13 Nov 2025 22:05:05 -0800 [thread overview]
Message-ID: <20251114060505.GA25077@sventech.com> (raw)
In-Reply-To: <20251113214540.2623070-1-elder@riscstar.com>
On Thu, Nov 13, 2025, Alex Elder <elder@riscstar.com> wrote:
> This series introduces a PHY driver and a PCIe driver to support PCIe
> on the SpacemiT K1 SoC. The PCIe implementation is derived from a
> Synopsys DesignWare PCIe IP. The PHY driver supports one combination
> PCIe/USB PHY as well as two PCIe-only PHYs. The combo PHY port uses
> one PCIe lane, and the other two ports each have two lanes. All PCIe
> ports operate at 5 GT/second.
>
> The PCIe PHYs must be configured using a value that can only be
> determined using the combo PHY, operating in PCIe mode. To allow
> that PHY to be used for USB, the needed calibration step is performed
> by the PHY driver automatically at probe time. Once this step is done,
> the PHY can be used for either PCIe or USB.
>
> The driver supports 256 MSIs, and initially does not support PCI INTx
> interrupts. The hardware does not support MSI-X.
>
> Version 6 of this series addresses a few comments from Christophe
> Jaillet, and improves a workaround that disables ASPM L1. The two
> people who had reported errors on earlier versions of this code have
> confirmed their NVMe devices now work when configured with the default
> RISC-V kernel configuration.
I've tested this latest patchset on my Orange Pi RV2 board. This
patchset now works with the Intel 600p NVME SSD I had previously had
troublw with. Thanks!
Tested-by: Johannes Erdfelt <johannes@erdfelt.com>
JE
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
WARNING: multiple messages have this Message-ID (diff)
From: Johannes Erdfelt <johannes@erdfelt.com>
To: Alex Elder <elder@riscstar.com>
Cc: dlan@gentoo.org, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, vkoul@kernel.org, kishon@kernel.org,
bhelgaas@google.com, lpieralisi@kernel.org,
kwilczynski@kernel.org, mani@kernel.org, ziyao@disroot.org,
aurelien@aurel32.net, mayank.rana@oss.qualcomm.com,
qiang.yu@oss.qualcomm.com, shradha.t@samsung.com,
inochiama@gmail.com, pjw@kernel.org, palmer@dabbelt.com,
aou@eecs.berkeley.edu, alex@ghiti.fr, p.zabel@pengutronix.de,
christian.bruel@foss.st.com, thippeswamy.havalige@amd.com,
krishna.chundru@oss.qualcomm.com, guodong@riscstar.com,
devicetree@vger.kernel.org, linux-pci@vger.kernel.org,
linux-phy@lists.infradead.org, spacemit@lists.linux.dev,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 0/7] Introduce SpacemiT K1 PCIe phy and host controller
Date: Thu, 13 Nov 2025 22:05:05 -0800 [thread overview]
Message-ID: <20251114060505.GA25077@sventech.com> (raw)
In-Reply-To: <20251113214540.2623070-1-elder@riscstar.com>
On Thu, Nov 13, 2025, Alex Elder <elder@riscstar.com> wrote:
> This series introduces a PHY driver and a PCIe driver to support PCIe
> on the SpacemiT K1 SoC. The PCIe implementation is derived from a
> Synopsys DesignWare PCIe IP. The PHY driver supports one combination
> PCIe/USB PHY as well as two PCIe-only PHYs. The combo PHY port uses
> one PCIe lane, and the other two ports each have two lanes. All PCIe
> ports operate at 5 GT/second.
>
> The PCIe PHYs must be configured using a value that can only be
> determined using the combo PHY, operating in PCIe mode. To allow
> that PHY to be used for USB, the needed calibration step is performed
> by the PHY driver automatically at probe time. Once this step is done,
> the PHY can be used for either PCIe or USB.
>
> The driver supports 256 MSIs, and initially does not support PCI INTx
> interrupts. The hardware does not support MSI-X.
>
> Version 6 of this series addresses a few comments from Christophe
> Jaillet, and improves a workaround that disables ASPM L1. The two
> people who had reported errors on earlier versions of this code have
> confirmed their NVMe devices now work when configured with the default
> RISC-V kernel configuration.
I've tested this latest patchset on my Orange Pi RV2 board. This
patchset now works with the Intel 600p NVME SSD I had previously had
troublw with. Thanks!
Tested-by: Johannes Erdfelt <johannes@erdfelt.com>
JE
WARNING: multiple messages have this Message-ID (diff)
From: Johannes Erdfelt <johannes@erdfelt.com>
To: Alex Elder <elder@riscstar.com>
Cc: dlan@gentoo.org, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, vkoul@kernel.org, kishon@kernel.org,
bhelgaas@google.com, lpieralisi@kernel.org,
kwilczynski@kernel.org, mani@kernel.org, ziyao@disroot.org,
aurelien@aurel32.net, mayank.rana@oss.qualcomm.com,
qiang.yu@oss.qualcomm.com, shradha.t@samsung.com,
inochiama@gmail.com, pjw@kernel.org, palmer@dabbelt.com,
aou@eecs.berkeley.edu, alex@ghiti.fr, p.zabel@pengutronix.de,
christian.bruel@foss.st.com, thippeswamy.havalige@amd.com,
krishna.chundru@oss.qualcomm.com, guodong@riscstar.com,
devicetree@vger.kernel.org, linux-pci@vger.kernel.org,
linux-phy@lists.infradead.org, spacemit@lists.linux.dev,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 0/7] Introduce SpacemiT K1 PCIe phy and host controller
Date: Thu, 13 Nov 2025 22:05:05 -0800 [thread overview]
Message-ID: <20251114060505.GA25077@sventech.com> (raw)
In-Reply-To: <20251113214540.2623070-1-elder@riscstar.com>
On Thu, Nov 13, 2025, Alex Elder <elder@riscstar.com> wrote:
> This series introduces a PHY driver and a PCIe driver to support PCIe
> on the SpacemiT K1 SoC. The PCIe implementation is derived from a
> Synopsys DesignWare PCIe IP. The PHY driver supports one combination
> PCIe/USB PHY as well as two PCIe-only PHYs. The combo PHY port uses
> one PCIe lane, and the other two ports each have two lanes. All PCIe
> ports operate at 5 GT/second.
>
> The PCIe PHYs must be configured using a value that can only be
> determined using the combo PHY, operating in PCIe mode. To allow
> that PHY to be used for USB, the needed calibration step is performed
> by the PHY driver automatically at probe time. Once this step is done,
> the PHY can be used for either PCIe or USB.
>
> The driver supports 256 MSIs, and initially does not support PCI INTx
> interrupts. The hardware does not support MSI-X.
>
> Version 6 of this series addresses a few comments from Christophe
> Jaillet, and improves a workaround that disables ASPM L1. The two
> people who had reported errors on earlier versions of this code have
> confirmed their NVMe devices now work when configured with the default
> RISC-V kernel configuration.
I've tested this latest patchset on my Orange Pi RV2 board. This
patchset now works with the Intel 600p NVME SSD I had previously had
troublw with. Thanks!
Tested-by: Johannes Erdfelt <johannes@erdfelt.com>
JE
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2025-11-14 6:05 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-13 21:45 [PATCH v6 0/7] Introduce SpacemiT K1 PCIe phy and host controller Alex Elder
2025-11-13 21:45 ` Alex Elder
2025-11-13 21:45 ` Alex Elder
2025-11-13 21:45 ` [PATCH v6 1/7] dt-bindings: phy: spacemit: Add SpacemiT PCIe/combo PHY Alex Elder
2025-11-13 21:45 ` Alex Elder
2025-11-13 21:45 ` Alex Elder
2025-11-13 21:45 ` [PATCH v6 2/7] dt-bindings: phy: spacemit: Introduce PCIe PHY Alex Elder
2025-11-13 21:45 ` Alex Elder
2025-11-13 21:45 ` Alex Elder
2025-11-13 21:45 ` [PATCH v6 3/7] dt-bindings: pci: spacemit: Introduce PCIe host controller Alex Elder
2025-11-13 21:45 ` Alex Elder
2025-11-13 21:45 ` [PATCH v6 4/7] phy: spacemit: Introduce PCIe/combo PHY Alex Elder
2025-11-13 21:45 ` Alex Elder
2025-11-13 21:45 ` Alex Elder
2025-11-18 8:56 ` Neil Armstrong
2025-11-18 8:56 ` Neil Armstrong
2025-11-18 8:56 ` Neil Armstrong
2025-11-18 14:11 ` Alex Elder
2025-11-18 14:11 ` Alex Elder
2025-11-18 14:11 ` Alex Elder
2025-12-01 13:49 ` Alex Elder
2025-12-01 13:49 ` Alex Elder
2025-12-01 13:49 ` Alex Elder
2025-11-13 21:45 ` [PATCH v6 5/7] PCI: spacemit: Add SpacemiT PCIe host driver Alex Elder
2025-11-13 21:45 ` Alex Elder
2025-11-17 13:01 ` Vitor Soares
2025-11-17 13:01 ` Vitor Soares
2025-11-17 13:17 ` Manivannan Sadhasivam
2025-11-17 13:17 ` Manivannan Sadhasivam
2025-11-13 21:45 ` [PATCH v6 6/7] riscv: dts: spacemit: Add a PCIe regulator Alex Elder
2025-11-13 21:45 ` Alex Elder
2025-11-13 21:45 ` [PATCH v6 7/7] riscv: dts: spacemit: PCIe and PHY-related updates Alex Elder
2025-11-13 21:45 ` Alex Elder
2025-11-14 5:34 ` [PATCH v6 0/7] Introduce SpacemiT K1 PCIe phy and host controller Aurelien Jarno
2025-11-14 5:34 ` Aurelien Jarno
2025-11-14 5:34 ` Aurelien Jarno
2025-11-14 6:05 ` Johannes Erdfelt [this message]
2025-11-14 6:05 ` Johannes Erdfelt
2025-11-14 6:05 ` Johannes Erdfelt
2025-11-15 4:21 ` Jason Montleon
2025-11-15 4:21 ` Jason Montleon
2025-11-15 4:21 ` Jason Montleon
2025-11-17 17:12 ` Alex Elder
2025-11-17 17:12 ` Alex Elder
2025-11-17 17:12 ` Alex Elder
2025-11-17 14:55 ` (subset) " Manivannan Sadhasivam
2025-11-17 14:55 ` Manivannan Sadhasivam
2025-11-17 14:55 ` Manivannan Sadhasivam
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=20251114060505.GA25077@sventech.com \
--to=johannes@erdfelt.com \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=aurelien@aurel32.net \
--cc=bhelgaas@google.com \
--cc=christian.bruel@foss.st.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlan@gentoo.org \
--cc=elder@riscstar.com \
--cc=guodong@riscstar.com \
--cc=inochiama@gmail.com \
--cc=kishon@kernel.org \
--cc=krishna.chundru@oss.qualcomm.com \
--cc=krzk+dt@kernel.org \
--cc=kwilczynski@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=linux-riscv@lists.infradead.org \
--cc=lpieralisi@kernel.org \
--cc=mani@kernel.org \
--cc=mayank.rana@oss.qualcomm.com \
--cc=p.zabel@pengutronix.de \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=qiang.yu@oss.qualcomm.com \
--cc=robh@kernel.org \
--cc=shradha.t@samsung.com \
--cc=spacemit@lists.linux.dev \
--cc=thippeswamy.havalige@amd.com \
--cc=vkoul@kernel.org \
--cc=ziyao@disroot.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.