From: mark.rutland@arm.com (Mark Rutland)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V4 1/6] Documentation: DT: Add bindings for FSL NS16550A UART
Date: Mon, 13 Oct 2014 13:40:31 +0100 [thread overview]
Message-ID: <20141013124031.GE15326@leverpostej> (raw)
In-Reply-To: <1412980849-21318-2-git-send-email-bhupesh.sharma@freescale.com>
On Fri, Oct 10, 2014 at 11:40:44PM +0100, Bhupesh Sharma wrote:
> 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"
This will need rebasing due to the addition of "fsl,16550-FIFO64". It's
a shame that the two strings follow different conventions, but it's too
late to change either now.
> - "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).
Ideally this would be described with the string entry in the list above,
rather than as a separate note.
Given the lack of notes for other instances, I'm happy to leave htis
here for now. So:
Acked-by: Mark Rutland <mark.rutland@arm.com>
Mark.
> +
> Example:
>
> uart at 80230000 {
> --
> 1.7.9.5
>
>
next prev parent reply other threads:[~2014-10-13 12:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-10 22:40 [PATCH V4 0/6] ARM64: Add support for FSL's LS2085A SoC Bhupesh Sharma
2014-10-10 22:40 ` [PATCH V4 1/6] Documentation: DT: Add bindings for FSL NS16550A UART Bhupesh Sharma
2014-10-13 12:40 ` Mark Rutland [this message]
2014-10-10 22:40 ` [PATCH V4 2/6] Documentation: DT: Add entry for FSL LS2085A SoC and Simulator model Bhupesh Sharma
2014-10-10 22:40 ` [PATCH V4 3/6] Documentation: DT: Add entry for FSL Management Complex Bhupesh Sharma
2014-10-10 22:40 ` [PATCH V4 4/6] arm64: Add DTS support for FSL's LS2085A SoC Bhupesh Sharma
2014-10-13 12:46 ` Mark Rutland
2014-10-10 22:40 ` [PATCH V4 5/6] arm64: dts/Makefile: Add support for FSL's LS2085A simulator model Bhupesh Sharma
2014-10-10 22:40 ` [PATCH V4 6/6] arm64: Add support for FSL's LS2085A SoC in Kconfig and defconfig Bhupesh Sharma
2014-10-28 17:50 ` [PATCH V4 0/6] ARM64: Add support for FSL's LS2085A SoC bhupesh.sharma at freescale.com
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=20141013124031.GE15326@leverpostej \
--to=mark.rutland@arm.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