From: Krzysztof Kozlowski <krzk@kernel.org>
To: Qiang Yu <qiang.yu@oss.qualcomm.com>
Cc: Vinod Koul <vkoul@kernel.org>,
Neil Armstrong <neil.armstrong@linaro.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Manivannan Sadhasivam <manivannan.sadhasivam@oss.qualcomm.com>,
Philipp Zabel <p.zabel@pengutronix.de>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
linux-arm-msm@vger.kernel.org, linux-phy@lists.infradead.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 1/3] dt-bindings: phy: qcom: Add Glymur QMP PCIe multiple link-mode PHY
Date: Sun, 19 Jul 2026 08:50:00 +0200 [thread overview]
Message-ID: <20260719-sloppy-cornflower-hippo-8212e2@quoll> (raw)
In-Reply-To: <20260717-glymur_linkmode_0717-v5-1-4f9e87a61463@oss.qualcomm.com>
On Fri, Jul 17, 2026 at 02:58:33AM -0700, Qiang Yu wrote:
> diff --git a/Documentation/devicetree/bindings/phy/qcom,glymur-qmp-pcie-multiphy.yaml b/Documentation/devicetree/bindings/phy/qcom,glymur-qmp-pcie-multiphy.yaml
> new file mode 100644
> index 000000000000..73550f77e9b6
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/phy/qcom,glymur-qmp-pcie-multiphy.yaml
Filename: qcom,glymur-qmp-gen5x8-pcie-phy.yaml
> @@ -0,0 +1,176 @@
> +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/phy/qcom,glymur-qmp-pcie-multiphy.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Qualcomm QMP PCIe multiple link-mode PHY controller (PCIe, Glymur)
> +
> +maintainers:
> + - Qiang Yu <qiang.yu@oss.qualcomm.com>
> + - Manivannan Sadhasivam <manivannan.sadhasivam@oss.qualcomm.com>
> +
> +description: |
> + The Glymur SoC uses a single PCIe Gen5 PHY hardware block for the
> + PCIe3a/PCIe3b controllers. This block supports two link modes, selected
> + at runtime via a TCSR syscon register:
> +
> + 1. x8 - a single 8-lane PHY instance is exposed (PCIe3a only)
> + 2. x4+x4 - two independent 4-lane PHY instances are exposed (PCIe3a and
> + PCIe3b)
> +
> + The node always describes both PHY instances ("port a" and "port b"),
> + regardless of which link mode is active on the board.
> +
> +properties:
> + compatible:
> + enum:
> + - qcom,glymur-qmp-gen5x8-pcie-phy
> +
> + reg:
> + minItems: 2
Dop
> + maxItems: 2
> +
> + reg-names:
> + items:
> + - const: port_a
> + - const: port_b
> +
> + clocks:
> + minItems: 10
Drop
> + maxItems: 10
> +
> + clock-names:
> + items:
> + - const: aux
> + - const: cfg_ahb
> + - const: ref
> + - const: rchng
> + - const: pipe
> + - const: phy_b_aux
> + - const: cfg_ahb_b
> + - const: rchng_b
> + - const: pipe_b
> + - const: pipediv2_b
> +
> + power-domains:
> + minItems: 2
Drop
> + maxItems: 2
> +
> + power-domain-names:
> + items:
> + - const: phy_a_gdsc
port_a
> + - const: phy_b_gdsc
port_b
> +
> + resets:
> + minItems: 4
Drop
> + maxItems: 4
> +
> + reset-names:
> + items:
> + - const: phy_a
port_a
> + - const: phy_a_nocsr
port_a_nocsr
etc.
> + - const: phy_b
> + - const: phy_b_nocsr
> +
> + vdda-phy-supply: true
> +
> + vdda-pll-supply: true
> +
> + vdda-refgen0p9-supply: true
> +
> + vdda-refgen1p2-supply: true
> +
> + qcom,link-mode:
> + description:
> + Reference to a register in the TCSR syscon that reports the link
> + mode the PCIe PHY is currently configured for, either a single x8
> + link or two independent x4 links. The link mode is programmed by
> + firmware before Linux boots; this property is only used to read
> + the active link mode, specified as a phandle to the syscon and
> + the register offset.
> + $ref: /schemas/types.yaml#/definitions/phandle-array
> + items:
> + - items:
> + - description: phandle of TCSR syscon
> + - description: offset of link mode register
> +
> + "#clock-cells":
> + const: 1
> +
> + clock-output-names:
> + items:
> + - description: Name of the PHY A pipe clock output.
> + - description: Name of the PHY B pipe clock output.
> +
> + "#phy-cells":
> + const: 1
You should explain in description the meaning of cell value. Or provide
filename of header with constants.
> +
> +required:
> + - compatible
> + - reg
> + - reg-names
> + - clocks
> + - clock-names
> + - power-domains
> + - power-domain-names
> + - resets
> + - reset-names
> + - vdda-phy-supply
> + - vdda-pll-supply
> + - vdda-refgen0p9-supply
> + - vdda-refgen1p2-supply
> + - qcom,link-mode
> + - "#clock-cells"
> + - clock-output-names
> + - "#phy-cells"
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + #include <dt-bindings/clock/qcom,glymur-gcc.h>
> + #include <dt-bindings/clock/qcom,glymur-tcsr.h>
> +
> + pcie3_phy: phy@f00000 {
Drop unused label.
The old 5x4 glymur compatible could be deprecated as well, but fine for
me without doing so.
Best regards,
Krzysztof
WARNING: multiple messages have this Message-ID (diff)
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Qiang Yu <qiang.yu@oss.qualcomm.com>
Cc: Vinod Koul <vkoul@kernel.org>,
Neil Armstrong <neil.armstrong@linaro.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Manivannan Sadhasivam <manivannan.sadhasivam@oss.qualcomm.com>,
Philipp Zabel <p.zabel@pengutronix.de>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
linux-arm-msm@vger.kernel.org, linux-phy@lists.infradead.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 1/3] dt-bindings: phy: qcom: Add Glymur QMP PCIe multiple link-mode PHY
Date: Sun, 19 Jul 2026 08:50:00 +0200 [thread overview]
Message-ID: <20260719-sloppy-cornflower-hippo-8212e2@quoll> (raw)
In-Reply-To: <20260717-glymur_linkmode_0717-v5-1-4f9e87a61463@oss.qualcomm.com>
On Fri, Jul 17, 2026 at 02:58:33AM -0700, Qiang Yu wrote:
> diff --git a/Documentation/devicetree/bindings/phy/qcom,glymur-qmp-pcie-multiphy.yaml b/Documentation/devicetree/bindings/phy/qcom,glymur-qmp-pcie-multiphy.yaml
> new file mode 100644
> index 000000000000..73550f77e9b6
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/phy/qcom,glymur-qmp-pcie-multiphy.yaml
Filename: qcom,glymur-qmp-gen5x8-pcie-phy.yaml
> @@ -0,0 +1,176 @@
> +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/phy/qcom,glymur-qmp-pcie-multiphy.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Qualcomm QMP PCIe multiple link-mode PHY controller (PCIe, Glymur)
> +
> +maintainers:
> + - Qiang Yu <qiang.yu@oss.qualcomm.com>
> + - Manivannan Sadhasivam <manivannan.sadhasivam@oss.qualcomm.com>
> +
> +description: |
> + The Glymur SoC uses a single PCIe Gen5 PHY hardware block for the
> + PCIe3a/PCIe3b controllers. This block supports two link modes, selected
> + at runtime via a TCSR syscon register:
> +
> + 1. x8 - a single 8-lane PHY instance is exposed (PCIe3a only)
> + 2. x4+x4 - two independent 4-lane PHY instances are exposed (PCIe3a and
> + PCIe3b)
> +
> + The node always describes both PHY instances ("port a" and "port b"),
> + regardless of which link mode is active on the board.
> +
> +properties:
> + compatible:
> + enum:
> + - qcom,glymur-qmp-gen5x8-pcie-phy
> +
> + reg:
> + minItems: 2
Dop
> + maxItems: 2
> +
> + reg-names:
> + items:
> + - const: port_a
> + - const: port_b
> +
> + clocks:
> + minItems: 10
Drop
> + maxItems: 10
> +
> + clock-names:
> + items:
> + - const: aux
> + - const: cfg_ahb
> + - const: ref
> + - const: rchng
> + - const: pipe
> + - const: phy_b_aux
> + - const: cfg_ahb_b
> + - const: rchng_b
> + - const: pipe_b
> + - const: pipediv2_b
> +
> + power-domains:
> + minItems: 2
Drop
> + maxItems: 2
> +
> + power-domain-names:
> + items:
> + - const: phy_a_gdsc
port_a
> + - const: phy_b_gdsc
port_b
> +
> + resets:
> + minItems: 4
Drop
> + maxItems: 4
> +
> + reset-names:
> + items:
> + - const: phy_a
port_a
> + - const: phy_a_nocsr
port_a_nocsr
etc.
> + - const: phy_b
> + - const: phy_b_nocsr
> +
> + vdda-phy-supply: true
> +
> + vdda-pll-supply: true
> +
> + vdda-refgen0p9-supply: true
> +
> + vdda-refgen1p2-supply: true
> +
> + qcom,link-mode:
> + description:
> + Reference to a register in the TCSR syscon that reports the link
> + mode the PCIe PHY is currently configured for, either a single x8
> + link or two independent x4 links. The link mode is programmed by
> + firmware before Linux boots; this property is only used to read
> + the active link mode, specified as a phandle to the syscon and
> + the register offset.
> + $ref: /schemas/types.yaml#/definitions/phandle-array
> + items:
> + - items:
> + - description: phandle of TCSR syscon
> + - description: offset of link mode register
> +
> + "#clock-cells":
> + const: 1
> +
> + clock-output-names:
> + items:
> + - description: Name of the PHY A pipe clock output.
> + - description: Name of the PHY B pipe clock output.
> +
> + "#phy-cells":
> + const: 1
You should explain in description the meaning of cell value. Or provide
filename of header with constants.
> +
> +required:
> + - compatible
> + - reg
> + - reg-names
> + - clocks
> + - clock-names
> + - power-domains
> + - power-domain-names
> + - resets
> + - reset-names
> + - vdda-phy-supply
> + - vdda-pll-supply
> + - vdda-refgen0p9-supply
> + - vdda-refgen1p2-supply
> + - qcom,link-mode
> + - "#clock-cells"
> + - clock-output-names
> + - "#phy-cells"
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + #include <dt-bindings/clock/qcom,glymur-gcc.h>
> + #include <dt-bindings/clock/qcom,glymur-tcsr.h>
> +
> + pcie3_phy: phy@f00000 {
Drop unused label.
The old 5x4 glymur compatible could be deprecated as well, but fine for
me without doing so.
Best regards,
Krzysztof
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
next prev parent reply other threads:[~2026-07-19 6:50 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-17 9:58 [PATCH v5 0/3] Add QMP PCIe multiple link-mode PHY support Qiang Yu
2026-07-17 9:58 ` Qiang Yu
2026-07-17 9:58 ` [PATCH v5 1/3] dt-bindings: phy: qcom: Add Glymur QMP PCIe multiple link-mode PHY Qiang Yu
2026-07-17 9:58 ` Qiang Yu
2026-07-19 6:50 ` Krzysztof Kozlowski [this message]
2026-07-19 6:50 ` Krzysztof Kozlowski
2026-07-20 3:26 ` Qiang Yu
2026-07-20 3:26 ` Qiang Yu
2026-07-17 9:58 ` [PATCH v5 2/3] phy: qcom: qmp-pcie: Add QMP PCIe Multi-PHY driver Qiang Yu
2026-07-17 9:58 ` Qiang Yu
2026-07-17 22:45 ` Bjorn Andersson
2026-07-17 22:45 ` Bjorn Andersson
2026-07-20 3:36 ` Qiang Yu
2026-07-20 3:36 ` Qiang Yu
2026-07-17 9:58 ` [PATCH v5 3/3] arm64: dts: qcom: glymur: Wire PCIe3a/3b to shared Gen5x8 PHY Qiang Yu
2026-07-17 9:58 ` Qiang Yu
2026-07-17 16:50 ` Konrad Dybcio
2026-07-17 16:50 ` Konrad Dybcio
2026-07-20 3:44 ` Qiang Yu
2026-07-20 3:44 ` Qiang Yu
2026-07-19 6:43 ` [PATCH v5 0/3] Add QMP PCIe multiple link-mode PHY support Krzysztof Kozlowski
2026-07-19 6:43 ` Krzysztof Kozlowski
2026-07-20 3:29 ` Qiang Yu
2026-07-20 3:29 ` Qiang Yu
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=20260719-sloppy-cornflower-hippo-8212e2@quoll \
--to=krzk@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=manivannan.sadhasivam@oss.qualcomm.com \
--cc=neil.armstrong@linaro.org \
--cc=p.zabel@pengutronix.de \
--cc=qiang.yu@oss.qualcomm.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 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.