From: Grant Likely <grant.likely@secretlab.ca>
To: Jamie Iles <jamie@jamieiles.com>
Cc: linux-serial@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCHv2 1/2] dt: document the of_serial bindings
Date: Thu, 23 Jun 2011 08:55:21 -0600 [thread overview]
Message-ID: <BANLkTim_=xToTYjATh8Z_ji3muMy3dXj0Q@mail.gmail.com> (raw)
In-Reply-To: <1308838115-23034-1-git-send-email-jamie@jamieiles.com>
On Thu, Jun 23, 2011 at 8:08 AM, Jamie Iles <jamie@jamieiles.com> wrote:
> The of_serial bindings can be used to register a number of serial
> devices. Document this binding with all of the others.
>
> Cc: Grant Likely <grant.likely@secretlab.ca>
> Cc: Arnd Bergmann <arnd@arndb.de>
> Signed-off-by: Jamie Iles <jamie@jamieiles.com>
> ---
> .../devicetree/bindings/tty/serial/of-serial.txt | 34 ++++++++++++++++++++
> 1 files changed, 34 insertions(+), 0 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/tty/serial/of-serial.txt
>
> diff --git a/Documentation/devicetree/bindings/tty/serial/of-serial.txt b/Documentation/devicetree/bindings/tty/serial/of-serial.txt
> new file mode 100644
> index 0000000..b0c52c2
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/tty/serial/of-serial.txt
> @@ -0,0 +1,34 @@
> +* UART (Universal Asynchronous Receiver/Transmitter)
> +
> +Required properties:
> +- compatible : one of:
> + - "ns8250"
> + - "ns16450"
> + - "ns16550a"
> + - "ns16550"
> + - "ns16750"
> + - "ns16850"
> + - "nvidia,tegra250-uart"
> + - "ibm,qpace-nwp-serial"
> + - "serial" if the port type is unknown.
> +- reg : offset and length of the register set for the device.
> +- interrupts : should contain uart interrupt.
> +- clock-frequency : the input clock frequency for the UART.
> +
> +Optional properties:
> +- current-speed : the current active speed of the UART.
> +- reg-offset : offset to apply to the mapbase from the start of the registers.
> +- reg-shift : quantity to shift the register offsets by.
> +- used-by-rtas : set to indicate that the port is in use by the firmware and
> + should not be registered.
> +
> +Example:
> +
> + uart@80230000 {
> + compatible = "ns8250";
> + device-type = "serial";
Drop device-type. Otherwise looks good.
g.
> + reg = <0x80230000 0x100>;
> + clock-frequency = <3686400>;
> + interrupts = <10>;
> + reg-shift = <2>;
> + };
> --
> 1.7.4.1
>
>
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
--
To unsubscribe from this list: send the line "unsubscribe linux-serial" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-06-23 14:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-23 14:08 [PATCHv2 1/2] dt: document the of_serial bindings Jamie Iles
2011-06-23 14:08 ` [PATCHv2 2/2] tty: of_serial: support for 32 bit accesses Jamie Iles
2011-06-23 14:55 ` Grant Likely [this message]
2011-06-23 14:56 ` [PATCHv2 1/2] dt: document the of_serial bindings Grant Likely
2011-06-23 14:57 ` Grant Likely
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='BANLkTim_=xToTYjATh8Z_ji3muMy3dXj0Q@mail.gmail.com' \
--to=grant.likely@secretlab.ca \
--cc=arnd@arndb.de \
--cc=jamie@jamieiles.com \
--cc=linux-serial@vger.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;
as well as URLs for NNTP newsgroup(s).