From: Puma Hsu <pumahsu@google.com>
To: mathias.nyman@intel.com, gregkh@linuxfoundation.org,
Thinh.Nguyen@synopsys.com
Cc: badhri@google.com, royluo@google.com, howardyen@google.com,
albertccwang@google.com, raychi@google.com,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
Puma Hsu <pumahsu@google.com>
Subject: [PATCH 1/3] dt-bindings: usb: Add xhci glue driver support
Date: Mon, 19 Feb 2024 14:10:06 +0800 [thread overview]
Message-ID: <20240219061008.1761102-2-pumahsu@google.com> (raw)
In-Reply-To: <20240219061008.1761102-1-pumahsu@google.com>
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@google.com>
---
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
next prev parent reply other threads:[~2024-02-19 6:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-19 6:10 [PATCH 0/3] usb: xhci: Add support for Google XHCI controller Puma Hsu
2024-02-19 6:10 ` Puma Hsu [this message]
2024-02-19 12:18 ` [PATCH 1/3] dt-bindings: usb: Add xhci glue driver support Krzysztof Kozlowski
2024-02-19 6:10 ` [PATCH 2/3] usb: xhci: Add support for Google XHCI controller Puma Hsu
2024-02-19 6:30 ` Greg KH
2024-02-21 9:22 ` Puma Hsu
2024-02-19 12:21 ` Krzysztof Kozlowski
2024-02-21 9:31 ` Puma Hsu
2024-02-21 9:52 ` Krzysztof Kozlowski
2024-02-22 9:45 ` Puma Hsu
2024-02-19 6:10 ` [PATCH 3/3] MAINTAINERS: Add maintainer for Google USB XHCI driver Puma Hsu
2024-02-19 6:31 ` Greg KH
2024-02-19 8:35 ` Puma Hsu
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=20240219061008.1761102-2-pumahsu@google.com \
--to=pumahsu@google.com \
--cc=Thinh.Nguyen@synopsys.com \
--cc=albertccwang@google.com \
--cc=badhri@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=howardyen@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@intel.com \
--cc=raychi@google.com \
--cc=royluo@google.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