Currently the dwc3 driver always probes xhci-plat driver
by hardcode in driver. Introduce a property to make this
flexible that a user can probe a xhci glue driver by the
generic dwc3 driver.
Signed-off-by: Puma Hsu <pumahsu@xxxxxxxxxx>
---
Documentation/devicetree/bindings/usb/usb-drd.yaml | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/Documentation/devicetree/bindings/usb/usb-drd.yaml b/Documentation/devicetree/bindings/usb/usb-drd.yaml
index 114fb5dc0498..215fb7f70054 100644
--- a/Documentation/devicetree/bindings/usb/usb-drd.yaml
+++ b/Documentation/devicetree/bindings/usb/usb-drd.yaml
@@ -62,6 +62,12 @@ properties:
enum: [host, peripheral]
default: peripheral
+ xhci-glue:
+ description:
+ Tell dwc3 core driver what xhci specific platform driver we want to probe.
+ The string should match to the name of device_driver of platform_driver
+ in the xhci specific platform driver.
+
additionalProperties: true
examples:
@@ -76,4 +82,5 @@ examples:
phy_type = "utmi_wide";
otg-rev = <0x0200>;
adp-disable;
+ xhci-glue = "xhci-hcd-plat";
};
--
2.44.0.rc0.258.g7320e95886-goog
