From: Frank Wang <frank.wang@rock-chips.com>
To: "Heiko Stübner" <heiko@sntech.de>
Cc: kishon@ti.com, robh+dt@kernel.org, mark.rutland@arm.com,
gregkh@linuxfoundation.org, 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
Subject: Re: [PATCH v2 4/5] dt-bindings: phy-rockchip-inno-usb2: add otg mux irq quirk
Date: Thu, 3 Aug 2017 09:47:37 +0800 [thread overview]
Message-ID: <0cd69042-5ff5-900a-fe6e-c162452b71bf@rock-chips.com> (raw)
In-Reply-To: <2188240.QH672TG27n@diego>
Hi Heiko,
On 2017/8/2 19:25, Heiko Stübner wrote:
> Hi Frank,
>
> Am Mittwoch, 2. August 2017, 15:53:09 CEST schrieb Frank Wang:
>> Add rockchip,otg_mux_irq_quirk property to support the otg-id/
>> otg-bvalid/linestate irqs that are multiplexed to one irq in
>> otg-port on some special Rockchip SoCs (e.g RV1108).
>>
>> Signed-off-by: Frank Wang <frank.wang@rock-chips.com>
>> ---
>> Documentation/devicetree/bindings/phy/phy-rockchip-inno-usb2.txt | 5 +++++
>> 1 file changed, 5 insertions(+)
>>
>> diff --git
>> a/Documentation/devicetree/bindings/phy/phy-rockchip-inno-usb2.txt
>> b/Documentation/devicetree/bindings/phy/phy-rockchip-inno-usb2.txt index
>> ddf868a..d49572b 100644
>> --- a/Documentation/devicetree/bindings/phy/phy-rockchip-inno-usb2.txt
>> +++ b/Documentation/devicetree/bindings/phy/phy-rockchip-inno-usb2.txt
>> @@ -22,6 +22,8 @@ Optional properties:
>> register files".
>> - rockchip,companion_grf_quirk : when set driver will request
>> "rockchip,usbgrf" phandle as one companion-grf.
>> + - rockchip,otg_mux_irq_quirk: set if otg-id/otg-bvalid/linestate irqs
>> + are multiplexed to one irq in otg-port on some SoCs.
>>
>> Required nodes : a sub-node is required for each port the phy provides.
>> The sub-node name is used to identify host or otg port,
>> @@ -36,6 +38,9 @@ Required properties (port (child) node):
>> * "otg-id" : for the otg id interrupt.
>> * "otg-bvalid" : for the otg vbus interrupt.
>> * "linestate" : for the host/otg linestate interrupt.
>> + * "otg-mux" : otg-port interrupt, which multiplex otg-id/otg-bvalid/
>> + linestate irqs to one irq. Should specify if
>> + rockchip,otg_mux_irq_quirk property is set.
> I'd think that should be auto-detectable in the driver without the quirk
> property above?
>
> I.e. check for the otg-mux interrupt first on probe and if can be found, you
> know that this is the case, otherwise look for the regular interrupts.
>
>
> Also I would write that down a bit differently, so that it doesn't confuse
> people. Something similar to:
>
> - interrupt-names : a list which should
> + 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 multiplex otg-id/otg-bvalid/
> + linestate irqs to one irq.
>
>
> Heiko
>
Thanks for your comments, I will fix it in next version.
BR.
Frank
next prev parent reply other threads:[~2017-08-03 1:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-02 7:53 [PATCH v2 0/5] add some quirks for Rockchip usb2-phy and add rv1108 SoCs' support Frank Wang
2017-08-02 7:53 ` [PATCH v2 1/5] phy: rockchip-inno-usb2: add companion grf quirk Frank Wang
2017-08-02 7:53 ` [PATCH v2 2/5] dt-bindings: phy-rockchip-inno-usb2: " Frank Wang
2017-08-02 7:53 ` [PATCH v2 3/5] phy: rockchip-inno-usb2: add otg mux irq quirk Frank Wang
2017-08-02 7:53 ` [PATCH v2 4/5] dt-bindings: phy-rockchip-inno-usb2: " Frank Wang
2017-08-02 11:25 ` Heiko Stübner
2017-08-03 1:47 ` Frank Wang [this message]
2017-08-02 7:54 ` [PATCH v2 5/5] phy: rockchip-inno-usb2: add support of usb2-phy for rv1108 SoCs Frank Wang
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=0cd69042-5ff5-900a-fe6e-c162452b71bf@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
all inboxes | Powered by JetHome®