[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <5084a99a-9140-4c4f-9873-f5478f48a49d@ieee.org>
Date: Tue, 10 Jun 2025 14:57:48 -0500
From: Alex Elder <elder@...e.org>
To: Ze Huang <huangze@...t.edu.cn>, Vinod Koul <vkoul@...nel.org>,
Kishon Vijay Abraham I <kishon@...nel.org>, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley
<conor+dt@...nel.org>, Yixun Lan <dlan@...too.org>,
Philipp Zabel <p.zabel@...gutronix.de>
Cc: linux-phy@...ts.infradead.org, devicetree@...r.kernel.org,
linux-riscv@...ts.infradead.org, spacemit@...ts.linux.dev,
linux-kernel@...r.kernel.org, Junzhong Pan <junzhong.pan@...cemit.com>
Subject: Re: [PATCH v5 2/4] dt-bindings: phy: spacemit: add K1 PCIe/USB3 combo
PHY
On 5/27/25 7:01 AM, Ze Huang wrote:
> Introduce support for SpacemiT K1 PCIe/USB3 combo PHY controller.
>
> PCIe portA and USB3 controller share this phy, only one of them can work
> at any given application scenario.
>
> Reviewed-by: Rob Herring (Arm) <robh@...nel.org>
> Co-developed-by: Junzhong Pan <junzhong.pan@...cemit.com>
> Signed-off-by: Junzhong Pan <junzhong.pan@...cemit.com>
> Signed-off-by: Ze Huang <huangze@...t.edu.cn>
This PHY has an interaction with PCIe port A.
In practice this PHY is only used for USB 3.0 (not PCIe).
However I am told that only the PHY used for port A is capable
of performing a resistor termination/tuning process (not ports
B and C). As a result, the PCIe driver needs this process to
complete on the PHY for port A; it can then read the port A TX
and RX calibration values (4 bits each). It uses these values
to configure the PHYs for ports B and C.
For this reason, this PHY code (and binding) should not be
merged until we are sure that the solution will also satisfy
these PCIe requirements.
-Alex
> ---
> .../bindings/phy/spacemit,k1-combphy.yaml | 72 ++++++++++++++++++++++
> 1 file changed, 72 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/phy/spacemit,k1-combphy.yaml b/Documentation/devicetree/bindings/phy/spacemit,k1-combphy.yaml
> new file mode 100644
> index 0000000000000000000000000000000000000000..93f7a3bb06bba380def77f87f6db0184af26e9e6
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/phy/spacemit,k1-combphy.yaml
> @@ -0,0 +1,72 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/phy/spacemit,k1-combphy.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: SpacemiT K1 PCIe/USB3 Combo PHY
> +
> +maintainers:
> + - Ze Huang <huangze9015@...il.com>
> +
> +description:
> + Combo PHY on SpacemiT K1 SoC. PCIe port A and USB3 controller share this
> + phy, only one of PCIe port A and USB3 port can work at any given application
> + scenario.
> +
> +properties:
> + compatible:
> + const: spacemit,k1-combphy
> +
> + reg:
> + items:
> + - description: PHY control registers
> + - description: PCIe/USB3 mode selection register
> +
> + reg-names:
> + items:
> + - const: ctrl
> + - const: sel
> +
> + resets:
> + maxItems: 1
> +
> + "#phy-cells":
> + const: 1
> + description:
> + Indicates the PHY mode to select. The value determines whether the PHY
> + operates in PCIe or USB3 mode.
> +
> + spacemit,lfps-threshold:
> + description:
> + Controls the LFPS signal detection threshold, affects polling.LFPS
> + handshake. Lower the threshold when core voltage rises.
> + $ref: /schemas/types.yaml#/definitions/uint32
> + minimum: 0
> + maximum: 0xff
> +
> + spacemit,rx-always-on:
> + description:
> + Affects RX.detect, enhance compatibility of some DFPs in device mode but
> + increase power consumption.
> + type: boolean
> +
> +required:
> + - compatible
> + - reg
> + - reg-names
> + - resets
> + - "#phy-cells"
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + phy@...10000 {
> + compatible = "spacemit,k1-combphy";
> + reg = <0xc0b10000 0x800>,
> + <0xd4282910 0x400>;
> + reg-names = "ctrl", "sel";
> + resets = <&syscon_apmu 19>;
> + #phy-cells = <1>;
> + };
>
Powered by blists - more mailing lists