linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johan Hovold <johan@kernel.org>
To: Abel Vesa <abel.vesa@linaro.org>
Cc: Andy Gross <agross@kernel.org>,
	Bjorn Andersson <andersson@kernel.org>,
	Konrad Dybcio <konrad.dybcio@linaro.org>,
	"vkoul@kernel.org" <vkoul@kernel.org>,
	Kishon Vijay Abraham I <kishon@kernel.org>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	linux-arm-msm@vger.kernel.org, linux-phy@lists.infradead.org,
	devicetree@vger.kernel.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 1/8] dt-bindings: phy: Add QMP PCIe PHY comptible for SM8550
Date: Wed, 18 Jan 2023 17:45:16 +0100	[thread overview]
Message-ID: <Y8giHJMtPu4wTlmA@hovoldconsulting.com> (raw)
In-Reply-To: <20230118005328.2378792-2-abel.vesa@linaro.org>

On Wed, Jan 18, 2023 at 02:53:21AM +0200, Abel Vesa wrote:
> Document the QMP PCIe PHY compatible for SM8550.
> 
> Signed-off-by: Abel Vesa <abel.vesa@linaro.org>
> ---
>  .../devicetree/bindings/phy/qcom,sc8280xp-qmp-pcie-phy.yaml     | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/Documentation/devicetree/bindings/phy/qcom,sc8280xp-qmp-pcie-phy.yaml b/Documentation/devicetree/bindings/phy/qcom,sc8280xp-qmp-pcie-phy.yaml
> index 8a85318d9c92..65f26cfff3fb 100644
> --- a/Documentation/devicetree/bindings/phy/qcom,sc8280xp-qmp-pcie-phy.yaml
> +++ b/Documentation/devicetree/bindings/phy/qcom,sc8280xp-qmp-pcie-phy.yaml
> @@ -20,6 +20,8 @@ properties:
>        - qcom,sc8280xp-qmp-gen3x2-pcie-phy
>        - qcom,sc8280xp-qmp-gen3x4-pcie-phy
>        - qcom,sm8350-qmp-gen3x1-pcie-phy
> +      - qcom,sm8550-qmp-gen3x2-pcie-phy
> +      - qcom,sm8550-qmp-gen4x2-pcie-phy
>  
>    reg:
>      minItems: 1

I don't think I'll have time to look at this week, but I did notice that
you fail do describe the clocks, regulators, and resets (as you also
did for the UFS PHY binding) which are currently different from
sc8280xp.

Please be more careful when adding compatible strings so we get this
right. You should also double check that the differences are really
warranted and not just due the vendor using different names for the same
resource.

At least the reset must be renamed ("pcie_1_nocsr_com_phy_reset", e.g.
drop 'pcie' and 'reset', maybe more).

Johan

  parent reply	other threads:[~2023-01-18 16:46 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-18  0:53 [PATCH v3 0/8] phy: qualcomm: Add PCIe support for SM8550 Abel Vesa
2023-01-18  0:53 ` [PATCH v3 1/8] dt-bindings: phy: Add QMP PCIe PHY comptible " Abel Vesa
2023-01-18 16:36   ` Rob Herring
2023-01-18 16:45   ` Johan Hovold [this message]
2023-01-18 21:25     ` Abel Vesa
2023-01-19  7:40       ` Johan Hovold
2023-01-18  0:53 ` [PATCH v3 2/8] phy: qcom-qmp: pcs: Add v6 register offsets Abel Vesa
2023-01-18  4:20   ` Dmitry Baryshkov
2023-01-18  0:53 ` [PATCH v3 3/8] phy: qcom-qmp: pcs: Add v6.20 " Abel Vesa
2023-01-18  4:25   ` Dmitry Baryshkov
2023-01-18  0:53 ` [PATCH v3 4/8] phy: qcom-qmp: pcs-pcie: Add v6 " Abel Vesa
2023-01-18  4:25   ` Dmitry Baryshkov
2023-01-18  0:53 ` [PATCH v3 5/8] phy: qcom-qmp: pcs-pcie: Add v6.20 " Abel Vesa
2023-01-18  4:26   ` Dmitry Baryshkov
2023-01-18  0:53 ` [PATCH v3 6/8] phy: qcom-qmp: qserdes-txrx: " Abel Vesa
2023-01-18  4:30   ` Dmitry Baryshkov
2023-01-18  0:53 ` [PATCH v3 7/8] phy: qcom-qmp: qserdes-lane-shared: Add v6 " Abel Vesa
2023-01-18  0:53 ` [PATCH v3 8/8] phy: qcom-qmp-pcie: Add support for SM8550 g3x2 and g4x2 PCIEs Abel Vesa
2023-01-18  4:34   ` Dmitry Baryshkov
2023-01-18 23:34     ` Abel Vesa
2023-01-19 13:07       ` Dmitry Baryshkov

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=Y8giHJMtPu4wTlmA@hovoldconsulting.com \
    --to=johan@kernel.org \
    --cc=abel.vesa@linaro.org \
    --cc=agross@kernel.org \
    --cc=andersson@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=kishon@kernel.org \
    --cc=konrad.dybcio@linaro.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-phy@lists.infradead.org \
    --cc=robh+dt@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).