From: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: Sricharan R <quic_srichara@quicinc.com>,
bhelgaas@google.com, lpieralisi@kernel.org, kw@linux.com,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
andersson@kernel.org, konrad.dybcio@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 V7 4/4] PCI: qcom: Add support for IPQ9574
Date: Wed, 6 Nov 2024 17:08:56 +0000 [thread overview]
Message-ID: <20241106170856.7iv2sjmjwyhnurps@thinkpad> (raw)
In-Reply-To: <20241106165312.GA1528877@bhelgaas>
On Wed, Nov 06, 2024 at 10:53:12AM -0600, Bjorn Helgaas wrote:
> On Wed, Nov 06, 2024 at 02:56:15PM +0000, Manivannan Sadhasivam wrote:
> > On Tue, Nov 05, 2024 at 07:40:24PM -0600, Bjorn Helgaas wrote:
> > > On Thu, Aug 01, 2024 at 11:18:03AM +0530, Sricharan R wrote:
> > > > From: devi priya <quic_devipriy@quicinc.com>
> > > >
> > > > The IPQ9574 platform has four Gen3 PCIe controllers:
> > > > two single-lane and two dual-lane based on SNPS core 5.70a.
> > > >
> > > > QCOM IP rev is 1.27.0 and Synopsys IP rev is 5.80a.
> > > > Reuse all the members of 'ops_2_9_0'.
> > >
> > > Wow, this is confusing.
> > >
> > > "Based on SNPS core 5.70a", but "Synopsys IP rev is 5.80a."
> > > Are those supposed to match? Or is it 5.70a of one thing but 5.80a of
> > > a different thing?
> >
> > Hmm, I'm not sure why 5.70a is mentioned here. It seems irrelevant
> > (even if it is the base).
> >
> > > And where does ops_2_9_0 come in? The code comment says:
> > >
> > > /* Qcom IP rev.: 2.9.0 Synopsys IP rev.: 5.00a */
> > > static const struct qcom_pcie_ops ops_2_9_0 = {
> > >
> > > which doesn't match 1.27.0 or 5.70a or 5.80a. In fact there's nothing
> > > in the file that matches 1.*27.*0
> > >
> > > Honestly, I don't really care if you have all the versions here in the
> > > commit log. But if the versions *are* here, can we make them make
> > > sense?
> >
> > We name the 'ops' structure based on Qcom IP revision. And we reuse
> > it across the SoCs which are compatible. That's why ops_2_9_0 is
> > used for this SoC which has Qcom IP rev 1.27.0.
>
> Got it. So a family of compatible Qcom IP starts with 2.9.0 and newer
> members are 1.27.0 etc. With no hint in the source about what the
> members of the family are. Perfect sEnSe.
>
You can get that information by mapping the ops structure with compatibles. I
feel less incentive in documenting the SoC names deriving the same IP.
And the reason why 2.9.0 ops is used by 1.27 is because, we ended up adding
support for 2.9.0 IP first and the lower version followed later.
- Mani
--
மணிவண்ணன் சதாசிவம்
next prev parent reply other threads:[~2024-11-06 17:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-01 5:47 [PATCH V7 0/4] Add PCIe support for IPQ9574 Sricharan R
2024-08-01 5:48 ` [PATCH V7 1/4] dt-bindings: PCI: qcom: Document the IPQ9574 PCIe controller Sricharan R
2024-08-01 5:48 ` [PATCH V7 2/4] arm64: dts: qcom: ipq9574: Add PCIe PHYs and controller nodes Sricharan R
2024-12-16 8:54 ` Mantas Pucka
2024-08-01 5:48 ` [PATCH V7 3/4] arm64: dts: qcom: ipq9574: Enable PCIe PHYs and controllers Sricharan R
2024-08-01 5:48 ` [PATCH V7 4/4] PCI: qcom: Add support for IPQ9574 Sricharan R
2024-11-06 1:40 ` Bjorn Helgaas
2024-11-06 14:56 ` Manivannan Sadhasivam
2024-11-06 16:53 ` Bjorn Helgaas
2024-11-06 17:08 ` Manivannan Sadhasivam [this message]
2024-11-03 21:01 ` [PATCH V7 0/4] Add PCIe " Krzysztof Wilczyński
2024-12-26 18:27 ` (subset) " 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=20241106170856.7iv2sjmjwyhnurps@thinkpad \
--to=manivannan.sadhasivam@linaro.org \
--cc=andersson@kernel.org \
--cc=bhelgaas@google.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=helgaas@kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzk+dt@kernel.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=quic_srichara@quicinc.com \
--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