[PATCH 1/2] dt-bindings: phy: Add Sophgo CV1800 USB phy
Conor Dooley
conor at kernel.org
Fri Apr 19 07:26:53 PDT 2024
On Fri, Apr 12, 2024 at 03:22:24PM +0800, Inochi Amaoto wrote:
> The USB phy of Sophgo CV18XX series SoC needs to sense a pin called
> "VBUS_DET" to get the right operation mode. If this pin is not
> connected, it only supports setting the mode manually.
>
> Add USB phy bindings for Sophgo CV18XX/SG200X series SoC.
>
> Signed-off-by: Inochi Amaoto <inochiama at outlook.com>
> ---
> .../bindings/phy/sophgo,cv1800-usb-phy.yaml | 90 +++++++++++++++++++
> 1 file changed, 90 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/phy/sophgo,cv1800-usb-phy.yaml
>
> diff --git a/Documentation/devicetree/bindings/phy/sophgo,cv1800-usb-phy.yaml b/Documentation/devicetree/bindings/phy/sophgo,cv1800-usb-phy.yaml
> new file mode 100644
> index 000000000000..cb394ac5d8c4
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/phy/sophgo,cv1800-usb-phy.yaml
> @@ -0,0 +1,90 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/phy/sophgo,cv1800-usb-phy.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Sophgo CV18XX/SG200X USB 2.0 PHY
> +
> +maintainers:
> + - Inochi Amaoto <inochiama at outlook.com>
> +
> +properties:
> + compatible:
> + const: sophgo,cv1800-usb-phy
> +
> + reg:
> + maxItems: 1
> +
> + "#phy-cells":
> + const: 0
> +
> + clocks:
> + items:
> + - description: PHY clock
> + - description: PHY app clock
> + - description: PHY stb clock
> + - description: PHY lpm clock
> +
> + clock-names:
> + items:
> + - const: phy
> + - const: app
> + - const: stb
> + - const: lpm
> +
> + dr_mode:
> + description: PHY device mode when initing.
"initing" isn't a word, "initialising" is the correct word. Or
"initializing" if you speak American. But if it is just the value during
initialisation, why do we need to know - we can just overwrite it in
software, right?
Are you sure that this is limited to initialisation? I would have
thought that it describes the configuration that the board is in, and is
a fixed property of the system?
> + enum: [host, peripheral, otg]
Rob, I know this is a phy rather than a controller, so referencing
usb-drd.yaml doesn't really make sense, but there are several PHYs using
dr_mode so it feels like there should be something to reference here
rather than defining the property anew.
> +
> + vbus_det-gpios:
> + description: GPIO to the USB OTG VBUS detect pin. This should not be
> + defined if vbus_det gpio and switch gpio are connected.
I don't understand the second sentence here.
> + maxItems: 1
> +
> + sophgo,switch-gpios:
> + description: GPIO for the phy to control connected switch.
> + maxItems: 2
You've got two items here, they should be described. /But/ the property
above says "switch gpio", which is singular. Which is it?
Cheers,
Conor.
> +
> +required:
> + - compatible
> + - "#phy-cells"
> + - clocks
> + - clock-names
> + - dr_mode
> +
> +allOf:
> + - if:
> + properties:
> + dr_mode:
> + const: otg
> + then:
> + required:
> + - vbus_det-gpios
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + phy at 48 {
> + compatible = "sophgo,cv1800-usb-phy";
> + reg = <0x48 0x4>;
> + #phy-cells = <0>;
> + clocks = <&clk 92>, <&clk 93>,
> + <&clk 94>, <&clk 95>;
> + clock-names = "phy", "app", "stb", "lpm";
> + dr_mode = "host";
> + };
> + - |
> + #include <dt-bindings/gpio/gpio.h>
> +
> + phy at 54 {
> + compatible = "sophgo,cv1800-usb-phy";
> + reg = <0x54 0x4>;
> + #phy-cells = <0>;
> + clocks = <&clk 92>, <&clk 93>,
> + <&clk 94>, <&clk 95>;
> + clock-names = "phy", "app", "stb", "lpm";
> + dr_mode = "otg";
> + vbus_det-gpios = <&portb 6 GPIO_ACTIVE_HIGH>;
> + };
> --
> 2.44.0
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 228 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-riscv/attachments/20240419/fc0c124a/attachment.sig>
More information about the linux-riscv
mailing list