From: Frank Wang <frank.wang@rock-chips.com>
To: Guenter Roeck <linux@roeck-us.net>, heiko@sntech.de
Cc: dianders@chromium.org, kishon@ti.com, robh+dt@kernel.org,
pawel.moll@arm.com, mark.rutland@arm.com,
ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-usb@vger.kernel.org, linux-rockchip@lists.infradead.org,
jwerner@chromium.org, xzy.xu@rock-chips.com,
huangtao@rock-chips.com, kever.yang@rock-chips.com,
william.wu@rock-chips.com, frank.wang@rock-chips.com
Subject: Re: [v2, 1/2] Documentation: bindings: add DT documentation for Rockchip USB2PHY
Date: Mon, 6 Jun 2016 12:30:11 +0800 [thread overview]
Message-ID: <59bd62b5-cc4f-68ce-e4d8-bd96e52db8bd@rock-chips.com> (raw)
In-Reply-To: <20160603192532.GA4241@roeck-us.net>
Hi Guenter,
On 2016/6/4 3:25, Guenter Roeck wrote:
> On Thu, Jun 02, 2016 at 02:48:09PM +0800, Frank Wang wrote:
>> Signed-off-by: Frank Wang <frank.wang@rock-chips.com>
>> ---
>>
>> Changes in v2:
>> - Changed vbus_host optional property from gpio to regulator.
>> - Specified vbus_otg-supply optional property.
>> - Specified otg_id and otg_bvalid property.
>>
>> .../bindings/phy/phy-rockchip-inno-usb2.txt | 55 ++++++++++++++++++++
>> 1 file changed, 55 insertions(+)
>> create mode 100644 Documentation/devicetree/bindings/phy/phy-rockchip-inno-usb2.txt
>>
>> diff --git a/Documentation/devicetree/bindings/phy/phy-rockchip-inno-usb2.txt b/Documentation/devicetree/bindings/phy/phy-rockchip-inno-usb2.txt
>> new file mode 100644
>> index 0000000..132e707
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/phy/phy-rockchip-inno-usb2.txt
>> @@ -0,0 +1,55 @@
>> +ROCKCHIP USB2.0 PHY WITH INNO IP BLOCK
>> +
>> +Required properties (phy (parent) node):
>> + - compatible : should contain:
>> + * "rockchip,rk3366-usb2phy"
>> + * "rockchip,rk3399-usb2phy"
>> + - #clock-cells : should be 0.
>> + - clock-names : specify the 480m output clk name.
>> +
>> +Optional properties:
>> + - vbus_host-supply : phandle to a regulator that supplies host vbus.
>> + - vbus_otg-supply : phandle to a regulator that supplies otg vbus.
>> +
>> +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.
>> +
> Would it make sense to also specify the sub-node names ? The driver matches
> "host-port", and presumably once supported "otg-port". Someone not knowing
> this may specify "hostport" or some other name variant and wonder why nothing
> works as expected.
Well, Yeah, I will correct it in the next patch (patch v3).
>> +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:
>> + * "otg_id" : for the otg id interrupt.
>> + * "otg_bvalid" : for the otg vbus interrupt.
>> + * "linestate" : for the host or otg linestate interrupt.
>> +
>> +Example:
>> +
>> +grf: syscon@ff770000 {
>> + compatible = "rockchip,rk3366-grf", "syscon", "simple-mfd";
>> + #address-cells = <1>;
>> + #size-cells = <1>;
>> +
>> +...
>> +
>> + u2phy: usb2-phy {
>> + compatible = "rockchip,rk3366-usb2phy";
>> + #clock-cells = <0>;
>> + clock-output-names = "sclk_otgphy0_480m";
>> +
>> + u2phy_otg: otg-port {
>> + #phy-cells = <0>;
>> + interrupts = <GIC_SPI 93 IRQ_TYPE_LEVEL_HIGH>,
>> + <GIC_SPI 94 IRQ_TYPE_LEVEL_HIGH>,
>> + <GIC_SPI 95 IRQ_TYPE_LEVEL_HIGH>;
>> + interrupt-names = "otg_id", "otg_bvalid", "linestate";
>> + status = "okay";
>> + };
>> +
>> + u2phy_host: host-port {
>> + #phy-cells = <0>;
>> + interrupts = <GIC_SPI 96 IRQ_TYPE_LEVEL_HIGH>;
>> + interrupt-names = "linestate";
>> + status = "okay";
>> + };
>> + };
>> +};
>
>
next prev parent reply other threads:[~2016-06-06 4:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-02 6:48 [PATCH v2 0/2] Add a new Rockchip usb2 phy driver Frank Wang
2016-06-02 6:48 ` [PATCH v2 1/2] Documentation: bindings: add DT documentation for Rockchip USB2PHY Frank Wang
[not found] ` <1464850090-99371-2-git-send-email-frank.wang-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2016-06-03 19:25 ` [v2, " Guenter Roeck
2016-06-06 4:30 ` Frank Wang [this message]
2016-06-02 6:48 ` [PATCH v2 2/2] phy: rockchip-inno-usb2: add a new driver for Rockchip usb2phy Frank Wang
[not found] ` <1464850090-99371-3-git-send-email-frank.wang-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2016-06-03 19:57 ` [v2, " Guenter Roeck
2016-06-06 4:45 ` Frank Wang
2016-06-03 19:59 ` Guenter Roeck
[not found] ` <20160603195922.GB3524-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>
2016-06-03 21:24 ` Heiko Stübner
2016-06-06 4:51 ` 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=59bd62b5-cc4f-68ce-e4d8-bd96e52db8bd@rock-chips.com \
--to=frank.wang@rock-chips.com \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=galak@codeaurora.org \
--cc=heiko@sntech.de \
--cc=huangtao@rock-chips.com \
--cc=ijc+devicetree@hellion.org.uk \
--cc=jwerner@chromium.org \
--cc=kever.yang@rock-chips.com \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=william.wu@rock-chips.com \
--cc=xzy.xu@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