From: Conor Dooley <conor@kernel.org>
To: caohang@eswincomputing.com
Cc: gregkh@linuxfoundation.org, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, Thinh.Nguyen@synopsys.com,
p.zabel@pengutronix.de, linux-kernel@vger.kernel.org,
linux-usb@vger.kernel.org, devicetree@vger.kernel.org,
ningyu@eswincomputing.com, linmin@eswincomputing.com,
pinkesh.vaghela@einfochips.com,
Senchuan Zhang <zhangsenchuan@eswincomputing.com>
Subject: Re: [PATCH] dt-bindings: usb: Add ESWIN EIC7700 USB controller
Date: Thu, 16 Oct 2025 16:47:43 +0100 [thread overview]
Message-ID: <20251016-oil-reuse-01758b4165ea@spud> (raw)
In-Reply-To: <20251016094748.722-1-caohang@eswincomputing.com>
[-- Attachment #1: Type: text/plain, Size: 4121 bytes --]
On Thu, Oct 16, 2025 at 05:47:48PM +0800, caohang@eswincomputing.com wrote:
> From: Hang Cao <caohang@eswincomputing.com>
>
> Add Device Tree binding documentation for the ESWIN EIC7700
> usb controller module.
>
> Signed-off-by: Senchuan Zhang <zhangsenchuan@eswincomputing.com>
> Signed-off-by: Hang Cao <caohang@eswincomputing.com>
> ---
> .../bindings/usb/eswin,eic7700-usb.yaml | 99 +++++++++++++++++++
> 1 file changed, 99 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/usb/eswin,eic7700-usb.yaml
>
> diff --git a/Documentation/devicetree/bindings/usb/eswin,eic7700-usb.yaml b/Documentation/devicetree/bindings/usb/eswin,eic7700-usb.yaml
> new file mode 100644
> index 000000000000..589a3ab6c644
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/usb/eswin,eic7700-usb.yaml
> @@ -0,0 +1,99 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/usb/eswin,eic7700-usb.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: ESWIN EIC7700 SoC Usb Controller
> +
> +maintainers:
> + - Wei Yang <yangwei1@eswincomputing.com>
> + - Senchuan Zhang <zhangsenchuan@eswincomputing.com>
> + - Hang Cao <caohang@eswincomputing.com>
> +
> +description:
> + The Usb controller on EIC7700 SoC.
> +
> +allOf:
> + - $ref: snps,dwc3-common.yaml#
> +
> +properties:
> + compatible:
> + const: eswin,eic7700-dwc3
> +
> + reg:
> + maxItems: 1
> +
> + interrupts:
> + maxItems: 1
> +
> + interrupt-names:
> + items:
> + - const: peripheral
> +
> + clocks:
> + maxItems: 3
> +
> + clock-names:
> + items:
> + - const: aclk
> + - const: cfg
> + - const: usb_en
> +
> + resets:
> + maxItems: 2
> +
> + reset-names:
> + items:
> + - const: vaux
> + - const: usb_rst
Drop the _rst here, since this can't be anything other than a reset.
> + eswin,hsp-sp-csr:
> + description:
> + HSP CSR is to control and get status of different high-speed peripherals
> + (such as Ethernet, USB, SATA, etc.) via register, which can tune
> + board-level's parameters of PHY, etc.
> + $ref: /schemas/types.yaml#/definitions/phandle-array
> + items:
> + - items:
> + - description: phandle to HSP Register Controller hsp_sp_csr node.
> + - description: USB bus register offset.
> + - description: AXI low power register offset.
This looks better than before, thanks.
> +
> +required:
> + - compatible
> + - reg
> + - clocks
> + - clock-names
> + - interrupts
> + - interrupt-names
> + - resets
> + - reset-names
> + - eswin,hsp-sp-csr
> +
> +unevaluatedProperties: false
> +
> +examples:
> + - |
> + usb@50480000 {
> + compatible = "eswin,eic7700-dwc3";
> + reg = <0x50480000 0x10000>;
> + clocks = <&clock 135>,
> + <&clock 136>,
> + <&hspcrg 18>;
> + clock-names = "aclk", "cfg", "usb_en";
> + interrupt-parent = <&plic>;
> + interrupts = <85>;
> + interrupt-names = "peripheral";
> + resets = <&reset 84>, <&hspcrg 2>;
> + reset-names = "vaux", "usb_rst";
> + dr_mode = "peripheral";
> + maximum-speed = "high-speed";
> + phy_type = "utmi";
> + snps,dis_enblslpm_quirk;
> + snps,dis-u2-freeclk-exists-quirk;
> + snps,dis_u2_susphy_quirk;
> + snps,dis-del-phy-power-chg-quirk;
> + snps,parkmode-disable-ss-quirk;
If any of these "quirks" are required for the device to function
properly, please mark them as required so that they don't ever get left
out. If it is board dependant, that's fine. I'm only interested in what
is set on the SoC level.
If most properties from the common snps binding are not possible, please
use additionalProperties: false and only permit those that are.
pw-bot: changes-requested
> + eswin,hsp-sp-csr = <&hsp_sp_csr 0x800 0x818>;
> + };
> --
> 2.34.1
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2025-10-16 15:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-16 9:46 [PATCH v4 0/2] Add driver support for ESWIN EIC7700 SoC USB controller caohang
2025-10-16 9:47 ` [PATCH] dt-bindings: usb: Add ESWIN EIC7700 " caohang
2025-10-16 15:47 ` Conor Dooley [this message]
2025-10-16 9:48 ` [PATCH] usb: dwc3: eic7700: Add EIC7700 USB driver caohang
2025-10-16 22:27 ` Thinh Nguyen
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=20251016-oil-reuse-01758b4165ea@spud \
--to=conor@kernel.org \
--cc=Thinh.Nguyen@synopsys.com \
--cc=caohang@eswincomputing.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=krzk+dt@kernel.org \
--cc=linmin@eswincomputing.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=ningyu@eswincomputing.com \
--cc=p.zabel@pengutronix.de \
--cc=pinkesh.vaghela@einfochips.com \
--cc=robh@kernel.org \
--cc=zhangsenchuan@eswincomputing.com \
/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