From: Alex Elder <elder@riscstar.com>
To: dlan@gentoo.org, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, vkoul@kernel.org, kishon@kernel.org
Cc: ziyao@disroot.org, aurelien@aurel32.net, johannes@erdfelt.com,
pjw@kernel.org, palmer@dabbelt.com, aou@eecs.berkeley.edu,
alex@ghiti.fr, p.zabel@pengutronix.de, guodong@riscstar.com,
devicetree@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 v7 0/5] Introduce SpacemiT K1 PCIe phy support
Date: Fri, 19 Dec 2025 09:28:08 -0600 [thread overview]
Message-ID: <ee9ce749-5ee4-41d9-8d1b-7b3b507b2217@riscstar.com> (raw)
In-Reply-To: <20251218151235.454997-1-elder@riscstar.com>
On 12/18/25 9:12 AM, Alex Elder wrote:
> This series introduces a PHY driver to support PCIe on the SpacemiT K1
> SoC. The PCIe controller 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 PCIe controller driver that was included in earlier versions of
> this series has already been accepted upstream:
> a812b09a6b599 ("dt-bindings: pci: spacemit: Introduce PCIe host
> controller")
> ff64e078e45fa ("PCI: spacemit: Add SpacemiT PCIe host driver")
> However this series still includes devicetree patches to enable the
> PCIe controller (along with the PHYs).
>
> The patches that remain in version 7 of this series are unchanged;
> they are simply rebased on top of Linux v6.19-rc1. The first two
> patches are the DT bindings for the PCIe and combo PCIe/USB PHY.
> The third is the PHY driver, and the last two are devicetree updates
> to enable the PCIe controller and PHYs.
>
> -Alex
Yixun pointed out that I neglected to provide a summary of the
change history in this message. Here is a link to version 6,
which summarizes prior history. My explanation for v7 indicates
what changed since v6.
https://lore.kernel.org/lkml/20251113214540.2623070-1-elder@riscstar.com/
He also said I neglected to add Neil's Reviewed-by tag, which
is true. That is here:
https://lore.kernel.org/all/ba532f8d-a452-40e5-af46-b58b89f70a92@linaro.org/
Sorry about that. If requested, I can send an otherwise
unchanged version 8, but for now I'll assume that's not
necessary.
-Alex
> Alex Elder (5):
> dt-bindings: phy: spacemit: Add SpacemiT PCIe/combo PHY
> dt-bindings: phy: spacemit: Introduce PCIe PHY
> phy: spacemit: Introduce PCIe/combo PHY
> riscv: dts: spacemit: Add a PCIe regulator
> riscv: dts: spacemit: PCIe and PHY-related updates
>
> .../bindings/phy/spacemit,k1-combo-phy.yaml | 114 +++
> .../bindings/phy/spacemit,k1-pcie-phy.yaml | 71 ++
> .../boot/dts/spacemit/k1-bananapi-f3.dts | 44 ++
> arch/riscv/boot/dts/spacemit/k1-pinctrl.dtsi | 33 +
> arch/riscv/boot/dts/spacemit/k1.dtsi | 176 +++++
> drivers/phy/Kconfig | 11 +
> drivers/phy/Makefile | 1 +
> drivers/phy/phy-spacemit-k1-pcie.c | 670 ++++++++++++++++++
> 8 files changed, 1120 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/phy/spacemit,k1-combo-phy.yaml
> create mode 100644 Documentation/devicetree/bindings/phy/spacemit,k1-pcie-phy.yaml
> create mode 100644 drivers/phy/phy-spacemit-k1-pcie.c
>
>
> base-commit: 8f0b4cce4481fb22653697cced8d0d04027cb1e8
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2025-12-19 15:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-18 15:12 [PATCH v7 0/5] Introduce SpacemiT K1 PCIe phy support Alex Elder
2025-12-18 15:12 ` [PATCH v7 1/5] dt-bindings: phy: spacemit: Add SpacemiT PCIe/combo PHY Alex Elder
2025-12-18 15:12 ` [PATCH v7 2/5] dt-bindings: phy: spacemit: Introduce PCIe PHY Alex Elder
2025-12-18 15:12 ` [PATCH v7 3/5] phy: spacemit: Introduce PCIe/combo PHY Alex Elder
2025-12-18 15:12 ` [PATCH v7 4/5] riscv: dts: spacemit: Add a PCIe regulator Alex Elder
2025-12-19 12:20 ` Yixun Lan
2025-12-18 15:12 ` [PATCH v7 5/5] riscv: dts: spacemit: PCIe and PHY-related updates Alex Elder
2025-12-19 12:21 ` Yixun Lan
2025-12-19 12:19 ` [PATCH v7 0/5] Introduce SpacemiT K1 PCIe phy support Yixun Lan
2025-12-19 15:28 ` Alex Elder [this message]
2025-12-23 17:44 ` (subset) " Vinod Koul
2025-12-24 2:43 ` Yixun Lan
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=ee9ce749-5ee4-41d9-8d1b-7b3b507b2217@riscstar.com \
--to=elder@riscstar.com \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=aurelien@aurel32.net \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlan@gentoo.org \
--cc=guodong@riscstar.com \
--cc=johannes@erdfelt.com \
--cc=kishon@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=linux-riscv@lists.infradead.org \
--cc=p.zabel@pengutronix.de \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=robh@kernel.org \
--cc=spacemit@lists.linux.dev \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox