From: Kunihiko Hayashi <hayashi.kunihiko@socionext.com>
To: "Rob Herring (Arm)" <robh@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Masami Hiramatsu <mhiramat@kernel.org>
Cc: linux-usb@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] dt-bindings: usb: Add Socionext Uniphier DWC3 controller
Date: Tue, 6 Jan 2026 13:33:56 +0900 [thread overview]
Message-ID: <2dde6891-a0e3-4e60-a773-302061a8e5a5@socionext.com> (raw)
In-Reply-To: <20260105162418.2842825-1-robh@kernel.org>
Hi Rob,
On 2026/01/06 1:24, Rob Herring (Arm) wrote:
> The Socionext Uniphier DWC3 controller binding is already in use, but
> undocumented. It's a straight-forward binding similar to other DWC3
> bindings.
>
> Signed-off-by: Rob Herring (Arm) <robh@kernel.org>
> ---
> v2:
> - Allow 1 phy entry for Pro4
> ---
> .../bindings/usb/socionext,uniphier-dwc3.yaml | 89 +++++++++++++++++++
> 1 file changed, 89 insertions(+)
> create mode 100644
> Documentation/devicetree/bindings/usb/socionext,uniphier-dwc3.yaml
>
> diff --git
> a/Documentation/devicetree/bindings/usb/socionext,uniphier-dwc3.yaml
> b/Documentation/devicetree/bindings/usb/socionext,uniphier-dwc3.yaml
> new file mode 100644
> index 000000000000..2b253339c199
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/usb/socionext,uniphier-dwc3.yaml
> @@ -0,0 +1,89 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/usb/socionext,uniphier-dwc3.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Socionext Uniphier SuperSpeed DWC3 USB SoC controller
> +
> +maintainers:
> + - Kunihiko Hayashi <hayashi.kunihiko@socionext.com>
> + - Masami Hiramatsu <mhiramat@kernel.org>
> +
> +select:
> + properties:
> + compatible:
> + contains:
> + const: socionext,uniphier-dwc3
> + required:
> + - compatible
> +
> +properties:
> + compatible:
> + items:
> + - const: socionext,uniphier-dwc3
> + - const: snps,dwc3
> +
> + reg:
> + maxItems: 1
> +
> + interrupts:
> + minItems: 1
> + items:
> + - description: Host or single combined interrupt
> + - description: Peripheral interrupt
> +
> + interrupt-names:
> + minItems: 1
> + items:
> + - enum:
> + - dwc_usb3
> + - host
> + - const: peripheral
> +
> + clocks:
> + maxItems: 3
> +
> + clock-names:
> + items:
> + - const: ref
> + - const: bus_early
> + - const: suspend
> +
> + phys:
> + description: 1 to 4 HighSpeed PHYs followed by 1 or 2 SuperSpeed PHYs
> + minItems: 1
> + maxItems: 6
> +
> + resets:
> + maxItems: 1
> +
> +required:
> + - compatible
> + - reg
> + - interrupts
> + - clocks
> + - clock-names
> + - phys
> +
> +unevaluatedProperties: false
> +
> +allOf:
> + - $ref: snps,dwc3.yaml#
> +
> +examples:
> + - |
> + #include <dt-bindings/interrupt-controller/arm-gic.h>
> +
> + usb@65a00000 {
> + compatible = "socionext,uniphier-dwc3", "snps,dwc3";
> + reg = <0x65a00000 0xcd00>;
> + interrupt-names = "dwc_usb3";
> + interrupts = <GIC_SPI 134 IRQ_TYPE_LEVEL_HIGH>;
> + clock-names = "ref", "bus_early", "suspend";
> + clocks = <&sys_clk 12>, <&sys_clk 12>, <&sys_clk 12>;
> + resets = <&usb0_rst 15>;
> + phys = <&usb0_hsphy0>, <&usb0_hsphy1>,
> + <&usb0_ssphy0>, <&usb0_ssphy1>;
> + dr_mode = "host";
> + };
I've checked this with ARCH=arm and ARCH=arm64.
Reviewed-by: Kunihiko Hayashi <hayashi.kunihiko@socionext.com>
Thank you,
---
Best Regards
Kunihiko Hayashi
prev parent reply other threads:[~2026-01-06 4:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-05 16:24 Rob Herring (Arm)
2026-01-06 4:33 ` Kunihiko Hayashi [this message]
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=2dde6891-a0e3-4e60-a773-302061a8e5a5@socionext.com \
--to=hayashi.kunihiko@socionext.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=robh@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®