From: festevam@gmail.com (Fabio Estevam)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/3] doc: dt-binding: generic onboard USB HUB
Date: Tue, 8 Dec 2015 00:30:59 -0200 [thread overview]
Message-ID: <CAOMZO5DfBW3hxp5odbefLQCmkocPy=LypVW5HJWzDkF__WD_sg@mail.gmail.com> (raw)
In-Reply-To: <1449538670-7954-3-git-send-email-peter.chen@freescale.com>
On Mon, Dec 7, 2015 at 11:37 PM, Peter Chen <peter.chen@freescale.com> wrote:
> Add dt-binding documentation for generic onboard USB HUB.
>
> Signed-off-by: Peter Chen <peter.chen@freescale.com>
> ---
> .../bindings/usb/generic-onboard-hub.txt | 28 ++++++++++++++++++++++
> 1 file changed, 28 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..ea92205
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/usb/generic-onboard-hub.txt
> @@ -0,0 +1,28 @@
> +Generic Onboard USB HUB
> +
> +Required properties:
> +- compatible: should be "generic-onboard-hub"
> +
> +Optional properties:
> +- clocks: the input clock for HUB.
> +
> +- clock-names: Should be "external_clk"
> +
> +- hub-reset-gpios: Should specify the GPIO for reset.
> +
> +- hub-reset-active-high: the active reset signal is high, if this property is
> + not set, the active reset signal is low.
> +
> +- hub-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>;
> + clock-names = "external_clk";
> + hub-reset-gpios = <&gpio7 12 0>;
> + hub-reset-active-high;
I think you could drop the 'hub-reset-active-high' property and do
like this instead:
hub-reset-gpios = <&gpio7 12 GPIO_ACTIVE_HIGH>;
or
hub-reset-gpios = <&gpio7 12 GPIO_ACTIVE_LOW>;
next prev parent reply other threads:[~2015-12-08 2:30 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-08 1:37 [PATCH 0/3] USB: add generic onboard USB HUB driver Peter Chen
2015-12-08 1:37 ` [PATCH 1/3] usb: misc: generic_onboard_hub: " Peter Chen
2015-12-08 2:59 ` Felipe Balbi
2015-12-08 9:18 ` Peter Chen
2015-12-08 13:55 ` Felipe Balbi
2015-12-09 8:45 ` Peter Chen
2015-12-08 3:16 ` kbuild test robot
2015-12-08 9:36 ` Peter Chen
2015-12-08 6:19 ` Sascha Hauer
2015-12-08 9:26 ` Peter Chen
2015-12-08 9:44 ` Sascha Hauer
2015-12-09 8:23 ` Peter Chen
2015-12-08 9:48 ` Arnd Bergmann
2015-12-09 8:14 ` Peter Chen
2015-12-08 15:36 ` Mathieu Poirier
2015-12-09 8:50 ` Peter Chen
2015-12-09 8:57 ` Lucas Stach
2015-12-09 9:00 ` Peter Chen
2015-12-09 9:13 ` Lucas Stach
2015-12-09 9:29 ` Peter Chen
2015-12-09 9:10 ` Arnd Bergmann
2015-12-09 9:08 ` Peter Chen
2015-12-08 1:37 ` [PATCH 2/3] doc: dt-binding: generic onboard USB HUB Peter Chen
2015-12-08 2:30 ` Fabio Estevam [this message]
2015-12-08 9:20 ` Peter Chen
2015-12-08 9:45 ` Arnd Bergmann
2015-12-08 9:50 ` Philipp Zabel
2015-12-08 9:58 ` Arnd Bergmann
2015-12-09 3:24 ` Rob Herring
2015-12-09 8:12 ` Peter Chen
2015-12-09 8:55 ` Arnd Bergmann
2015-12-15 20:21 ` Ulf Hansson
2015-12-16 2:46 ` Peter Chen
2015-12-09 8:09 ` Peter Chen
2015-12-08 1:37 ` [PATCH 3/3] ARM: dts: imx6qdl-udoo.dtsi: fix onboard USB HUB property 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='CAOMZO5DfBW3hxp5odbefLQCmkocPy=LypVW5HJWzDkF__WD_sg@mail.gmail.com' \
--to=festevam@gmail.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).