From: Kunihiko Hayashi <hayashi.kunihiko@socionext.com>
To: Rob Herring <robh@kernel.org>
Cc: Philipp Zabel <p.zabel@pengutronix.de>,
Mark Rutland <mark.rutland@arm.com>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
Masami Hiramatsu <masami.hiramatsu@linaro.org>,
Jassi Brar <jaswinder.singh@linaro.org>
Subject: Re: [PATCH 1/2] dt-bindings: reset: uniphier: add USB3 controller reset support
Date: Wed, 04 Jul 2018 10:09:38 +0900 [thread overview]
Message-ID: <20180704100938.8235.4A936039@socionext.com> (raw)
In-Reply-To: <20180703233747.GA850@rob-hp-laptop>
Hi Rob,
On Tue, 3 Jul 2018 17:37:47 -0600 <robh@kernel.org> wrote:
> On Fri, Jun 29, 2018 at 05:11:30PM +0900, Kunihiko Hayashi wrote:
> > Add DT bindings for reset control of USB3 controller implemented in
> > UniPhier SoCs.
> >
> > Signed-off-by: Kunihiko Hayashi <hayashi.kunihiko@socionext.com>
> > ---
> > .../devicetree/bindings/reset/uniphier-reset.txt | 45 ++++++++++++++++++++++
> > 1 file changed, 45 insertions(+)
> >
> > diff --git a/Documentation/devicetree/bindings/reset/uniphier-reset.txt b/Documentation/devicetree/bindings/reset/uniphier-reset.txt
> > index 93efed6..f21d81c 100644
> > --- a/Documentation/devicetree/bindings/reset/uniphier-reset.txt
> > +++ b/Documentation/devicetree/bindings/reset/uniphier-reset.txt
> > @@ -118,3 +118,48 @@ Example:
> >
> > other nodes ...
> > };
> > +
> > +
> > +USB3 controller reset
> > +---------------------
> > +
> > +Required properties:
> > +- compatible: Should be
> > + "socionext,uniphier-pro4-usb3-reset" - for Pro4 SoC
> > + "socionext,uniphier-pxs2-usb3-reset" - for PXs2 SoC
> > + "socionext,uniphier-ld20-usb3-reset" - for LD20 SoC
> > + "socionext,uniphier-pxs3-usb3-reset" - for PXs3 SoC
> > +- #reset-cells: Should be 1.
> > +- reg: Specifies offset and length of the register set for the device.
> > +- clocks: A list of phandles to the clock gate for USB3 glue layer.
> > + According to the clock-names, appropriate clocks are required.
> > +- clock-names: Should contain
> > + "gio", "link" - for Pro4 SoC
> > + "link" - for others
> > +- resets: A list of phandles to the reset control for USB3 glue layer.
> > + According to the reset-names, appropriate resets are required.
> > +- reset-names: Should contain
> > + "gio", "link" - for Pro4 SoC
> > + "link" - for others
> > +
> > +Example:
> > +
> > + usb-glue@65b00000 {
> > + compatible = "socionext,uniphier-ld20-dwc3-glue",
> > + "simple-mfd";
> > + #address-cells = <1>;
> > + #size-cells = <1>;
> > + ranges = <0 0x65b00000 0x400>;
> > +
> > + usb_rst: reset@0 {
> > + compatible = "socionext,uniphier-ld20-usb3-reset";
>
> This looks weird. You have a reset controller within the USB block? And
> then a parent reset controller too?
Yes, this reset control is included in USB3 glue layer, and this is necessary
to enable USB3 core. The following diagram shows those relationships.
USB3 block
|
+---USB3 glue layer
| |
| +--- usb3-reset
| |
| +--- usb3-regluator
| |
| +--- usb3-phy
|
+---USB3 core
The system reset, as parent reset controller, is necessary to enable
the entire USB3 block including the glue layer.
> > + reg = <0x0 0x4>;
> > + #reset-cells = <1>;
> > + clock-names = "link";
> > + clocks = <&sys_clk 14>;
> > + clock-names = "link";
> > + resets = <&sys_rst 14>;
> > + };
> > +
> > + other nodes ...
>
> What other nodes?
As mentioned above, the glue layer consists of reset, regulator, and phy.
I assume that the "other nodes" mean that these nodes are placed.
Thank you,
---
Best Regards,
Kunihiko Hayashi
next prev parent reply other threads:[~2018-07-04 1:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-29 8:11 [PATCH 0/2] reset: uniphier: add USB3 controller reset support Kunihiko Hayashi
2018-06-29 8:11 ` [PATCH 1/2] dt-bindings: " Kunihiko Hayashi
2018-06-29 9:57 ` Philipp Zabel
2018-07-03 23:37 ` Rob Herring
2018-07-04 1:09 ` Kunihiko Hayashi [this message]
2018-06-29 8:11 ` [PATCH 2/2] reset: uniphier: add USB3 controller reset control Kunihiko Hayashi
2018-06-29 9:51 ` kbuild test robot
2018-06-29 9:55 ` Philipp Zabel
2018-06-29 10:53 ` Kunihiko Hayashi
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=20180704100938.8235.4A936039@socionext.com \
--to=hayashi.kunihiko@socionext.com \
--cc=devicetree@vger.kernel.org \
--cc=jaswinder.singh@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=masami.hiramatsu@linaro.org \
--cc=p.zabel@pengutronix.de \
--cc=robh@kernel.org \
--cc=yamada.masahiro@socionext.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