From: Martin Kepplinger <martin.kepplinger@puri.sm>
To: balbi@kernel.org, robh@kernel.org
Cc: gregkh@linuxfoundation.org, linux-usb@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Martin Kepplinger <martin.kepplinger@puri.sm>
Subject: [PATCH 2/2] dt-bindings: usb: dwc3: add optional extcon description
Date: Wed, 18 Mar 2020 09:35:08 +0100 [thread overview]
Message-ID: <20200318083508.20781-2-martin.kepplinger@puri.sm> (raw)
In-Reply-To: <20200318083508.20781-1-martin.kepplinger@puri.sm>
the dwc3 drd module already hooks up an extcon device if described in DT.
Signed-off-by: Martin Kepplinger <martin.kepplinger@puri.sm>
---
Documentation/devicetree/bindings/usb/dwc3.txt | 2 ++
1 file changed, 2 insertions(+)
diff --git a/Documentation/devicetree/bindings/usb/dwc3.txt b/Documentation/devicetree/bindings/usb/dwc3.txt
index 9946ff9ba735..9aa0cefbf5f6 100644
--- a/Documentation/devicetree/bindings/usb/dwc3.txt
+++ b/Documentation/devicetree/bindings/usb/dwc3.txt
@@ -31,6 +31,8 @@ Exception for clocks:
"xlnx,zynqmp-dwc3"
Optional properties:
+ - extcon: phandle for the extcon device dwc3 DRD uses to detect
+ connect/disconnect events.
- usb-phy : array of phandle for the PHY device. The first element
in the array is expected to be a handle to the USB2/HS PHY and
the second element is expected to be a handle to the USB3/SS PHY
--
2.20.1
next prev parent reply other threads:[~2020-03-18 8:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-18 8:35 [PATCH 1/2] usb: dwc3: support continuous runtime PM with dual role Martin Kepplinger
2020-03-18 8:35 ` Martin Kepplinger [this message]
2020-03-30 23:04 ` [PATCH 2/2] dt-bindings: usb: dwc3: add optional extcon description Rob Herring
2020-03-18 11:13 ` [PATCH 1/2] usb: dwc3: support continuous runtime PM with dual role Roger Quadros
2020-03-18 11:16 ` Martin Kepplinger
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=20200318083508.20781-2-martin.kepplinger@puri.sm \
--to=martin.kepplinger@puri.sm \
--cc=balbi@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).