devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Boyd <swboyd@chromium.org>
To: Andy Gross <agross@kernel.org>,
	Kishon Vijay Abraham I <kishon@ti.com>,
	Mark Rutland <mark.rutland@arm.com>,
	Rob Herring <robh+dt@kernel.org>,
	Sandeep Maheswaram <sanm@codeaurora.org>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	Manu Gautam <mgautam@codeaurora.org>,
	Sandeep Maheswaram <sanm@codeaurora.org>
Subject: Re: [PATCH 2/2] dt-bindings: phy-qcom-qmp: Add SC7180 QMP phy support
Date: Mon, 04 Nov 2019 13:52:26 -0800	[thread overview]
Message-ID: <5dc09d9b.1c69fb81.3bb21.4dfc@mx.google.com> (raw)
In-Reply-To: <1572418544-11593-3-git-send-email-sanm@codeaurora.org>

Quoting Sandeep Maheswaram (2019-10-29 23:55:44)
> Add QMP phy entries for SC7180 in device tree bindings.
> 
> Signed-off-by: Sandeep Maheswaram <sanm@codeaurora.org>
> ---
>  Documentation/devicetree/bindings/phy/qcom-qmp-phy.txt | 11 +++++++++--
>  1 file changed, 9 insertions(+), 2 deletions(-)
> 

Can you convert this binding to YAML? Would make it easier to see what
is applicable to certain compatibles.

> diff --git a/Documentation/devicetree/bindings/phy/qcom-qmp-phy.txt b/Documentation/devicetree/bindings/phy/qcom-qmp-phy.txt
> index eac9ad3..369f5b7 100644
> --- a/Documentation/devicetree/bindings/phy/qcom-qmp-phy.txt
> +++ b/Documentation/devicetree/bindings/phy/qcom-qmp-phy.txt
> @@ -15,17 +15,20 @@ Required properties:
>                "qcom,sdm845-qmp-usb3-phy" for USB3 QMP V3 phy on sdm845,
>                "qcom,sdm845-qmp-usb3-uni-phy" for USB3 QMP V3 UNI phy on sdm845,
>                "qcom,sdm845-qmp-ufs-phy" for UFS QMP phy on sdm845,
> -              "qcom,sm8150-qmp-ufs-phy" for UFS QMP phy on sm8150.
> +              "qcom,sm8150-qmp-ufs-phy" for UFS QMP phy on sm8150,

Should remove the comma at the end of these lines so they don't have to
change.

> +              "qcom,sc7180-qmp-usb3-phy" for USB3 QMP V3 phy on sc7180.
>  
>  - reg:
>    - index 0: address and length of register set for PHY's common
>               serdes block.
>    - index 1: address and length of the DP_COM control block (for
> -             "qcom,sdm845-qmp-usb3-phy" only).
> +             "qcom,sdm845-qmp-usb3-phy" and "qcom,sc7180-qmp-usb3-phy" only).
>  
>  - reg-names:
>    - For "qcom,sdm845-qmp-usb3-phy":
>      - Should be: "reg-base", "dp_com"
> +  - For "qcom,sc7180-qmp-usb3-phy":
> +    - Should be: "reg-base", "dp_com"
>    - For all others:
>      - The reg-names property shouldn't be defined.

Why is this so complicated? Would be better to just know that index 1 is
dp_com and index 0 is "normal" register base.

>  
> @@ -60,6 +63,8 @@ Required properties:
>                         "ref", "ref_aux".
>                 For "qcom,sm8150-qmp-ufs-phy" must contain:
>                         "ref", "ref_aux".
> +               For "qcom,sc7180-qmp-usb3-phy" must contain:
> +                       "aux", "cfg_ahb", "ref", "com_aux".
>  
>   - resets: a list of phandles and reset controller specifier pairs,
>            one for each entry in reset-names.
> @@ -88,6 +93,8 @@ Required properties:
>                         "ufsphy".
>                 For "qcom,sm8150-qmp-ufs-phy": must contain:
>                         "ufsphy".
> +               For "qcom,sc7180-qmp-usb3-phy" must contain:
> +                       "phy", "common".

Please sort these lists based on compatible string.

>  
>   - vdda-phy-supply: Phandle to a regulator supply to PHY core block.
>   - vdda-pll-supply: Phandle to 1.8V regulator supply to PHY refclk pll block.

      reply	other threads:[~2019-11-04 22:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-30  6:55 [PATCH 0/2] Add QMP V3 USB3 PHY support for SC7180 Sandeep Maheswaram
2019-10-30  6:55 ` [PATCH 1/2] phy: qcom-qmp: " Sandeep Maheswaram
2019-11-07 15:35   ` Manu Gautam
2019-10-30  6:55 ` [PATCH 2/2] dt-bindings: phy-qcom-qmp: Add SC7180 QMP phy support Sandeep Maheswaram
2019-11-04 21:52   ` Stephen Boyd [this message]

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=5dc09d9b.1c69fb81.3bb21.4dfc@mx.google.com \
    --to=swboyd@chromium.org \
    --cc=agross@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=kishon@ti.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mgautam@codeaurora.org \
    --cc=robh+dt@kernel.org \
    --cc=sanm@codeaurora.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).