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 v3 1/2] dt-bindings: usb: Add ESWIN EIC7700 USB controller
Date: Mon, 15 Sep 2025 18:34:27 +0100 [thread overview]
Message-ID: <20250915-affair-halves-4f881f6c7cdb@spud> (raw)
In-Reply-To: <20250915091024.2128-1-caohang@eswincomputing.com>
[-- Attachment #1: Type: text/plain, Size: 3901 bytes --]
On Mon, Sep 15, 2025 at 05:10:24PM +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..37797b85f417
> --- /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: 2
> +
> + clock-names:
> + items:
> + - const: aclk
> + - const: cfg
> +
> + resets:
> + maxItems: 1
> +
> + reset-names:
> + items:
> + - const: vaux
> +
> + 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 close
> + module's clock,reset module independently and 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.
> + - description: vbus frequency register offset.
> + - description: mpll register offset.
As I mentioned on the shdci binding patch, I'm not happy with the
justification for this phandle. What exactly is the clock that this
controls and why does it not have a dedicated clock-controller driver
and reset-controller driver?
> +
> +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 170>,
> + <&clock 171>;
> + clock-names = "aclk", "cfg";
> + interrupt-parent = <&plic>;
> + interrupts = <85>;
> + interrupt-names = "peripheral";
> + resets = <&reset 84>;
> + reset-names = "vaux";
> + 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;
> + eswin,hsp-sp-csr = <&hsp_sp_csr 0x800 0x818 0x83c 0x840>;
> + };
> --
> 2.34.1
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2025-09-15 17:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-15 8:53 [PATCH v3 0/2] Add driver support for ESWIN EIC7700 SoC USB controller caohang
2025-09-15 9:10 ` [PATCH v3 1/2] dt-bindings: usb: Add ESWIN EIC7700 " caohang
2025-09-15 17:34 ` Conor Dooley [this message]
2025-09-23 4:40 ` Hang Cao
2025-09-24 19:55 ` Conor Dooley
2025-09-26 8:15 ` Hang Cao
2025-09-15 9:10 ` [PATCH v3 2/2] usb: dwc3: eic7700: Add EIC7700 USB driver caohang
2025-09-15 17:31 ` kernel test robot
2025-09-19 21:14 ` 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=20250915-affair-halves-4f881f6c7cdb@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