Devicetree
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Jon Mason <jon.mason@broadcom.com>
Cc: Kishon Vijay Abraham I <kishon@ti.com>,
	Florian Fainelli <f.fainelli@gmail.com>,
	Mark Rutland <mark.rutland@arm.com>,
	bcm-kernel-feedback-list@broadcom.com,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 4/6] dt-bindings: usb: Add documentation for NS2 IDM USB3
Date: Thu, 3 Aug 2017 14:08:38 -0500	[thread overview]
Message-ID: <20170803190838.q4o7ijukgoliik5n@rob-hp-laptop> (raw)
In-Reply-To: <1501109787-15489-5-git-send-email-jon.mason@broadcom.com>

On Wed, Jul 26, 2017 at 06:56:25PM -0400, Jon Mason wrote:
> Add documentation for IDM USB3 registers available in NS2 SoC
> 
> Signed-off-by: Jon Mason <jon.mason@broadcom.com>
> ---
>  Documentation/devicetree/bindings/usb/brcm,usb3-idm.txt | 14 ++++++++++++++
>  1 file changed, 14 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/usb/brcm,usb3-idm.txt
> 
> diff --git a/Documentation/devicetree/bindings/usb/brcm,usb3-idm.txt b/Documentation/devicetree/bindings/usb/brcm,usb3-idm.txt
> new file mode 100644
> index 000000000000..3618dbcbe890
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/usb/brcm,usb3-idm.txt
> @@ -0,0 +1,14 @@
> +Broadcom IDM USB3 registers
> +
> +Required properties:
> +- compatible: "brcm,usb3-idm"
> +- reg: Base address and length of the USB registers
> +
> +
> +Example:
> +
> +usb3_idm: idm@67000000 {

I'm assuming these are all some misc registers in addition to the USB 
controller? If this is the USB controller itself, then use generic node 
names for the DT spec.

Acked-by: Rob Herring <robh@kernel.org>

> +        compatible = "brcm,usb3-idm";
> +        reg = <0x67000000 0x2000>;
> +};
> +
> -- 
> 2.7.4
> 

  reply	other threads:[~2017-08-03 19:08 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-26 22:56 [PATCH v2 0/6] USB3 support for Broadcom NS2 SoC Jon Mason
2017-07-26 22:56 ` [PATCH v2 1/6] dt-bindings: phy: Add documentation for NS2 USB3 PHY Jon Mason
     [not found]   ` <1501109787-15489-2-git-send-email-jon.mason-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>
2017-08-03 19:03     ` Rob Herring
2017-07-26 22:56 ` [PATCH v2 2/6] dt-bindings: usb: Add documentation for NS2 CDRU USB3 Jon Mason
     [not found]   ` <1501109787-15489-3-git-send-email-jon.mason-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>
2017-08-03 19:05     ` Rob Herring
2017-07-26 22:56 ` [PATCH v2 3/6] dt-bindings: usb: Add documentation for NS2 ICFG USB3 Jon Mason
2017-08-03 19:06   ` Rob Herring
2017-07-26 22:56 ` [PATCH v2 4/6] dt-bindings: usb: Add documentation for NS2 IDM USB3 Jon Mason
2017-08-03 19:08   ` Rob Herring [this message]
2017-07-26 22:56 ` [PATCH v2 5/6] phy: Add USB3 PHY support for Broadcom NS2 SoC Jon Mason
2017-08-02  6:36   ` Kishon Vijay Abraham I
     [not found]     ` <9f25daa0-13b3-2a56-34bb-f3705672fae5-l0cyMroinI0@public.gmane.org>
2017-08-03 15:23       ` Jon Mason
2017-07-26 22:56 ` [PATCH v2 6/6] arm64: dts: ns2: Add USB3 Support Jon Mason

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=20170803190838.q4o7ijukgoliik5n@rob-hp-laptop \
    --to=robh@kernel.org \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=devicetree@vger.kernel.org \
    --cc=f.fainelli@gmail.com \
    --cc=jon.mason@broadcom.com \
    --cc=kishon@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.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