From: Robert Marko <robimarko@gmail.com>
To: agross@kernel.org, andersson@kernel.org,
konrad.dybcio@linaro.org, bhelgaas@google.com,
lpieralisi@kernel.org, robh@kernel.org, kw@linux.com,
krzysztof.kozlowski+dt@linaro.org, mani@kernel.org,
svarbanov@mm-sol.com, shawn.guo@linaro.org,
linux-arm-msm@vger.kernel.org, linux-pci@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Robert Marko <robimarko@gmail.com>
Subject: [PATCH v2 7/9] PCI: qcom: Add support for IPQ8074 Gen3 port
Date: Fri, 13 Jan 2023 17:44:47 +0100 [thread overview]
Message-ID: <20230113164449.906002-7-robimarko@gmail.com> (raw)
In-Reply-To: <20230113164449.906002-1-robimarko@gmail.com>
IPQ8074 has one Gen2 and one Gen3 port, with Gen2 port already supported.
Add compatible for Gen3 port which uses the same controller as IPQ6018.
Signed-off-by: Robert Marko <robimarko@gmail.com>
---
Changes in v2:
* Capitalize subject to match previous history
---
drivers/pci/controller/dwc/pcie-qcom.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/pci/controller/dwc/pcie-qcom.c b/drivers/pci/controller/dwc/pcie-qcom.c
index b9350d93b4ba..b69a406a2660 100644
--- a/drivers/pci/controller/dwc/pcie-qcom.c
+++ b/drivers/pci/controller/dwc/pcie-qcom.c
@@ -1817,6 +1817,7 @@ static const struct of_device_id qcom_pcie_match[] = {
{ .compatible = "qcom,pcie-ipq8064", .data = &cfg_2_1_0 },
{ .compatible = "qcom,pcie-ipq8064-v2", .data = &cfg_2_1_0 },
{ .compatible = "qcom,pcie-ipq8074", .data = &cfg_2_3_3 },
+ { .compatible = "qcom,pcie-ipq8074-gen3", .data = &cfg_2_9_0 },
{ .compatible = "qcom,pcie-msm8996", .data = &cfg_2_3_2 },
{ .compatible = "qcom,pcie-qcs404", .data = &cfg_2_4_0 },
{ .compatible = "qcom,pcie-sa8540p", .data = &cfg_1_9_0 },
--
2.39.0
next prev parent reply other threads:[~2023-01-13 16:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-13 16:44 [PATCH v2 1/9] arm64: dts: qcom: ipq8074: fix Gen2 PCIe QMP PHY Robert Marko
2023-01-13 16:44 ` [PATCH v2 2/9] arm64: dts: qcom: ipq8074: fix Gen3 " Robert Marko
2023-01-13 16:44 ` [PATCH v2 3/9] arm64: dts: qcom: ipq8074: correct Gen2 PCIe ranges Robert Marko
2023-01-13 16:44 ` [PATCH v2 4/9] arm64: dts: qcom: ipq8074: set Gen2 PCIe pcie max-link-speed Robert Marko
2023-01-13 16:44 ` [PATCH v2 5/9] dt-bindings: PCI: qcom: alphabetically sort compatibles Robert Marko
2023-01-13 16:44 ` [PATCH v2 6/9] dt-bindings: PCI: qcom: document IPQ8074 Gen3 port Robert Marko
2023-01-13 16:44 ` Robert Marko [this message]
2023-01-13 16:44 ` [PATCH v2 8/9] arm64: dts: qcom: ipq8074: fix Gen3 PCIe node Robert Marko
2023-01-30 17:11 ` Arnd Bergmann
2023-02-02 9:16 ` Robert Marko
2023-02-02 9:42 ` Arnd Bergmann
2023-02-28 13:20 ` Manivannan Sadhasivam
2023-03-01 10:57 ` Robert Marko
2023-01-13 16:44 ` [PATCH v2 9/9] arm64: dts: qcom: ipq8074: correct PCIe QMP PHY output clock names Robert Marko
2023-01-16 9:14 ` (subset) [PATCH v2 1/9] arm64: dts: qcom: ipq8074: fix Gen2 PCIe QMP PHY Lorenzo Pieralisi
2023-01-19 4:54 ` Bjorn Andersson
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=20230113164449.906002-7-robimarko@gmail.com \
--to=robimarko@gmail.com \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=bhelgaas@google.com \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kw@linux.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=mani@kernel.org \
--cc=robh@kernel.org \
--cc=shawn.guo@linaro.org \
--cc=svarbanov@mm-sol.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).