devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Florian Fainelli <f.fainelli@gmail.com>
To: linux-serial@vger.kernel.org
Cc: devicetree@vger.kernel.org, mbizon@freebox.fr, jogo@openwrt.org,
	gregkh@linuxfoundation.org,
	Florian Fainelli <f.fainelli@gmail.com>
Subject: [PATCH 4/4] Documentation: devicetree: add bindings documentation for bcm63xx-uart
Date: Wed, 19 Feb 2014 15:22:47 -0800	[thread overview]
Message-ID: <1392852167-26243-5-git-send-email-f.fainelli@gmail.com> (raw)
In-Reply-To: <1392852167-26243-1-git-send-email-f.fainelli@gmail.com>

Add the Device Tree binding documentation for the non-standard BCM63xx
UART hardware block found in the BCM63xx DSL SoCs.

Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
---
 .../devicetree/bindings/serial/bcm63xx-uart.txt    | 24 ++++++++++++++++++++++
 1 file changed, 24 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/serial/bcm63xx-uart.txt

diff --git a/Documentation/devicetree/bindings/serial/bcm63xx-uart.txt b/Documentation/devicetree/bindings/serial/bcm63xx-uart.txt
new file mode 100644
index 0000000..829441d
--- /dev/null
+++ b/Documentation/devicetree/bindings/serial/bcm63xx-uart.txt
@@ -0,0 +1,24 @@
+Broadcom BCM63xx UART: Non standard UART used in the Broadcom BCM63xx DSL SoCs
+
+Required properties:
+- compatible: must be "brcm,bcm63xx-uart"
+- reg: offset and length of the register set for the device
+- interrupts: device interrupt
+- clocks: a phandle to the functional clock node
+- clock-names: must be "periph"
+
+Note: each UART port must have an alias correctly numbered in the "aliases"
+node, e.g:
+
+serial0: uart@600 {
+	compatible = "brcm,bcm63xx-uart";
+	reg = <0x600 0x1b>;
+	interrupts = <GIC_SPI 32 0>;
+	clocks = <&periph_clk>;
+	clock-names = "periph";
+};
+
+aliases {
+	uart0 = &serial0;
+	uart1 = &serial1;
+};
-- 
1.8.3.2


  parent reply	other threads:[~2014-02-19 23:22 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-19 23:22 [PATCH 0/4] Device Tree probing for bcm63xx-uart Florian Fainelli
2014-02-19 23:22 ` [PATCH 1/4] tty: serial: bcm63xx_uart: include linux/io.h Florian Fainelli
2014-02-19 23:22 ` [PATCH 2/4] tty: serial: bcm63xx_uart: define UART_REG_SIZE constant Florian Fainelli
2014-02-19 23:22 ` [PATCH 3/4] tty: serial: bcm63xx_uart: add support for DT probing Florian Fainelli
2014-02-20  0:00   ` Jonas Gorski
2014-02-20  1:29     ` Florian Fainelli
2014-02-20 10:59       ` Jonas Gorski
2014-02-20 12:16         ` Arnd Bergmann
2014-02-20 16:18           ` Florian Fainelli
2014-02-20 12:21         ` Mark Rutland
2014-02-19 23:22 ` Florian Fainelli [this message]
2014-02-20  9:45   ` [PATCH 4/4] Documentation: devicetree: add bindings documentation for bcm63xx-uart Mark Rutland

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=1392852167-26243-5-git-send-email-f.fainelli@gmail.com \
    --to=f.fainelli@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jogo@openwrt.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=mbizon@freebox.fr \
    /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).