From: Ryan Chen <ryan_chen@aspeedtech.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Joel Stanley <joel@jms.id.au>,
Andrew Jeffery <andrew@codeconstruct.com.au>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Philipp Zabel <p.zabel@pengutronix.de>
Cc: <linux-usb@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-aspeed@lists.ozlabs.org>, <linux-kernel@vger.kernel.org>,
Ryan Chen <ryan_chen@aspeedtech.com>
Subject: [PATCH v2 1/2] dt-bindings: usb: aspeed,usb-vhub: Add ast2700 support
Date: Fri, 28 Nov 2025 08:27:30 +0800 [thread overview]
Message-ID: <20251128-upstream_vhub-v2-1-1fa66a5833c2@aspeedtech.com> (raw)
In-Reply-To: <20251128-upstream_vhub-v2-0-1fa66a5833c2@aspeedtech.com>
Add the "aspeed,ast2700-usb-vhub" compatible. The ast2700 vhub
controller requires an reset, so make the "resets" property
mandatory for this compatible to reflect the hardware requirement.
Signed-off-by: Ryan Chen <ryan_chen@aspeedtech.com>
---
.../devicetree/bindings/usb/aspeed,usb-vhub.yaml | 22 ++++++++++++++++++++--
1 file changed, 20 insertions(+), 2 deletions(-)
diff --git a/Documentation/devicetree/bindings/usb/aspeed,usb-vhub.yaml b/Documentation/devicetree/bindings/usb/aspeed,usb-vhub.yaml
index 7f22f9c031b2..b8bac2cce949 100644
--- a/Documentation/devicetree/bindings/usb/aspeed,usb-vhub.yaml
+++ b/Documentation/devicetree/bindings/usb/aspeed,usb-vhub.yaml
@@ -17,8 +17,8 @@ description: |+
Supported number of devices and endpoints vary depending on hardware
revisions. AST2400 and AST2500 Virtual Hub supports 5 downstream devices
- and 15 generic endpoints, while AST2600 Virtual Hub supports 7 downstream
- devices and 21 generic endpoints.
+ and 15 generic endpoints, while AST2600 and AST2700 Virtual Hub supports
+ 7 downstream devices and 21 generic endpoints.
properties:
compatible:
@@ -26,6 +26,7 @@ properties:
- aspeed,ast2400-usb-vhub
- aspeed,ast2500-usb-vhub
- aspeed,ast2600-usb-vhub
+ - aspeed,ast2700-usb-vhub
reg:
maxItems: 1
@@ -33,6 +34,9 @@ properties:
clocks:
maxItems: 1
+ resets:
+ maxItems: 1
+
interrupts:
maxItems: 1
@@ -107,6 +111,20 @@ required:
- aspeed,vhub-downstream-ports
- aspeed,vhub-generic-endpoints
+if:
+ properties:
+ compatible:
+ contains:
+ const: aspeed,ast2700-usb-vhub
+
+then:
+ required:
+ - resets
+
+else:
+ properties:
+ resets: false
+
additionalProperties: false
examples:
--
2.34.1
next prev parent reply other threads:[~2025-11-28 0:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-28 0:27 [PATCH v2 0/2] Add AST2700 support for Aspeed vhub Ryan Chen
2025-11-28 0:27 ` Ryan Chen [this message]
2025-11-28 17:32 ` [PATCH v2 1/2] dt-bindings: usb: aspeed,usb-vhub: Add ast2700 support Conor Dooley
2025-11-28 0:27 ` [PATCH v2 2/2] usb: gadget: aspeed-vhub: " Ryan Chen
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=20251128-upstream_vhub-v2-1-1fa66a5833c2@aspeedtech.com \
--to=ryan_chen@aspeedtech.com \
--cc=andrew@codeconstruct.com.au \
--cc=benh@kernel.crashing.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=joel@jms.id.au \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--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