From: frank.wang@rock-chips.com (Frank Wang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 4/5] dt-bindings: phy-rockchip-inno-usb2: add otg-mux interrupt
Date: Fri, 11 Aug 2017 09:46:34 +0800 [thread overview]
Message-ID: <4bba0de8-cb15-9f1a-5ecc-61d03804d5da@rock-chips.com> (raw)
In-Reply-To: <20170810170640.xdntfubu3lzoqsad@rob-hp-laptop>
Hi Rob,
On 2017/8/11 1:06, Rob Herring wrote:
> On Thu, Aug 03, 2017 at 04:09:12PM +0800, Frank Wang wrote:
>> 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
> s/obove/above/
Sorry, thanks for your reminding and will fix.
BR.
Frank
>
> With that,
>
> Acked-by: Rob Herring <robh@kernel.org>
>
>
>
next prev parent reply other threads:[~2017-08-11 1:46 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 ` [PATCH v3 4/5] dt-bindings: phy-rockchip-inno-usb2: add " Frank Wang
2017-08-10 17:06 ` Rob Herring
2017-08-11 1:46 ` Frank Wang [this message]
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=4bba0de8-cb15-9f1a-5ecc-61d03804d5da@rock-chips.com \
--to=frank.wang@rock-chips.com \
--cc=linux-arm-kernel@lists.infradead.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).