From: robh@kernel.org (Rob Herring)
To: linus-amlogic@lists.infradead.org
Subject: [PATCH v7 usb-next 4/4] dt-bindings: usb: xhci: include the roothub and a device in the example
Date: Thu, 26 Oct 2017 22:29:57 -0500 [thread overview]
Message-ID: <20171027032957.m55ntlce646hpd5a@rob-hp-laptop> (raw)
In-Reply-To: <20171023215718.3446-5-martin.blumenstingl@googlemail.com>
On Mon, Oct 23, 2017 at 11:57:18PM +0200, Martin Blumenstingl wrote:
> This extends the existing example from the USB xHCI binding
> documentation so it includes the roothub and an actual device.
> The goal of this is to show that the roothub is specified alongside the
> actual devices on the USB bus (which is important because a device on
> the USB bus - for example a hub - might need it's own phys / phy-names
> properties. modelling the roothub as separate device and not nesting the
> other devices on the bus below the roothub allows us to keep the
> properties, for example the PHYs, separated).
>
> Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
> ---
> Documentation/devicetree/bindings/usb/usb-xhci.txt | 23 ++++++++++++++++++++++
> 1 file changed, 23 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/usb/usb-xhci.txt b/Documentation/devicetree/bindings/usb/usb-xhci.txt
> index 5b49ba9f2f9a..20e5ce2b016a 100644
> --- a/Documentation/devicetree/bindings/usb/usb-xhci.txt
> +++ b/Documentation/devicetree/bindings/usb/usb-xhci.txt
> @@ -42,4 +42,27 @@ Example:
> compatible = "generic-xhci";
> reg = <0xf0931000 0x8c8>;
> interrupts = <0x0 0x4e 0x0>;
> +
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + /* see usb-roothub.txt */
> + roothub at 0 {
> + compatible = "usb1d6b,3", "usb1d6b,2";
> + #address-cells = <1>;
> + #size-cells = <0>;
> + reg = <0>;
> +
> + port at 1 {
> + reg = <1>;
> + phys = <&usb2_phy1>, <&usb3_phy1>;
> + phy-names = "usb2-phy", "usb3-phy";
> + };
> + };
> +
> + /* see usb-device.txt */
> + hub: genesys at 1 {
What do the 0 and 1 addresses correspond to?
> + compatible = "usb5e3,608";
> + reg = <1>;
> + };
> };
> --
> 2.14.2
>
next prev parent reply other threads:[~2017-10-27 3:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-23 21:57 [PATCH v7 usb-next 0/4] initialize (multiple) PHYs on the roothub Martin Blumenstingl
2017-10-23 21:57 ` [PATCH v7 usb-next 1/4] dt-bindings: usb: add the documentation for USB root-hub Martin Blumenstingl
2017-10-23 21:57 ` [PATCH v7 usb-next 2/4] usb: core: add a wrapper for the USB PHYs on the root-hub Martin Blumenstingl
2017-10-24 0:06 ` Chunfeng Yun
2017-10-23 21:57 ` [PATCH v7 usb-next 3/4] usb: core: hcd: integrate the PHY roothub wrapper Martin Blumenstingl
2017-10-24 0:07 ` Chunfeng Yun
2017-10-26 5:42 ` Manu Gautam
2017-10-30 23:10 ` Martin Blumenstingl
2017-10-31 11:30 ` Chunfeng Yun
2017-10-23 21:57 ` [PATCH v7 usb-next 4/4] dt-bindings: usb: xhci: include the roothub and a device in the example Martin Blumenstingl
2017-10-27 3:29 ` Rob Herring [this message]
2017-10-27 19:20 ` Martin Blumenstingl
2017-10-27 19:55 ` Alan Stern
2017-10-28 13:33 ` Martin Blumenstingl
2017-10-30 14:08 ` Arnd Bergmann
2017-10-30 22:59 ` Martin Blumenstingl
2017-11-12 20:48 ` Martin Blumenstingl
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=20171027032957.m55ntlce646hpd5a@rob-hp-laptop \
--to=robh@kernel.org \
--cc=linus-amlogic@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
all inboxes | Powered by JetHome®