From: Qu Wenruo <wqu@suse.com>
To: linux-rockchip@lists.infradead.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org
Cc: sebastian.reichel@collabora.com, heiko@sntech.de
Subject: [PATCH RFC 3/5] drivers: pci: controller: add PCIE controller driver for RK3588
Date: Sat, 4 Feb 2023 16:48:00 +0800 [thread overview]
Message-ID: <5ec4caab3fa934c173bbbfbbf711b1d2429426a7.1675498628.git.wqu@suse.com> (raw)
In-Reply-To: <cover.1675498628.git.wqu@suse.com>
According to the downstream code, the RK3568 and RK3588 share the same
driver.
Downstream code only has extra handling for the following cases:
- RK1808 driver
- Bifurcation handling
- Endpoint handling
All of the above features are not available upstream anyway.
Thus here we only need to add a new compatible string for the existing
driver.
Signed-off-by: Qu Wenruo <wqu@suse.com>
---
drivers/pci/controller/dwc/pcie-dw-rockchip.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/pci/controller/dwc/pcie-dw-rockchip.c b/drivers/pci/controller/dwc/pcie-dw-rockchip.c
index c1e7653e508e..435b717e5bc6 100644
--- a/drivers/pci/controller/dwc/pcie-dw-rockchip.c
+++ b/drivers/pci/controller/dwc/pcie-dw-rockchip.c
@@ -354,6 +354,7 @@ static int rockchip_pcie_probe(struct platform_device *pdev)
static const struct of_device_id rockchip_pcie_of_match[] = {
{ .compatible = "rockchip,rk3568-pcie", },
+ { .compatible = "rockchip,rk3588-pcie", },
{},
};
--
2.39.1
WARNING: multiple messages have this Message-ID (diff)
From: Qu Wenruo <wqu@suse.com>
To: linux-rockchip@lists.infradead.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org
Cc: sebastian.reichel@collabora.com, heiko@sntech.de
Subject: [PATCH RFC 3/5] drivers: pci: controller: add PCIE controller driver for RK3588
Date: Sat, 4 Feb 2023 16:48:00 +0800 [thread overview]
Message-ID: <5ec4caab3fa934c173bbbfbbf711b1d2429426a7.1675498628.git.wqu@suse.com> (raw)
In-Reply-To: <cover.1675498628.git.wqu@suse.com>
According to the downstream code, the RK3568 and RK3588 share the same
driver.
Downstream code only has extra handling for the following cases:
- RK1808 driver
- Bifurcation handling
- Endpoint handling
All of the above features are not available upstream anyway.
Thus here we only need to add a new compatible string for the existing
driver.
Signed-off-by: Qu Wenruo <wqu@suse.com>
---
drivers/pci/controller/dwc/pcie-dw-rockchip.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/pci/controller/dwc/pcie-dw-rockchip.c b/drivers/pci/controller/dwc/pcie-dw-rockchip.c
index c1e7653e508e..435b717e5bc6 100644
--- a/drivers/pci/controller/dwc/pcie-dw-rockchip.c
+++ b/drivers/pci/controller/dwc/pcie-dw-rockchip.c
@@ -354,6 +354,7 @@ static int rockchip_pcie_probe(struct platform_device *pdev)
static const struct of_device_id rockchip_pcie_of_match[] = {
{ .compatible = "rockchip,rk3568-pcie", },
+ { .compatible = "rockchip,rk3588-pcie", },
{},
};
--
2.39.1
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
WARNING: multiple messages have this Message-ID (diff)
From: Qu Wenruo <wqu@suse.com>
To: linux-rockchip@lists.infradead.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org
Cc: sebastian.reichel@collabora.com, heiko@sntech.de
Subject: [PATCH RFC 3/5] drivers: pci: controller: add PCIE controller driver for RK3588
Date: Sat, 4 Feb 2023 16:48:00 +0800 [thread overview]
Message-ID: <5ec4caab3fa934c173bbbfbbf711b1d2429426a7.1675498628.git.wqu@suse.com> (raw)
In-Reply-To: <cover.1675498628.git.wqu@suse.com>
According to the downstream code, the RK3568 and RK3588 share the same
driver.
Downstream code only has extra handling for the following cases:
- RK1808 driver
- Bifurcation handling
- Endpoint handling
All of the above features are not available upstream anyway.
Thus here we only need to add a new compatible string for the existing
driver.
Signed-off-by: Qu Wenruo <wqu@suse.com>
---
drivers/pci/controller/dwc/pcie-dw-rockchip.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/pci/controller/dwc/pcie-dw-rockchip.c b/drivers/pci/controller/dwc/pcie-dw-rockchip.c
index c1e7653e508e..435b717e5bc6 100644
--- a/drivers/pci/controller/dwc/pcie-dw-rockchip.c
+++ b/drivers/pci/controller/dwc/pcie-dw-rockchip.c
@@ -354,6 +354,7 @@ static int rockchip_pcie_probe(struct platform_device *pdev)
static const struct of_device_id rockchip_pcie_of_match[] = {
{ .compatible = "rockchip,rk3568-pcie", },
+ { .compatible = "rockchip,rk3588-pcie", },
{},
};
--
2.39.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-02-04 8:48 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-04 8:47 [PATCH RFC 0/5] arm64: rockchip: enable PCIE3 controller and its phy for Rock5B boards Qu Wenruo
2023-02-04 8:47 ` Qu Wenruo
2023-02-04 8:47 ` Qu Wenruo
2023-02-04 8:47 ` [PATCH RFC 1/5] drivers: phy: rockhip: remove 24M and 25M clock handling for naneng combphy Qu Wenruo
2023-02-04 8:47 ` Qu Wenruo
2023-02-04 8:47 ` Qu Wenruo
2023-02-04 8:47 ` [PATCH RFC 2/5] dt-bindings: pci: controller: add pcie controller binding for RK3588 Qu Wenruo
2023-02-04 8:47 ` Qu Wenruo
2023-02-04 8:47 ` Qu Wenruo
2023-02-06 10:43 ` Krzysztof Kozlowski
2023-02-06 10:43 ` Krzysztof Kozlowski
2023-02-06 10:43 ` Krzysztof Kozlowski
2023-02-04 8:48 ` Qu Wenruo [this message]
2023-02-04 8:48 ` [PATCH RFC 3/5] drivers: pci: controller: add PCIE controller driver " Qu Wenruo
2023-02-04 8:48 ` Qu Wenruo
2023-02-04 8:48 ` [PATCH RFC 4/5] arm64: dts: rockchip: add PCIE3 controller and phy " Qu Wenruo
2023-02-04 8:48 ` Qu Wenruo
2023-02-04 8:48 ` Qu Wenruo
2023-02-04 8:48 ` [PATCH RFC 5/5] arm64: dts: rockchip: enable PCIE3 controller and phy for Rock5B boards Qu Wenruo
2023-02-04 8:48 ` Qu Wenruo
2023-02-04 8:48 ` Qu Wenruo
2023-02-20 18:33 ` [PATCH RFC 0/5] arm64: rockchip: enable PCIE3 controller and its " Piotr Oniszczuk
2023-02-20 18:33 ` Piotr Oniszczuk
2023-02-20 18:33 ` Piotr Oniszczuk
[not found] ` <583D2908-ECED-4226-A6CD-683F0D5BEA71@gmail.com>
2023-02-21 0:14 ` Qu Wenruo
2023-02-21 0:14 ` Qu Wenruo
2023-02-21 0:14 ` Qu Wenruo
2023-02-21 18:03 ` Piotr Oniszczuk
2023-02-21 18:03 ` Piotr Oniszczuk
2023-02-21 18:03 ` Piotr Oniszczuk
2023-02-21 18:55 ` Peter Geis
2023-02-21 18:55 ` Peter Geis
2023-02-21 18:55 ` Peter Geis
2023-02-21 21:45 ` Sebastian Reichel
2023-02-21 21:45 ` Sebastian Reichel
2023-02-21 21:45 ` Sebastian Reichel
2023-02-21 23:39 ` Qu Wenruo
2023-02-21 23:39 ` Qu Wenruo
2023-02-21 23:39 ` Qu Wenruo
2023-02-22 1:25 ` Peter Geis
2023-02-22 1:25 ` Peter Geis
2023-02-22 1:25 ` Peter Geis
[not found] ` <A539A994-7E2C-4B51-8BAB-32AE475607DD@gmail.com>
2023-03-09 12:17 ` Qu Wenruo
2023-03-09 12:17 ` Qu Wenruo
2023-03-09 12:17 ` Qu Wenruo
2023-03-09 13:00 ` Piotr Oniszczuk
2023-03-09 13:00 ` Piotr Oniszczuk
2023-03-09 13:00 ` Piotr Oniszczuk
2023-03-10 0:16 ` Qu Wenruo
2023-03-10 0:16 ` Qu Wenruo
2023-03-10 0:16 ` Qu Wenruo
2023-03-10 8:09 ` Lucas Tanure
2023-03-10 8:09 ` Lucas Tanure
2023-03-10 8:09 ` Lucas Tanure
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=5ec4caab3fa934c173bbbfbbf711b1d2429426a7.1675498628.git.wqu@suse.com \
--to=wqu@suse.com \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=sebastian.reichel@collabora.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 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.