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

[Hongliang Yang <hongliang.yang@cixtech.com>]

On 06/09/2026 06:45, Krzysztof Kozlowski wrote:
> In the description you describe hardware, not binding.
>
>> +  glue nodes can reference their register offsets through the
>> +  cix,usb-rcsu phandle (see cix,sky1-usbssp.yaml).
>
> Syscon is not a USB device. This is not supposed to be in USB.

Understood. We will drop the syscon node and this binding entirely.

To explain the hardware first, so that we agree on the target shape:

USB4 (controller 0) and USB5 (controller 1) do not have their own glue
register bank inside the controller address space. Their glue registers
live in a shared RCSU register region in the SoC system control
aperture (0x091c0000 ~ 0x091c0440). Within that region each controller
owns its own registers and the two sets do not overlap:

  - USB4: AXI bus attribute configuration register at 0x091c0314 and
    controller status registers (clock enable/valid/req flags) at
    0x091c0400 ~ 0x091c040c
  - USB5: AXI bus attribute configuration register at 0x091c0324 and
    controller status registers at 0x091c0410 ~ 0x091c041c

Only the USB controllers use these registers. The remaining USB
controllers (USB0 ~ USB3) each have their own private RCSU slice
elsewhere in the same aperture, one slice per controller.

Following your feedback on the wrapper node ("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"), our plan for v5 is to
drop the separate glue node and merge everything into a single node,
in the same shape as socionext,uniphier-dwc3:

    usb@91d0000 {
        compatible = "cix,sky1-usbssp", "cdns,usb3";
        reg = <0x00 0x91d0000 0x00 0x4000>,   /* otg */
              <0x00 0x91d8000 0x00 0x8000>,   /* xhci */
              <0x00 0x91d4000 0x00 0x4000>,   /* dev */
              <0x00 0x091c0314 0x00 0x10>,    /* axi attribute cfg */
              <0x00 0x091c0400 0x00 0x10>;    /* controller status */
        reg-names = "otg", "xhci", "dev", "axi", "status";
        /* clocks, resets, interrupts, phys, dr_mode, cix,usb-syscon */
    };

The cix,sky1-usbssp binding would then $ref cdns,usb3.yaml and add the
two extra reg entries plus the Sky1 glue properties (clocks, resets and
the cix,usb-syscon phandle to the S5 system controller for mode
straps, which also provides the resets). No syscon node, no wrapper
node, no child node.

On the driver side the Sky1 glue driver would follow the same approach
as the DWC3 glue drivers (e.g. dwc3-generic-plat / dwc3-imx8mp): the
glue driver binds the single node and initializes the Cadence core
in-process instead of populating a child device, with the core probe
split into an exported helper as done for DWC3.

Does this match what you had in mind, or would you prefer a different
split of the reg entries / naming?

Best regards,
Hongliang Yang