devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robherring2@gmail.com>
To: Niklas Cassel <nks@flawful.org>
Cc: Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
	Mark Rutland <mark.rutland@arm.com>,
	Ian Campbell <ijc+devicetree@hellion.org.uk>,
	Kumar Gala <galak@codeaurora.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH RESEND 2/2] serial: add device tree binding documentation for ETRAX FS UART
Date: Fri, 13 Mar 2015 10:25:56 -0500	[thread overview]
Message-ID: <CAL_JsqLdCyiiX+Nc8t0ZSLMZcyGFoH9HGCj3FebVoz7rLNrm2A@mail.gmail.com> (raw)
In-Reply-To: <1424298578-6833-1-git-send-email-nks@flawful.org>

On Wed, Feb 18, 2015 at 4:29 PM, Niklas Cassel <nks@flawful.org> wrote:
> Signed-off-by: Niklas Cassel <nks@flawful.org>
> ---
> [PATCH 1/2] of this patch series has already reached its way into mainline.
> It would be nice if someone picked up [PATCH 2/2] (this commit) before the merge window closes.
>
>  .../devicetree/bindings/serial/axis,etraxfs-uart.txt  | 19 +++++++++++++++++++
>  Documentation/devicetree/bindings/vendor-prefixes.txt |  1 +
>  2 files changed, 20 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/serial/axis,etraxfs-uart.txt

Applied for 4.0. Thanks.

Rob

>
> diff --git a/Documentation/devicetree/bindings/serial/axis,etraxfs-uart.txt b/Documentation/devicetree/bindings/serial/axis,etraxfs-uart.txt
> new file mode 100644
> index 0000000..ebcbb62
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/serial/axis,etraxfs-uart.txt
> @@ -0,0 +1,19 @@
> +ETRAX FS UART
> +
> +Required properties:
> +- compatible : "axis,etraxfs-uart"
> +- reg: offset and length of the register set for the device.
> +- interrupts: device interrupt
> +
> +Optional properties:
> +- {dtr,dsr,ri,cd}-gpios: specify a GPIO for DTR/DSR/RI/CD
> +  line respectively.
> +
> +Example:
> +
> +serial@b00260000 {
> +       compatible = "axis,etraxfs-uart";
> +       reg = <0xb0026000 0x1000>;
> +       interrupts = <68>;
> +       status = "disabled";
> +};
> diff --git a/Documentation/devicetree/bindings/vendor-prefixes.txt b/Documentation/devicetree/bindings/vendor-prefixes.txt
> index d6bad12..f8d088e 100644
> --- a/Documentation/devicetree/bindings/vendor-prefixes.txt
> +++ b/Documentation/devicetree/bindings/vendor-prefixes.txt
> @@ -27,6 +27,7 @@ atmel Atmel Corporation
>  auo    AU Optronics Corporation
>  avago  Avago Technologies
>  avic   Shanghai AVIC Optoelectronics Co., Ltd.
> +axis   Axis Communications AB
>  bosch  Bosch Sensortec GmbH
>  brcm   Broadcom Corporation
>  buffalo        Buffalo, Inc.
> --
> 2.2.2
>

      reply	other threads:[~2015-03-13 15:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-18 22:29 [PATCH RESEND 2/2] serial: add device tree binding documentation for ETRAX FS UART Niklas Cassel
2015-03-13 15:25 ` Rob Herring [this message]

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=CAL_JsqLdCyiiX+Nc8t0ZSLMZcyGFoH9HGCj3FebVoz7rLNrm2A@mail.gmail.com \
    --to=robherring2@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=galak@codeaurora.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=nks@flawful.org \
    --cc=pawel.moll@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;
as well as URLs for NNTP newsgroup(s).