From: Varadarajan Narayanan <quic_varada@quicinc.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: <lpieralisi@kernel.org>, <kw@linux.com>,
<manivannan.sadhasivam@linaro.org>, <robh@kernel.org>,
<bhelgaas@google.com>, <krzk+dt@kernel.org>,
<conor+dt@kernel.org>, <vkoul@kernel.org>, <kishon@kernel.org>,
<andersson@kernel.org>, <konradybcio@kernel.org>,
<p.zabel@pengutronix.de>, <quic_nsekar@quicinc.com>,
<dmitry.baryshkov@linaro.org>, <linux-arm-msm@vger.kernel.org>,
<linux-pci@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <linux-phy@lists.infradead.org>
Subject: Re: [PATCH v2 1/6] dt-bindings: phy: qcom,uniphy-pcie: Document PCIe uniphy
Date: Wed, 11 Dec 2024 14:21:40 +0530 [thread overview]
Message-ID: <Z1lSnLyh6LSpk4z1@hu-varada-blr.qualcomm.com> (raw)
In-Reply-To: <7js7lswzde67izdradhuzgvlixwiblgf7aosdvavknbclbtjew@6w3y2e2k3mtk>
On Thu, Dec 05, 2024 at 10:38:05AM +0100, Krzysztof Kozlowski wrote:
> On Wed, Dec 04, 2024 at 05:03:24PM +0530, Varadarajan Narayanan wrote:
> > From: Nitheesh Sekar <quic_nsekar@quicinc.com>
> >
> > Document the Qualcomm UNIPHY PCIe 28LP present in IPQ5332.
> >
> > Signed-off-by: Nitheesh Sekar <quic_nsekar@quicinc.com>
> > Signed-off-by: Varadarajan Narayanan <quic_varada@quicinc.com>
> > ---
> > v2: Rename the file to match the compatible
>
> Either I look at wrong v1 from your cover letter or there was no such
> file in v1, so how it can be a rename?
>
> What happened here?
This driver was pulled in from [1] "Enable IPQ5018 PCI support (Nitheesh Sekar)"
In that review, there was this feedback [4]
-------------------------------
> +++
> b/Documentation/devicetree/bindings/phy/qcom,uniphy-pcie-28lp.yaml
Filename should match compatibles and they do not use 28lp.
-------------------------------
> > Drop 'driver' from title
> > Dropped 'clock-names'
> > Fixed 'reset-names'
> > --
> > .../bindings/phy/qcom,uniphy-pcie.yaml | 82 +++++++++++++++++++
> > 1 file changed, 82 insertions(+)
> > create mode 100644 Documentation/devicetree/bindings/phy/qcom,uniphy-pcie.yaml
> >
> > diff --git a/Documentation/devicetree/bindings/phy/qcom,uniphy-pcie.yaml b/Documentation/devicetree/bindings/phy/qcom,uniphy-pcie.yaml
> > new file mode 100644
> > index 000000000000..e0ad98a9f324
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/phy/qcom,uniphy-pcie.yaml
>
> This does not match compatible, so I don't see how it even matches your
> changelog.
Since this phy has both single and dual line capabilities I used
the phy's name alone for the file name. Will rename this as
qcom,ipq5332-uniphy-pcie-phy.yaml
If this is not suitable, can you please suggest one that would be
apt for this phy.
> > @@ -0,0 +1,82 @@
> > +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
> > +%YAML 1.2
> > +---
> > +$id: http://devicetree.org/schemas/phy/qcom,uniphy-pcie.yaml#
> > +$schema: http://devicetree.org/meta-schemas/core.yaml#
> > +
> > +title: Qualcomm UNIPHY PCIe 28LP PHY
> > +
> > +maintainers:
> > + - Nitheesh Sekar <quic_nsekar@quicinc.com>
> > + - Varadarajan Narayanan <quic_varada@quicinc.com>
> > +
> > +description:
> > + PCIe and USB combo PHY found in Qualcomm IPQ5332 SoC
> > +
> > +properties:
> > + compatible:
> > + enum:
> > + - qcom,ipq5332-uniphy-pcie-gen3x1
>
> Odd naming. Did anyone suggest this? I would expect something matches
> like everything else recent (see X1 for example).
It was not suggested by anyone. Since [4] didn't comment on this
continued to use it. Will change it as follows (similar to
qcom,x1e80100-qmp-gen4x2-pcie-phy)
qcom,ipq5332-uniphy-gen3x1-pcie-phy
qcom,ipq5332-uniphy-gen3x2-pcie-phy
>
> > + - qcom,ipq5332-uniphy-pcie-gen3x2
> > +
> > + reg:
> > + maxItems: 1
> > +
> > + clocks:
> > + minItems: 2
>
> What happened here? This cannot be minItems and it never was.
Will fix this.
> > +
> > + resets:
> > + minItems: 2
> > + maxItems: 3
>
> Why this varies?
>
> This patch is odd. Confusing changelog, v1 entirely different and not
> matching what is here, unusual and incorrect code in the binding itself.
>
> Provide changelog explaining WHY you did such odd changes.
This series combines [1] and [2]. [1] introduces IPQ5018 PCIe
support and [2] depends on [1] to introduce IPQ5332 PCIe support.
Since the community was interested in [2] (please see [3]), tried
to revive IPQ5332's PCIe support with this patch. Apologies for
not expressing this in the cover letter.
> Open *LATEST* existing Qcom bindings and look how they do it. Do not
> implement things differently.
Sure.
Thanks
Varada
1. Enable IPQ5018 PCI support (Nitheesh Sekar) - https://lore.kernel.org/all/20231003120846.28626-1-quic_nsekar@quicinc.com/
2. Add PCIe support for Qualcomm IPQ5332 (Praveenkumar I) - https://lore.kernel.org/linux-arm-msm/20231214062847.2215542-1-quic_ipkumar@quicinc.com/
3. Community interest - https://lore.kernel.org/linux-arm-msm/20240310132915.GE3390@thinkpad/
4. dt-bindings feedback - https://lore.kernel.org/all/4bc021c1-0198-41a4-aa73-bf0cf0c0420a@linaro.org/
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
next prev parent reply other threads:[~2024-12-11 8:52 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-04 11:33 [PATCH v2 0/6] Add PCIe support for Qualcomm IPQ5332 Varadarajan Narayanan
2024-12-04 11:33 ` [PATCH v2 1/6] dt-bindings: phy: qcom,uniphy-pcie: Document PCIe uniphy Varadarajan Narayanan
2024-12-05 9:38 ` Krzysztof Kozlowski
2024-12-11 8:51 ` Varadarajan Narayanan [this message]
2024-12-04 11:33 ` [PATCH v2 2/6] phy: qcom: Introduce PCIe UNIPHY 28LP driver Varadarajan Narayanan
2024-12-04 23:01 ` Dmitry Baryshkov
2024-12-05 9:39 ` Krzysztof Kozlowski
2024-12-06 8:46 ` Krzysztof Kozlowski
2024-12-05 16:40 ` Konrad Dybcio
2024-12-16 6:30 ` Varadarajan Narayanan
2024-12-16 12:05 ` Konrad Dybcio
2024-12-04 11:33 ` [PATCH v2 3/6] dt-bindings: PCI: qcom: Add IPQ5332 SoC Varadarajan Narayanan
2024-12-05 9:40 ` Krzysztof Kozlowski
2024-12-04 11:33 ` [PATCH v2 4/6] pci: qcom: Add support for IPQ5332 Varadarajan Narayanan
2024-12-04 23:10 ` Bjorn Helgaas
2024-12-11 9:34 ` Manivannan Sadhasivam
2024-12-04 11:33 ` [PATCH v2 5/6] arm64: dts: qcom: ipq5332: Add PCIe related nodes Varadarajan Narayanan
2024-12-05 16:55 ` Konrad Dybcio
2024-12-04 11:33 ` [PATCH v2 6/6] arm64: dts: qcom: ipq5332: Enable PCIe phys and controllers Varadarajan Narayanan
2024-12-05 16:58 ` Konrad Dybcio
2024-12-16 11:27 ` Varadarajan Narayanan
2024-12-05 16:58 ` Konrad Dybcio
-- strict thread matches above, loose matches on Subject: below --
2024-08-27 4:57 [PATCH V2 0/6] Enable IPQ5018 PCI support Sricharan R
2024-08-27 4:57 ` [PATCH V2 1/6] dt-bindings: phy: qcom,uniphy-pcie: Document PCIe uniphy Sricharan R
2024-08-27 6:27 ` Krzysztof Kozlowski
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=Z1lSnLyh6LSpk4z1@hu-varada-blr.qualcomm.com \
--to=quic_varada@quicinc.com \
--cc=andersson@kernel.org \
--cc=bhelgaas@google.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=kishon@kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@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=linux-phy@lists.infradead.org \
--cc=lpieralisi@kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=p.zabel@pengutronix.de \
--cc=quic_nsekar@quicinc.com \
--cc=robh@kernel.org \
--cc=vkoul@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