From: Greg KH <gregkh@linuxfoundation.org>
To: Matthias Brugger <matthias.bgg@gmail.com>
Cc: linux-kernel@vger.kernel.org, robh+dt@kernel.org,
pawel.moll@arm.com, mark.rutland@arm.com,
ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
rdunlap@infradead.org, jslaby@suse.cz, grant.likely@linaro.org,
alan@linux.intel.com, varkabhadram@gmail.com,
tklauser@distanz.ch, heiko@sntech.de, yingjoe.chen@gmail.com,
devicetree@vger.kernel.org, linux-doc@vger.kernel.org,
linux-serial@vger.kernel.org
Subject: Re: [PATCH v4 2/2] DTS: serial: Add bindings documention for the Mediatek UARTs
Date: Mon, 8 Sep 2014 15:33:14 -0700 [thread overview]
Message-ID: <20140908223314.GA26151@kroah.com> (raw)
In-Reply-To: <1407852737-17265-3-git-send-email-matthias.bgg@gmail.com>
On Tue, Aug 12, 2014 at 04:12:17PM +0200, Matthias Brugger wrote:
> This patch adds the devicetree documentation for the Mediatek UART.
>
> Signed-off-by: Matthias Brugger <matthias.bgg@gmail.com>
> ---
> .../devicetree/bindings/serial/mtk-uart.txt | 20 ++++++++++++++++++++
> 1 file changed, 20 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/serial/mtk-uart.txt
>
> diff --git a/Documentation/devicetree/bindings/serial/mtk-uart.txt b/Documentation/devicetree/bindings/serial/mtk-uart.txt
> new file mode 100644
> index 0000000..6ca0e15
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/serial/mtk-uart.txt
> @@ -0,0 +1,20 @@
> +* Mediatek Universal Asynchronous Receiver/Transmitter (UART)
> +
> +Required properties:
> +- compatible: "mediatek,mt6577-uart"
> + Compatibility with mt6577, mt6589, mt6582
> +
> +- reg: The base address of the UART register bank.
> +
> +- interrupts: A single interrupt specifier.
> +
> +- clocks: Clock driving the hardware.
> +
> +Example:
> +
> + uart0: serial@11006000 {
> + compatible = "mediatek,mt6577-uart";
> + reg = <0x11006000 0x400>;
> + interrupts = <GIC_SPI 51 IRQ_TYPE_LEVEL_LOW>;
> + clocks = <&uart_clk>;
> + };
> --
> 1.7.9.5
Resend this one as well with the 1/2 patch please.
thanks,
greg k-h
next prev parent reply other threads:[~2014-09-08 22:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-12 14:12 [PATCH v4 0/2] tty: serial: Add mediatek UART driver Matthias Brugger
2014-08-12 14:12 ` [PATCH v4 1/2] tty: serial: 8250: Add Mediatek " Matthias Brugger
2014-09-02 11:35 ` Mark Rutland
2014-09-08 22:32 ` Greg KH
2014-08-12 14:12 ` [PATCH v4 2/2] DTS: serial: Add bindings documention for the Mediatek UARTs Matthias Brugger
[not found] ` <1407852737-17265-3-git-send-email-matthias.bgg-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-09-02 11:31 ` Mark Rutland
2014-09-08 22:33 ` Greg KH [this message]
2014-09-09 14:55 ` Matthias Brugger
2014-09-02 10:00 ` [PATCH v4 0/2] tty: serial: Add mediatek UART driver Matthias Brugger
[not found] ` <1407852737-17265-1-git-send-email-matthias.bgg-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-09-02 10:08 ` Matthias Brugger
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=20140908223314.GA26151@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=alan@linux.intel.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=grant.likely@linaro.org \
--cc=heiko@sntech.de \
--cc=ijc+devicetree@hellion.org.uk \
--cc=jslaby@suse.cz \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=matthias.bgg@gmail.com \
--cc=pawel.moll@arm.com \
--cc=rdunlap@infradead.org \
--cc=robh+dt@kernel.org \
--cc=tklauser@distanz.ch \
--cc=varkabhadram@gmail.com \
--cc=yingjoe.chen@gmail.com \
/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).