From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Nitheesh Sekar <quic_nsekar@quicinc.com>,
agross@kernel.org, andersson@kernel.org,
konrad.dybcio@linaro.org, lpieralisi@kernel.org, kw@linux.com,
robh@kernel.org, bhelgaas@google.com,
krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
vkoul@kernel.org, kishon@kernel.org, mani@kernel.org,
p.zabel@pengutronix.de, quic_srichara@quicinc.com,
quic_varada@quicinc.com, quic_ipkumar@quicinc.com,
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 1/6] dt-bindings: phy: qcom,uniphy-pcie: Document PCIe uniphy
Date: Wed, 4 Oct 2023 08:57:52 +0200 [thread overview]
Message-ID: <4bc021c1-0198-41a4-aa73-bf0cf0c0420a@linaro.org> (raw)
In-Reply-To: <20231003120846.28626-2-quic_nsekar@quicinc.com>
On 03/10/2023 14:08, Nitheesh Sekar wrote:
> Document the Qualcomm UNIPHY PCIe 28LP present in IPQ5018.
>
> Signed-off-by: Nitheesh Sekar <quic_nsekar@quicinc.com>
Thank you for your patch. There is something to discuss/improve.
> ---
> .../bindings/phy/qcom,uniphy-pcie-28lp.yaml | 77 +++++++++++++++++++
> 1 file changed, 77 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/phy/qcom,uniphy-pcie-28lp.yaml
>
> diff --git a/Documentation/devicetree/bindings/phy/qcom,uniphy-pcie-28lp.yaml b/Documentation/devicetree/bindings/phy/qcom,uniphy-pcie-28lp.yaml
> new file mode 100644
> index 000000000000..6b2574f9532e
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/phy/qcom,uniphy-pcie-28lp.yaml
Filename should match compatibles and they do not use 28lp.
> @@ -0,0 +1,77 @@
> +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/phy/qcom,uniphy-pcie-28lp.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Qualcomm UNIPHY PCIe 28LP PHY driver
Driver as Linux driver? Drop. Describe the hardware instead.
> +
> +maintainers:
> + - Nitheesh Sekar <quic_nsekar@quicinc.com>
> + - Sricharan Ramabadhran <quic_srichara@quicinc.com>
> +
> +properties:
> + compatible:
> + enum:
> + - qcom,ipq5018-uniphy-pcie-gen2x1
> + - qcom,ipq5018-uniphy-pcie-gen2x2
> +
> + reg:
> + maxItems: 1
> +
> + clocks:
> + maxItems: 1
> +
> + clock-names:
> + items:
> + - const: pipe_clk
Drop _clk... or even drop entire clock-names. Not needed for one entry.
> +
> + resets:
> + maxItems: 2
> +
> + reset-names:
> + items:
> + - const: phy
> + - const: phy_phy
These are absolutely terrible names. If you have third one, it would be
"phy_phy_phy"? Drop or provide something useful.
> +
> + "#phy-cells":
> + const: 0
> +
> + "#clock-cells":
> + const: 0
> +
> + clock-output-names:
> + maxItems: 1
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-10-04 6:57 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-03 12:08 [PATCH 0/6] Enable IPQ5018 PCI support Nitheesh Sekar
2023-10-03 12:08 ` [PATCH 1/6] dt-bindings: phy: qcom,uniphy-pcie: Document PCIe uniphy Nitheesh Sekar
2023-10-04 6:57 ` Krzysztof Kozlowski [this message]
2023-10-05 2:53 ` Nitheesh Sekar
2023-10-03 12:08 ` [PATCH 2/6] dt-bindings: PCI: qcom: Add IPQ5108 SoC Nitheesh Sekar
2023-10-04 6:59 ` Krzysztof Kozlowski
2023-10-07 0:25 ` Konrad Dybcio
2023-10-09 9:10 ` Nitheesh Sekar
2023-10-03 12:08 ` [PATCH 3/6] phy: qcom: Introduce PCIe UNIPHY 28LP driver Nitheesh Sekar
2023-10-03 15:15 ` Dmitry Baryshkov
2023-10-04 8:13 ` Krzysztof Kozlowski
2023-10-05 2:55 ` Nitheesh Sekar
2023-10-04 17:27 ` Robert Marko
2023-10-03 12:08 ` [PATCH 4/6] PCI: qcom: Add support for IPQ5018 Nitheesh Sekar
2023-10-03 15:19 ` Dmitry Baryshkov
2023-10-09 17:32 ` Manivannan Sadhasivam
2023-10-03 12:08 ` [PATCH 5/6] arm64: dts: qcom: ipq5018: Add PCIe related nodes Nitheesh Sekar
2023-10-03 15:23 ` Dmitry Baryshkov
2023-10-03 17:29 ` Nitheesh Sekar
2023-10-09 17:17 ` Manivannan Sadhasivam
2023-10-03 12:08 ` [PATCH 6/6] arm64: dts: qcom: ipq5018: Enable PCIe Nitheesh Sekar
2023-10-07 0:27 ` Konrad Dybcio
2023-10-09 6:15 ` Nitheesh Sekar
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=4bc021c1-0198-41a4-aa73-bf0cf0c0420a@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=bhelgaas@google.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kishon@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=linux-phy@lists.infradead.org \
--cc=lpieralisi@kernel.org \
--cc=mani@kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=quic_ipkumar@quicinc.com \
--cc=quic_nsekar@quicinc.com \
--cc=quic_srichara@quicinc.com \
--cc=quic_varada@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;
as well as URLs for NNTP newsgroup(s).