From: Lorenzo Pieralisi <lpieralisi@kernel.org>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: Robert Marko <robimarko@gmail.com>,
agross@kernel.org, andersson@kernel.org,
konrad.dybcio@linaro.org, bhelgaas@google.com,
robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
mani@kernel.org, kw@linux.com, 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
Subject: Re: [PATCH 7/9] PCI: qcom: add support for IPQ8074 Gen3 port
Date: Fri, 13 Jan 2023 14:33:58 +0100 [thread overview]
Message-ID: <Y8FdxtCitnBd1c6k@lpieralisi> (raw)
In-Reply-To: <20221117192837.GA1203269@bhelgaas>
On Thu, Nov 17, 2022 at 01:28:37PM -0600, Bjorn Helgaas wrote:
> Hi Robert,
>
> If you post a v2 for any reason, capitalize the subject line to match
> previous history:
>
> PCI: qcom: Rename host-init error label
> PCI: qcom: Drop unused post_deinit callback
> PCI: qcom: Sort device-id table
> PCI: qcom: Clean up IP configurations
> ...
If he could do that while rebasing on top of my current pci/qcom branch
that would be ideal, I tried to cherry-pick patches 5,6,7 but 5 does not
apply.
Thanks,
Lorenzo
>
> On Wed, Nov 16, 2022 at 10:48:39PM +0100, Robert Marko wrote:
> > 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>
> > ---
> > 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 77e5dc7b88ad..97e8510c53fb 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.38.1
> >
next prev parent reply other threads:[~2023-01-13 13:39 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-16 21:48 [PATCH 1/9] arm64: dts: qcom: ipq8074: fix Gen2 PCIe QMP PHY Robert Marko
2022-11-16 21:48 ` [PATCH 2/9] arm64: dts: qcom: ipq8074: fix Gen3 " Robert Marko
2022-12-05 21:52 ` Bjorn Andersson
2022-12-06 9:51 ` Robert Marko
2022-12-27 19:20 ` Bjorn Andersson
2022-12-28 11:10 ` Robert Marko
2022-12-29 17:29 ` Bjorn Andersson
2023-01-03 20:31 ` Robert Marko
2022-11-16 21:48 ` [PATCH 3/9] arm64: dts: qcom: ipq8074: correct Gen2 PCIe ranges Robert Marko
2022-11-16 21:48 ` [PATCH 4/9] arm64: dts: qcom: ipq8074: set Gen2 PCIe pcie max-link-speed Robert Marko
2022-11-16 21:48 ` [PATCH 5/9] dt-bindings: PCI: qcom: alphabetically sort compatibles Robert Marko
2022-11-17 13:16 ` Krzysztof Kozlowski
2023-01-15 4:29 ` Manivannan Sadhasivam
2022-11-16 21:48 ` [PATCH 6/9] dt-bindings: PCI: qcom: document IPQ8074 Gen3 port Robert Marko
2022-11-17 14:39 ` Krzysztof Kozlowski
2023-01-15 4:28 ` Manivannan Sadhasivam
2022-11-16 21:48 ` [PATCH 7/9] PCI: qcom: add support for " Robert Marko
2022-11-17 19:28 ` Bjorn Helgaas
2023-01-13 13:33 ` Lorenzo Pieralisi [this message]
2023-01-13 16:41 ` Robert Marko
2023-01-15 4:30 ` Manivannan Sadhasivam
2022-11-16 21:48 ` [PATCH 8/9] arm64: dts: qcom: ipq8074: fix Gen3 PCIe node Robert Marko
2022-11-16 21:48 ` [PATCH 9/9] arm64: dts: qcom: ipq8074: correct PCIe QMP PHY output clock names Robert Marko
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=Y8FdxtCitnBd1c6k@lpieralisi \
--to=lpieralisi@kernel.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=bhelgaas@google.com \
--cc=devicetree@vger.kernel.org \
--cc=helgaas@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=mani@kernel.org \
--cc=robh+dt@kernel.org \
--cc=robimarko@gmail.com \
--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).