From: Frank Wang <frank.wang@rock-chips.com>
To: heiko@sntech.de, kishon@ti.com, robh+dt@kernel.org,
mark.rutland@arm.com, gregkh@linuxfoundation.org
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-rockchip@lists.infradead.org, huangtao@rock-chips.com,
william.wu@rock-chips.com, daniel.meng@rock-chips.com,
kever.yang@rock-chips.com, andy.yan@rock-chips.com,
wmc@rock-chips.com, Frank Wang <frank.wang@rock-chips.com>
Subject: [PATCH v3 4/5] dt-bindings: phy-rockchip-inno-usb2: add otg-mux interrupt
Date: Thu, 3 Aug 2017 16:09:12 +0800 [thread overview]
Message-ID: <1501747753-6983-5-git-send-email-frank.wang@rock-chips.com> (raw)
In-Reply-To: <1501747753-6983-1-git-send-email-frank.wang@rock-chips.com>
Add otg-mux property to support multiplexed interrupt in otg-port
on some Rockchip SoC (e.g RV1108).
Signed-off-by: Frank Wang <frank.wang@rock-chips.com>
---
Documentation/devicetree/bindings/phy/phy-rockchip-inno-usb2.txt | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/phy/phy-rockchip-inno-usb2.txt b/Documentation/devicetree/bindings/phy/phy-rockchip-inno-usb2.txt
index ddf868a..ed6aee4 100644
--- a/Documentation/devicetree/bindings/phy/phy-rockchip-inno-usb2.txt
+++ b/Documentation/devicetree/bindings/phy/phy-rockchip-inno-usb2.txt
@@ -32,10 +32,14 @@ Required nodes : a sub-node is required for each port the phy provides.
Required properties (port (child) node):
- #phy-cells : must be 0. See ./phy-bindings.txt for details.
- interrupts : specify an interrupt for each entry in interrupt-names.
- - interrupt-names : a list which shall be the following entries:
+ - interrupt-names : a list which should be one of the following cases:
+ Regular case:
* "otg-id" : for the otg id interrupt.
* "otg-bvalid" : for the otg vbus interrupt.
* "linestate" : for the host/otg linestate interrupt.
+ Some SoCs use one interrupt with the obove muxed together, so for these
+ * "otg-mux" : otg-port interrupt, which mux otg-id/otg-bvalid/linestate
+ to one.
Optional properties:
- phy-supply : phandle to a regulator that provides power to VBUS.
--
2.0.0
next prev parent reply other threads:[~2017-08-03 8:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-03 8:09 [PATCH v3 0/5] add some quirks for Rockchip usb2-phy and add rv1108 SoCs' support Frank Wang
2017-08-03 8:09 ` [PATCH v3 1/5] phy: rockchip-inno-usb2: add companion grf quirk Frank Wang
2017-08-03 8:09 ` [PATCH v3 2/5] dt-bindings: phy-rockchip-inno-usb2: " Frank Wang
2017-08-10 17:05 ` Rob Herring
2017-08-11 1:43 ` Frank Wang
2017-08-03 8:09 ` [PATCH v3 3/5] phy: rockchip-inno-usb2: add support for otg-mux interrupt Frank Wang
2017-08-03 8:09 ` Frank Wang [this message]
2017-08-10 17:06 ` [PATCH v3 4/5] dt-bindings: phy-rockchip-inno-usb2: add " Rob Herring
2017-08-11 1:46 ` Frank Wang
2017-08-03 8:10 ` [PATCH v3 5/5] phy: rockchip-inno-usb2: add support of usb2-phy for rv1108 SoCs Frank Wang
2017-08-10 17:07 ` Rob Herring
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=1501747753-6983-5-git-send-email-frank.wang@rock-chips.com \
--to=frank.wang@rock-chips.com \
--cc=andy.yan@rock-chips.com \
--cc=daniel.meng@rock-chips.com \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=heiko@sntech.de \
--cc=huangtao@rock-chips.com \
--cc=kever.yang@rock-chips.com \
--cc=kishon@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=william.wu@rock-chips.com \
--cc=wmc@rock-chips.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).