Re: [PATCH v4 2/4] dt-bindings: usb: Add CIX Sky1 USBSSP controller

[Krzysztof Kozlowski]

On 06/09/2026 05:24, Hongliang Yang wrote:
> Add device tree binding for the CIX Sky1 Cadence USBSSP controller
> glue layer. The integration adds glue registers and mode strap
> controls in the Sky1 S5 system controller. The CIX glue node wraps
> a Cadence USBSSP core as a child node.
> 
> The per-controller RCSU control and status registers live in a shared
> RCSU region described by the cix,sky1-usbss-rcsu binding and are
> referenced through the cix,usb-rcsu phandle.
> 
> The per-controller RCSU registers are accessed through a syscon regmap
> referenced by the cix,usb-rcsu phandle.
> Signed-off-by: Hongliang Yang <hongliang.yang@xxxxxxxxxxx>
> ---
>  .../bindings/usb/cix,sky1-usbssp.yaml         | 144 ++++++++++++++++++
>  MAINTAINERS                                   |   3 +
>  2 files changed, 147 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/usb/cix,sky1-usbssp.yaml
> 
> diff --git a/Documentation/devicetree/bindings/usb/cix,sky1-usbssp.yaml b/Documentation/devicetree/bindings/usb/cix,sky1-usbssp.yaml
> new file mode 100644
> index 000000000000..8e66dea50fa7
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/usb/cix,sky1-usbssp.yaml
> @@ -0,0 +1,144 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/usb/cix,sky1-usbssp.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: CIX Sky1 Cadence USBSSP Controller
> +
> +maintainers:
> +  - Hongliang Yang <hongliang.yang@xxxxxxxxxxx>
> +
> +description:
> +  The CIX Sky1 USBSSP controller is based on the Cadence USBSSP DRD
> +  controller. The integration adds glue registers and mode strap controls
> +  in the Sky1 S5 system controller. The CIX glue node wraps a Cadence
> +  USBSSP core as a child node. The per-controller RCSU control/status
> +  registers live in a shared RCSU region and are accessed through the
> +  cix,usb-rcsu phandle.
> +
> +properties:
> +  compatible:
> +    const: cix,sky1-usbssp
> +

No MMIO here?

> +  cix,usb-rcsu:

Then this is your device.

Last time you claimed you have TWO registers. ONLY. Now you claim you
have entire address space, but somewhere else.

If you do not have here MMIO, then this glue layer is not a separate
device node and you should have one node only, just like we did for DWC.
One node for glue layer and CDNS USB.

If you have here MMIO for some glue over IP block, then it is unlikely
to be a syscon.



> +    $ref: /schemas/types.yaml#/definitions/phandle-array
> +    description: |
> +      A phandle to the USBSSP RCSU system controller region (see
> +      cix,sky1-usbss-rcsu.yaml) followed by two cells: the offset of
> +      the AXI property configuration register and the offset of the
> +      controller status register, both relative to the RCSU region.
> +    items:
> +      items:
> +        - description: phandle to the USBSSP RCSU syscon node
> +        - description: offset of the AXI property configuration register
> +        - description: offset of the controller status register
> +
> +  clocks:
> +    items:
> +      - description: Start-of-frame clock
> +      - description: AXI bus clock
> +      - description: Low-power mode clock
> +      - description: APB register interface clock
> +
> +  clock-names:
> +    items:
> +      - const: sof
> +      - const: axi
> +      - const: lpm
> +      - const: apb
> +
> +  resets:
> +    items:
> +      - description: APB register reset
> +      - description: Controller reset
> +
> +  reset-names:
> +    items:
> +      - const: apb
> +      - const: core
> +
> +  cix,usb-syscon:
> +    $ref: /schemas/types.yaml#/definitions/phandle
> +    description:
> +      Phandle to the Sky1 S5 system controller used to program USB mode
> +      strap controls.

One more syscon?

> +
> +  "#address-cells":
> +    const: 2
> +
> +  "#size-cells":
> +    const: 2
> +
> +  ranges: true
> +
> +patternProperties:
> +  "^usb@[0-9a-f]+$":
> +    $ref: cdns,usb3.yaml#
> +
> +required:
> +  - compatible
> +  - cix,usb-rcsu
> +  - clocks
> +  - clock-names
> +  - resets
> +  - reset-names
> +  - cix,usb-syscon
> +  - "#address-cells"
> +  - "#size-cells"
> +  - ranges
> +
> +unevaluatedProperties: false
> +
> +examples:
> +  - |
> +    #include <dt-bindings/clock/cix,sky1.h>
> +    #include <dt-bindings/interrupt-controller/arm-gic.h>
> +    #include <dt-bindings/reset/cix,sky1-s5-system-control.h>
> +
> +    soc {
> +        #address-cells = <2>;
> +        #size-cells = <2>;
> +
> +        rcsu: syscon@91c0300 {
> +            compatible = "cix,sky1-usbss-rcsu", "syscon";
> +            reg = <0x00 0x091c0300 0x00 0x200>;
> +        };

Drop node irrelevant.


> +
> +        usb-4 {

This is just "usb". Not usb-foo.

> +            compatible = "cix,sky1-usbssp";
> +            ranges;
> +            #address-cells = <2>;
> +
> +            clocks = <&scmi_clk CLK_TREE_USB3A_H0_CLK_SOF>,
> +                     <&scmi_clk CLK_TREE_USB3A_0_AXI_GATE>,
> +                     <&scmi_clk CLK_TREE_USB3A_H0_CLK_LPM>,
> +                     <&scmi_clk CLK_TREE_USB3A_0_APB_GATE>;
> +            clock-names = "sof", "axi", "lpm", "apb";
> +            resets = <&src SKY1_USBC_SS2_PRST_N>,
> +                     <&src SKY1_USBC_SS2_RST_N>;
> +            reset-names = "apb", "core";
> +            #size-cells = <2>;

size-cells follows address-cells.


Best regards,
Krzysztof