From: richard.yu@hpe.com
To: verdun@hpe.com, nick.hawkins@hpe.com, gregkh@linuxfoundation.org,
robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
conor+dt@kernel.org, richard.yu@hpe.com,
linux-usb@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v2 1/3] dt-bindings: usb: Add HPE GXP HUB Controller
Date: Thu, 7 Sep 2023 16:05:59 -0500 [thread overview]
Message-ID: <20230907210601.25284-2-richard.yu@hpe.com> (raw)
In-Reply-To: <20230907210601.25284-1-richard.yu@hpe.com>
From: Richard Yu <richard.yu@hpe.com>
Provide access to the two register regions for GXP HUB
controller through the hpe,gxp-hub binding.
Signed-off-by: Richard Yu <richard.yu@hpe.com>
---
v2:
*Removed the term "virtual" as it is still a device.
*Removed the downstream port number and generic endpoints
number properties from device tree structure.
---
.../devicetree/bindings/usb/hpe,gxp-hub.yaml | 53 +++++++++++++++++++
1 file changed, 53 insertions(+)
create mode 100644 Documentation/devicetree/bindings/usb/hpe,gxp-hub.yaml
diff --git a/Documentation/devicetree/bindings/usb/hpe,gxp-hub.yaml b/Documentation/devicetree/bindings/usb/hpe,gxp-hub.yaml
new file mode 100644
index 000000000000..b3e7bc42d134
--- /dev/null
+++ b/Documentation/devicetree/bindings/usb/hpe,gxp-hub.yaml
@@ -0,0 +1,53 @@
+# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/usb/hpe,gxp-hub.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: HPE GXP USB HUB controller
+
+maintainers:
+ - Nick Hawkins <nick.hawkins@hpe.com>
+ - Richard Yu <richard.yu@hpe.com>
+
+description:
+ The HPE GXP USB HUB Controller implements 1 set of USB
+ register and several sets of device and endpoint registers to support
+ the HUB's downstream USB devices.
+
+properties:
+ compatible:
+ enum:
+ - hpe,gxp-hub
+
+ reg:
+ items:
+ - description: GXP hub (gxphub) controller register set
+ - description: Several sets of Device and Endpoint registers to support
+ the HUB's downstream USB devices.
+
+ reg-names:
+ items:
+ - const: gxphub
+ - const: udc
+
+ interrupts:
+ maxItems: 1
+
+required:
+ - compatible
+ - reg
+ - reg-names
+ - interrupts
+
+additionalProperties: false
+
+examples:
+ - |
+ usb-hub@80400800 {
+ compatible = "hpe,gxp-hub";
+ reg = <0x80400800 0x0200>, <0x80401000 0x8000>;
+ reg-names = "gxphub", "udc";
+ interrupts = <13>;
+ interrupt-parent = <&vic1>;
+ };
--
2.17.1
next prev parent reply other threads:[~2023-09-07 21:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-07 21:05 [PATCH v2 0/3] Add USB driver for HPE GXP Architecture richard.yu
2023-09-07 21:05 ` richard.yu [this message]
2023-09-11 14:57 ` [PATCH v2 1/3] dt-bindings: usb: Add HPE GXP HUB Controller Rob Herring
2023-09-07 21:06 ` [PATCH v2 2/3] usb: gadget: udc: gxp-udc: add HPE GXP USB HUB support richard.yu
2023-10-02 12:21 ` Greg KH
2023-10-25 22:14 ` Yu, Richard
2023-09-07 21:06 ` [PATCH v2 3/3] MAINTAINERS: add USB HUB support for GXP richard.yu
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=20230907210601.25284-2-richard.yu@hpe.com \
--to=richard.yu@hpe.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=nick.hawkins@hpe.com \
--cc=robh+dt@kernel.org \
--cc=verdun@hpe.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;
as well as URLs for NNTP newsgroup(s).