linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: bhupesh.sharma@freescale.com (Bhupesh Sharma)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2 1/6] Documentation: DT: Add bindings for FSL NS16550A UART
Date: Thu, 28 Aug 2014 15:25:01 +0530	[thread overview]
Message-ID: <1409219706-14843-2-git-send-email-bhupesh.sharma@freescale.com> (raw)
In-Reply-To: <1409219706-14843-1-git-send-email-bhupesh.sharma@freescale.com>

This patch addss the device-tree documentation for Freescale's
NS16550 UART (also called DUART).

There is a specific errata fix required in FSL NS16550 UART
which ensures that an random interrupt storm is not observed when
a break is provided as an input to the UART.

Signed-off-by: Bhupesh Sharma <bhupesh.sharma@freescale.com>
---
 .../devicetree/bindings/serial/of-serial.txt       |   12 ++++++++++++
 1 file changed, 12 insertions(+)

diff --git a/Documentation/devicetree/bindings/serial/of-serial.txt b/Documentation/devicetree/bindings/serial/of-serial.txt
index 7705477..1bdc569 100644
--- a/Documentation/devicetree/bindings/serial/of-serial.txt
+++ b/Documentation/devicetree/bindings/serial/of-serial.txt
@@ -14,6 +14,7 @@ Required properties:
 	- "altr,16550-FIFO32"
 	- "altr,16550-FIFO64"
 	- "altr,16550-FIFO128"
+	- "fsl,ns16550"
 	- "serial" if the port type is unknown.
 - reg : offset and length of the register set for the device.
 - interrupts : should contain uart interrupt.
@@ -39,6 +40,17 @@ Optional properties:
   property.
 - has-hw-flow-control: the hardware has flow control capability.
 
+Note:
+* fsl,ns16550:
+  ------------
+  Freescale DUART is very similar to the PC16552D (and to a
+  pair of NS16550A), albeit with some nonstandard behavior such as
+  erratum A-004737 (relating to incorrect BRK handling).
+
+  Represents a single port that is compatible with the DUART found
+  on many Freescale chips (examples include mpc8349, mpc8548,
+  mpc8641d, p4080 and ls2085a).
+
 Example:
 
 	uart at 80230000 {
-- 
1.7.9.5

  reply	other threads:[~2014-08-28  9:55 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-28  9:55 [PATCH V2 0/6] ARM64: Add support for FSL's LS2085A SoC Bhupesh Sharma
2014-08-28  9:55 ` Bhupesh Sharma [this message]
2014-08-28  9:55 ` [PATCH V2 2/6] Documentation: DT: Add entry for FSL LS2085A SoC and Simulator model Bhupesh Sharma
2014-08-28  9:55 ` [PATCH V2 3/6] Documentation: DT: Add entry for FSL Management Complex Bhupesh Sharma
2014-08-28  9:55 ` [PATCH V2 4/6] arm64: Add DTS support for FSL's LS2085A SoC Bhupesh Sharma
2014-08-28 14:56   ` Mark Rutland
2014-08-29 15:51     ` bhupesh.sharma at freescale.com
2014-08-29 17:47       ` Mark Rutland
2014-08-29 18:07         ` bhupesh.sharma at freescale.com
2014-09-02 10:05           ` Catalin Marinas
2014-09-02 10:14             ` Catalin Marinas
2014-09-02 10:27               ` bhupesh.sharma at freescale.com
2014-09-02 10:19             ` Marc Zyngier
2014-09-03 17:23   ` Geoff Levand
2014-09-03 17:53     ` Mark Rutland
2014-09-03 18:17       ` Geoff Levand
2014-08-28  9:55 ` [PATCH V2 5/6] arm64: dts/Makefile: Add support for FSL's LS2085A simulator model Bhupesh Sharma
2014-08-28  9:55 ` [PATCH V2 6/6] arm64: Add support for FSL's LS2085A SoC in Kconfig and defconfig Bhupesh Sharma

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=1409219706-14843-2-git-send-email-bhupesh.sharma@freescale.com \
    --to=bhupesh.sharma@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).