new file mode 100644
@@ -0,0 +1,54 @@
+# SPDX-License-Identifier: GPL-2.0-only or BSD-2-Clause
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/usb/onboard_usb_hub.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: Binding for onboard USB hubs
+
+maintainers:
+ - Matthias Kaehlcke <mka@chromium.org>
+
+properties:
+ compatible:
+ items:
+ - enum:
+ - realtek,rts5411
+ - const: onboard-usb-hub
+
+ vdd-supply:
+ description:
+ phandle to the regulator that provides power to the hub.
+
+required:
+ - compatible
+ - vdd-supply
+
+examples:
+ - |
+ usb_hub: usb-hub {
+ compatible = "realtek,rts5411", "onboard-usb-hub";
+ vdd-supply = <&pp3300_hub>;
+ };
+
+ usb_controller {
+ dr_mode = "host";
+ #address-cells = <1>;
+ #size-cells = <0>;
+
+ /* 2.0 hub on port 1 */
+ hub@1 {
+ compatible = "usbbda,5411";
+ reg = <1>;
+ hub = <&usb_hub>;
+ };
+
+ /* 3.0 hub on port 2 */
+ hub@2 {
+ compatible = "usbbda,411";
+ reg = <2>;
+ hub = <&usb_hub>;
+ };
+ };
+
+...
Discrete onboard USB hubs (an example for such a hub is the Realtek RTS5411) need to be powered and may require initialization of other resources (like GPIOs or clocks) to work properly. This adds a device tree binding for these hubs. Signed-off-by: Matthias Kaehlcke <mka@chromium.org> --- Changes in v3: - updated commit message - removed recursive reference to $self - adjusted 'compatible' definition to support multiple entries - changed USB controller phandle to be a node Changes in v2: - removed 'wakeup-source' and 'power-off-in-suspend' properties - consistently use spaces for indentation in example .../bindings/usb/onboard_usb_hub.yaml | 54 +++++++++++++++++++ 1 file changed, 54 insertions(+) create mode 100644 Documentation/devicetree/bindings/usb/onboard_usb_hub.yaml