From: Raviteja Garimella <raviteja.garimella@broadcom.com>
To: Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Felipe Balbi <balbi@kernel.org>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
bcm-kernel-feedback-list@broadcom.com, linux-usb@vger.kernel.org
Subject: [PATCH v3 6/7] DT bindings documentation for Broadcom IPROC USB Device controller.
Date: Tue, 28 Mar 2017 16:32:08 +0530 [thread overview]
Message-ID: <1490698929-10915-7-git-send-email-raviteja.garimella@broadcom.com> (raw)
In-Reply-To: <1490698929-10915-1-git-send-email-raviteja.garimella@broadcom.com>
The device node is used for UDCs integrated into Broadcom's
iProc family of SoCs'. The UDC is based on Synopsys Designware
Cores AHB Subsystem USB Device Controller IP.
Signed-off-by: Raviteja Garimella <raviteja.garimella@broadcom.com>
---
Documentation/devicetree/bindings/usb/iproc-udc.txt | 21 +++++++++++++++++++++
1 file changed, 21 insertions(+)
create mode 100644 Documentation/devicetree/bindings/usb/iproc-udc.txt
diff --git a/Documentation/devicetree/bindings/usb/iproc-udc.txt b/Documentation/devicetree/bindings/usb/iproc-udc.txt
new file mode 100644
index 0000000..272d7fa
--- /dev/null
+++ b/Documentation/devicetree/bindings/usb/iproc-udc.txt
@@ -0,0 +1,21 @@
+Broadcom IPROC USB Device controller.
+
+The device node is used for UDCs integrated into Broadcom's
+iProc family (Northstar2, Cygnus) of SoCs'. The UDC is based
+on Synopsys Designware Cores AHB Subsystem Device Controller
+IP.
+
+Required properties:
+ - compatible: Add the compatibility strings for supported platforms.
+ For Broadcom NS2 platform, add "brcm,ns2-udc","brcm,iproc-udc".
+ For Broadcom Cygnus platform, add "brcm,cygnus-udc", "brcm,iproc-udc".
+ - reg: Offset and length of UDC register set
+ - interrupts: description of interrupt line
+ - phys: phandle to phy node.
+
+Example:
+ udc_dwc: usb@664e0000 {
+ compatible = "brcm,ns2-udc", "brcm,iproc-udc";
+ reg = <0x664e0000 0x2000>;
+ interrupts = <GIC_SPI 424 IRQ_TYPE_LEVEL_HIGH>;
+ phys = <&usbdrd_phy>;
--
2.1.0
next prev parent reply other threads:[~2017-03-28 11:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-28 11:02 [PATCH v3 0/7] Platform driver support for 'amd5536udc' driver Raviteja Garimella
2017-03-28 11:02 ` [PATCH v3 1/7] UDC: Split the driver into amd (pci) and Synopsys core IP driver Raviteja Garimella
2017-03-28 11:02 ` [PATCH v3 2/7] UDC: Rename amd5536udc driver file based on IP Raviteja Garimella
2017-03-31 9:49 ` Felipe Balbi
2017-03-31 13:16 ` Raviteja Garimella
2017-03-28 11:02 ` [PATCH v3 3/7] UDC: make debug prints compatible with both pci and platform devices Raviteja Garimella
2017-03-28 11:02 ` [PATCH v3 4/7] UDC: Provide correct arguments for 'dma_pool_create' Raviteja Garimella
2017-03-28 11:02 ` [PATCH v3 5/7] UDC: Use struct dma_pool instead of pci_pool Raviteja Garimella
2017-03-28 11:02 ` Raviteja Garimella [this message]
2017-03-28 11:02 ` [PATCH v3 7/7] UDC: Add Synopsys UDC Platform driver Raviteja Garimella
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=1490698929-10915-7-git-send-email-raviteja.garimella@broadcom.com \
--to=raviteja.garimella@broadcom.com \
--cc=balbi@kernel.org \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.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®