linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: peter.chen@freescale.com (Peter Chen)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 2/3] doc: dt-binding: generic onboard USB HUB
Date: Mon, 14 Dec 2015 15:26:13 +0800	[thread overview]
Message-ID: <1450077974-22762-3-git-send-email-peter.chen@freescale.com> (raw)
In-Reply-To: <1450077974-22762-1-git-send-email-peter.chen@freescale.com>

Add dt-binding documentation for generic onboard USB HUB.

Signed-off-by: Peter Chen <peter.chen@freescale.com>
---
 .../devicetree/bindings/usb/generic-onboard-hub.txt  | 20 ++++++++++++++++++++
 1 file changed, 20 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/usb/generic-onboard-hub.txt

diff --git a/Documentation/devicetree/bindings/usb/generic-onboard-hub.txt b/Documentation/devicetree/bindings/usb/generic-onboard-hub.txt
new file mode 100644
index 0000000..d19d912
--- /dev/null
+++ b/Documentation/devicetree/bindings/usb/generic-onboard-hub.txt
@@ -0,0 +1,20 @@
+Generic Onboard USB HUB
+
+Required properties:
+- compatible: should be "generic-onboard-hub"
+
+Optional properties:
+- clocks: the input clock for USB HUB.
+- clock-frequency: the frequency for HUB's clock.
+- reset-gpios: Should specify the GPIO for reset.
+- reset-duration-us: the duration for assert reset signal, the time unit
+  is microsecond.
+
+Example:
+
+	usb_hub1 {
+		compatible = "generic-onboard-hub";
+		clocks = <&clks IMX6QDL_CLK_CKO>;
+		reset-gpios = <&gpio7 12 GPIO_ACTIVE_LOW>;
+		hub-reset-duration-us = <2>;
+	};
-- 
1.9.1

  parent reply	other threads:[~2015-12-14  7:26 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-14  7:26 [PATCH v2 0/3] USB: add generic onboard USB HUB driver Peter Chen
2015-12-14  7:26 ` [PATCH v2 1/3] usb: misc: generic_onboard_hub: " Peter Chen
2015-12-14  7:26 ` Peter Chen [this message]
2015-12-14  7:26 ` [PATCH v2 3/3] ARM: dts: imx6qdl-udoo.dtsi: fix onboard USB HUB property Peter Chen
2015-12-14  9:35 ` [PATCH v2 0/3] USB: add generic onboard USB HUB driver Arnd Bergmann
2015-12-15  8:33   ` Peter Chen
2015-12-16 22:59   ` Rob Herring
2015-12-16 23:13     ` Arnd Bergmann
2015-12-17  2:31       ` Peter Chen
2015-12-17 13:49         ` Rob Herring
2015-12-18  7:38           ` Peter Chen
2015-12-17 16:13     ` Alan Stern
2015-12-18  7:42       ` Peter Chen
2015-12-18 15:38         ` Alan Stern
2015-12-21  8:33           ` Peter Chen
2015-12-21 19:40             ` Alan Stern
2015-12-22  3:32               ` Peter Chen
2015-12-22 15:48                 ` Alan Stern
2016-01-05 14:36             ` Rob Herring
2016-01-05 15:59               ` Alan Stern
2016-01-06  3:20               ` Peter Chen
2016-01-07 14:18                 ` Rob Herring
2016-01-08  3:33                   ` Peter Chen
2016-02-24  9:22                   ` Peter Chen
2015-12-14 11:26 ` Fabio Estevam
2015-12-15  6:28   ` Peter Chen
2015-12-15 11:32     ` Fabio Estevam
2015-12-16  4:11       ` Peter Chen
2015-12-16 10:11         ` Fabio Estevam
2015-12-16 20:05           ` Maciej S. Szmigiero
2015-12-17  6:57             ` Peter Chen
2015-12-18 23:48               ` Maciej S. Szmigiero
2015-12-21  8:44                 ` Peter Chen

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=1450077974-22762-3-git-send-email-peter.chen@freescale.com \
    --to=peter.chen@freescale.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).