From: Sebastian Reichel <sebastian.reichel@collabora.com>
To: linux-phy@lists.infradead.org, linux-rockchip@lists.infradead.org
Cc: "Jingoo Han" <jingoohan1@gmail.com>,
"Gustavo Pimentel" <gustavo.pimentel@synopsys.com>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Vinod Koul" <vkoul@kernel.org>,
"Kishon Vijay Abraham I" <kishon@kernel.org>,
"Krzysztof Wilczyński" <kw@linux.com>,
"Rob Herring" <robh@kernel.org>,
"Serge Semin" <fancer.lancer@gmail.com>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Heiko Stuebner" <heiko@sntech.de>,
"Shawn Lin" <shawn.lin@rock-chips.com>,
"Simon Xue" <xxm@rock-chips.com>,
"John Clark" <inindev@gmail.com>, "Qu Wenruo" <wqu@suse.com>,
devicetree@vger.kernel.org, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
"Sebastian Reichel" <sebastian.reichel@collabora.com>,
kernel@collabora.com
Subject: [PATCH v1 0/2] RK3588 PCIe3 support
Date: Fri, 14 Jul 2023 19:53:29 +0200 [thread overview]
Message-ID: <20230714175331.112923-1-sebastian.reichel@collabora.com> (raw)
Hi,
This adds PCIe v3 support for RK3588. The series has been tested with
Rockchip RK3588 EVB1 and a PCIe wlan card, I will also test Rock 5B
next week. The series depends on the PCIe v2 series [0].
Note, that the PCIe3 PHY driver is currently missing bifurcation
support for RK3588. Thus after this series only PCIe3x4 is usable
(in aggregated x4 mode) without adding support for the PHY's
"rockchip,pcie30-phymode" DT property, which allows configuring
how the lanes are distributed. Apparently this seems to be the
most common configuration. Both EVB1 and Rock 5B use it, so I
cannot test anything else anyways.
[0] https://lore.kernel.org/all/20230713171851.73052-1-sebastian.reichel@collabora.com/
-- Sebastian
Sebastian Reichel (2):
dt-bindings: phy: rockchip: add RK3588 PCIe v3 phy
arm64: dts: rockchip: rk3588: add PCIe3 support
.../bindings/phy/rockchip,pcie3-phy.yaml | 33 ++++-
arch/arm64/boot/dts/rockchip/rk3588.dtsi | 128 ++++++++++++++++++
2 files changed, 156 insertions(+), 5 deletions(-)
--
2.40.1
next reply other threads:[~2023-07-14 17:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-14 17:53 Sebastian Reichel [this message]
2023-07-14 17:53 ` [PATCH v1 1/2] dt-bindings: phy: rockchip: add RK3588 PCIe v3 phy Sebastian Reichel
2023-07-15 10:29 ` Conor Dooley
2023-07-14 17:53 ` [PATCH v1 2/2] arm64: dts: rockchip: rk3588: add PCIe3 support Sebastian Reichel
2023-07-15 16:45 ` Serge Semin
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=20230714175331.112923-1-sebastian.reichel@collabora.com \
--to=sebastian.reichel@collabora.com \
--cc=bhelgaas@google.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=fancer.lancer@gmail.com \
--cc=gustavo.pimentel@synopsys.com \
--cc=heiko@sntech.de \
--cc=inindev@gmail.com \
--cc=jingoohan1@gmail.com \
--cc=kernel@collabora.com \
--cc=kishon@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kw@linux.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=lpieralisi@kernel.org \
--cc=robh@kernel.org \
--cc=shawn.lin@rock-chips.com \
--cc=vkoul@kernel.org \
--cc=wqu@suse.com \
--cc=xxm@rock-chips.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;
as well as URLs for NNTP newsgroup(s).