From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Bhupesh Sharma <bhupesh.sharma@linaro.org>
Cc: linux-arm-msm@vger.kernel.org, linux-phy@lists.infradead.org,
bhupesh.linux@gmail.com, agross@kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
robh+dt@kernel.org, vkoul@kernel.org,
Rob Herring <robh@kernel.org>
Subject: Re: [PATCH v3 3/4] dt-bindings: phy: qcom,qmp: Describe phy@ subnode properly
Date: Sat, 23 Apr 2022 08:51:39 -0700 [thread overview]
Message-ID: <YmQgi0i9PDCVqrGz@ripper> (raw)
In-Reply-To: <20220418205509.1102109-4-bhupesh.sharma@linaro.org>
On Mon 18 Apr 13:55 PDT 2022, Bhupesh Sharma wrote:
> Currently the qcom,qmp-phy dt-binding doesn't describe
> the 'reg' and '#phy-cells' properties for the phy@ subnode.
>
> Fix the same.
>
> Cc: Bjorn Andersson <bjorn.andersson@linaro.org>
> Cc: Rob Herring <robh@kernel.org>
> Signed-off-by: Bhupesh Sharma <bhupesh.sharma@linaro.org>
> ---
> .../devicetree/bindings/phy/qcom,qmp-phy.yaml | 13 +++++++++++++
> 1 file changed, 13 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/phy/qcom,qmp-phy.yaml b/Documentation/devicetree/bindings/phy/qcom,qmp-phy.yaml
> index 411c79dbfa15..c553c8ad0d1a 100644
> --- a/Documentation/devicetree/bindings/phy/qcom,qmp-phy.yaml
> +++ b/Documentation/devicetree/bindings/phy/qcom,qmp-phy.yaml
> @@ -118,6 +118,19 @@ patternProperties:
> Each device node of QMP phy is required to have as many child nodes as
> the number of lanes the PHY has.
> properties:
> + reg:
> + minItems: 1
> + maxItems: 6
> + items:
> + description: |
> + List of offset and length pairs of register sets for PHY blocks.
> + common block control registers, such as - SW_RESET, START_CTRL.
> + pcs registers, such as - PCS_STATUS, POWER_DOWN_CONTROL,
> + pcs misc registers, such as - PCS_MISC_TYPEC_CTRL.
The two cases we have is:
tx
rx
pcs
pcs_misc
and:
tx
rx
pcs
tx2
rx2
pcs_misc
So I think we should express that explicitly here.
Regards,
Bjorn
> +
> + "#phy-cells":
> + const: 0
> +
> "#clock-cells":
> enum: [ 0, 1, 2 ]
>
> --
> 2.35.1
>
WARNING: multiple messages have this Message-ID (diff)
From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Bhupesh Sharma <bhupesh.sharma@linaro.org>
Cc: linux-arm-msm@vger.kernel.org, linux-phy@lists.infradead.org,
bhupesh.linux@gmail.com, agross@kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
robh+dt@kernel.org, vkoul@kernel.org,
Rob Herring <robh@kernel.org>
Subject: Re: [PATCH v3 3/4] dt-bindings: phy: qcom, qmp: Describe phy@ subnode properly
Date: Sat, 23 Apr 2022 08:51:39 -0700 [thread overview]
Message-ID: <YmQgi0i9PDCVqrGz@ripper> (raw)
In-Reply-To: <20220418205509.1102109-4-bhupesh.sharma@linaro.org>
On Mon 18 Apr 13:55 PDT 2022, Bhupesh Sharma wrote:
> Currently the qcom,qmp-phy dt-binding doesn't describe
> the 'reg' and '#phy-cells' properties for the phy@ subnode.
>
> Fix the same.
>
> Cc: Bjorn Andersson <bjorn.andersson@linaro.org>
> Cc: Rob Herring <robh@kernel.org>
> Signed-off-by: Bhupesh Sharma <bhupesh.sharma@linaro.org>
> ---
> .../devicetree/bindings/phy/qcom,qmp-phy.yaml | 13 +++++++++++++
> 1 file changed, 13 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/phy/qcom,qmp-phy.yaml b/Documentation/devicetree/bindings/phy/qcom,qmp-phy.yaml
> index 411c79dbfa15..c553c8ad0d1a 100644
> --- a/Documentation/devicetree/bindings/phy/qcom,qmp-phy.yaml
> +++ b/Documentation/devicetree/bindings/phy/qcom,qmp-phy.yaml
> @@ -118,6 +118,19 @@ patternProperties:
> Each device node of QMP phy is required to have as many child nodes as
> the number of lanes the PHY has.
> properties:
> + reg:
> + minItems: 1
> + maxItems: 6
> + items:
> + description: |
> + List of offset and length pairs of register sets for PHY blocks.
> + common block control registers, such as - SW_RESET, START_CTRL.
> + pcs registers, such as - PCS_STATUS, POWER_DOWN_CONTROL,
> + pcs misc registers, such as - PCS_MISC_TYPEC_CTRL.
The two cases we have is:
tx
rx
pcs
pcs_misc
and:
tx
rx
pcs
tx2
rx2
pcs_misc
So I think we should express that explicitly here.
Regards,
Bjorn
> +
> + "#phy-cells":
> + const: 0
> +
> "#clock-cells":
> enum: [ 0, 1, 2 ]
>
> --
> 2.35.1
>
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
next prev parent reply other threads:[~2022-04-23 15:49 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-18 20:55 [PATCH v3 0/4] Fix dtbs_check warning(s) for Qualcomm QMP PHY Bhupesh Sharma
2022-04-18 20:55 ` Bhupesh Sharma
2022-04-18 20:55 ` [PATCH v3 1/4] dt-bindings: phy: qcom,qmp: Mark '#clock-cells' as a 'optional' property Bhupesh Sharma
2022-04-18 20:55 ` [PATCH v3 1/4] dt-bindings: phy: qcom, qmp: " Bhupesh Sharma
2022-04-19 12:12 ` [PATCH v3 1/4] dt-bindings: phy: qcom,qmp: " Rob Herring
2022-04-19 12:12 ` [PATCH v3 1/4] dt-bindings: phy: qcom, qmp: " Rob Herring
2022-04-23 15:46 ` [PATCH v3 1/4] dt-bindings: phy: qcom,qmp: " Bjorn Andersson
2022-04-23 15:46 ` Bjorn Andersson
2022-05-15 6:36 ` Bhupesh Sharma
2022-05-15 6:36 ` [PATCH v3 1/4] dt-bindings: phy: qcom, qmp: " Bhupesh Sharma
2022-04-18 20:55 ` [PATCH v3 2/4] dt-bindings: phy: qcom,qmp: Describe 'vdda-max-microamp' & 'vdda-pll-max-microamp' properties Bhupesh Sharma
2022-04-18 20:55 ` [PATCH v3 2/4] dt-bindings: phy: qcom, qmp: " Bhupesh Sharma
2022-04-18 22:34 ` [PATCH v3 2/4] dt-bindings: phy: qcom,qmp: " Dmitry Baryshkov
2022-04-18 22:34 ` Dmitry Baryshkov
2022-04-19 3:36 ` Bhupesh Sharma
2022-04-19 3:36 ` Bhupesh Sharma
2022-04-23 15:56 ` Bjorn Andersson
2022-04-23 15:56 ` Bjorn Andersson
2022-04-18 20:55 ` [PATCH v3 3/4] dt-bindings: phy: qcom,qmp: Describe phy@ subnode properly Bhupesh Sharma
2022-04-18 20:55 ` [PATCH v3 3/4] dt-bindings: phy: qcom, qmp: " Bhupesh Sharma
2022-04-23 15:51 ` Bjorn Andersson [this message]
2022-04-23 15:51 ` Bjorn Andersson
2022-04-18 20:55 ` [PATCH v3 4/4] arm64: dts: qcom: sm8450: Fix qmp phy node (use phy@ instead of lanes@) Bhupesh Sharma
2022-04-18 20:55 ` Bhupesh Sharma
2022-04-23 16:03 ` (subset) " Bjorn Andersson
2022-04-23 16:03 ` 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=YmQgi0i9PDCVqrGz@ripper \
--to=bjorn.andersson@linaro.org \
--cc=agross@kernel.org \
--cc=bhupesh.linux@gmail.com \
--cc=bhupesh.sharma@linaro.org \
--cc=devicetree@vger.kernel.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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.