From: Abel Vesa <abel.vesa@linaro.org>
To: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
Cc: "Konrad Dybcio" <konrad.dybcio@linaro.org>,
"Bjorn Andersson" <andersson@kernel.org>,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Krzysztof Wilczyński" <kw@linux.com>,
"Rob Herring" <robh@kernel.org>,
"Bjorn Helgaas" <bhelgaas@google.com>,
linux-pci@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/2] PCI: qcom: Add X1E80100 PCIe support
Date: Fri, 2 Feb 2024 11:31:50 +0200 [thread overview]
Message-ID: <Zby2hp2vH4TRv+xV@linaro.org> (raw)
In-Reply-To: <ZbyuANz7Jza7lzZS@linaro.org>
On 24-02-02 10:55:28, Abel Vesa wrote:
> On 24-02-02 14:18:06, Manivannan Sadhasivam wrote:
> > On Fri, Feb 02, 2024 at 10:41:03AM +0200, Abel Vesa wrote:
> > > On 24-02-01 20:20:40, Konrad Dybcio wrote:
> > > > On 29.01.2024 12:10, Abel Vesa wrote:
> > > > > Add the compatible and the driver data for X1E80100.
> > > > >
> > > > > Signed-off-by: Abel Vesa <abel.vesa@linaro.org>
> > > > > ---
> > > > > 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 10f2d0bb86be..2a6000e457bc 100644
> > > > > --- a/drivers/pci/controller/dwc/pcie-qcom.c
> > > > > +++ b/drivers/pci/controller/dwc/pcie-qcom.c
> > > > > @@ -1642,6 +1642,7 @@ static const struct of_device_id qcom_pcie_match[] = {
> > > > > { .compatible = "qcom,pcie-sm8450-pcie0", .data = &cfg_1_9_0 },
> > > > > { .compatible = "qcom,pcie-sm8450-pcie1", .data = &cfg_1_9_0 },
> > > > > { .compatible = "qcom,pcie-sm8550", .data = &cfg_1_9_0 },
> > > > > + { .compatible = "qcom,pcie-x1e80100", .data = &cfg_1_9_0 },
> > > >
> > > > I swear I'm not delaying everything related to x1 on purpose..
> > > >
> > >
> > > No worries.
> > >
> > > > But..
> > > >
> > > > Would a "qcom,pcie-v1.9.0" generic match string be a good idea?
> > >
> > > Sure. So that means this would be fallback compatible for all the following platforms:
> > >
> > > - sa8540p
> > > - sa8775p
> > > - sc7280
> > > - sc8180x
> > > - sc8280xp
> > > - sdx55
> > > - sm8150
> > > - sm8250
> > > - sm8350
> > > - sm8450-pcie0
> > > - sm8450-pcie1
> > > - sm8550
> > > - x1e80100
> > >
> > > Will prepare a patchset.
> > >
> >
> > NO. Fallback should be based on the base SoC for this platform.
>
> Right, so since the SM8250 is the one that has the core version 1.9.0,
> should we just the sm8550 compatible as fallback for all other ones.
>
> Yes, I know that there is SM8150, which has core version 1.5.0, but it
> is still 1.9.0 compatible.
>
> Or maybe we should rename the config to 1_5_0 and have the sm8150
> compatible as fallback for all these platforms.
>
Actually no, that's a bad idea. I would break DT backwards compatibility.
I'll just drop the compatible from driver and add fallback in DT for
X1E80100.
> >
> > - Mani
> >
> > --
> > மணிவண்ணன் சதாசிவம்
next prev parent reply other threads:[~2024-02-02 9:31 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-29 11:10 [PATCH v2 0/2] PCI: qcom: Add PCIe support for X1E80100 Abel Vesa
2024-01-29 11:10 ` [PATCH v2 1/2] dt-bindings: PCI: qcom: Document the X1E80100 PCIe Controller Abel Vesa
2024-01-29 14:19 ` Krzysztof Kozlowski
2024-01-29 14:36 ` Abel Vesa
2024-02-02 12:44 ` Manivannan Sadhasivam
2024-01-29 11:10 ` [PATCH v2 2/2] PCI: qcom: Add X1E80100 PCIe support Abel Vesa
2024-02-01 19:20 ` Konrad Dybcio
2024-02-02 8:13 ` neil.armstrong
2024-02-02 8:41 ` Manivannan Sadhasivam
2024-02-02 10:31 ` Abel Vesa
2024-02-02 12:43 ` Manivannan Sadhasivam
2024-02-02 8:41 ` Abel Vesa
2024-02-02 8:44 ` neil.armstrong
2024-02-02 8:51 ` Abel Vesa
2024-02-02 8:48 ` Manivannan Sadhasivam
2024-02-02 8:55 ` Abel Vesa
2024-02-02 9:31 ` Abel Vesa [this message]
2024-02-02 9:48 ` Manivannan Sadhasivam
2024-02-02 12:44 ` Manivannan Sadhasivam
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=Zby2hp2vH4TRv+xV@linaro.org \
--to=abel.vesa@linaro.org \
--cc=andersson@kernel.org \
--cc=bhelgaas@google.com \
--cc=konrad.dybcio@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=manivannan.sadhasivam@linaro.org \
--cc=robh@kernel.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;
as well as URLs for NNTP newsgroup(s).