From: Palmer Dabbelt <palmer@sifive.com>
To: Paul Walmsley <paul.walmsley@sifive.com>
Cc: mark.rutland@arm.com, devicetree@vger.kernel.org, paul@pwsan.com,
Greg KH <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org, robh+dt@kernel.org,
linux-serial@vger.kernel.org,
Paul Walmsley <paul.walmsley@sifive.com>,
linux-riscv@lists.infradead.org
Subject: Re: [PATCH 1/2] dt-bindings: serial: add documentation for the SiFive UART driver
Date: Fri, 19 Oct 2018 09:51:59 -0700 (PDT) [thread overview]
Message-ID: <mhng-607b838d-f2e0-4c14-8274-9d696cbc7e78@palmer-si-x1c4> (raw)
Message-ID: <20181019165159.1IMJf0BunlWW_NGCkLhK4niAvh8K4etYnUT48JbHnO8@z> (raw)
In-Reply-To: <20181018234352.26788-2-paul.walmsley@sifive.com>
On Thu, 18 Oct 2018 16:43:53 PDT (-0700), Paul Walmsley wrote:
> Add DT binding documentation for the Linux driver for the SiFive
> asynchronous serial IP block. Nothing too exotic.
>
> Cc: linux-serial@vger.kernel.org
> Cc: devicetree@vger.kernel.org
> Cc: linux-riscv@lists.infradead.org
> Cc: linux-kernel@vger.kernel.org
> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Cc: Rob Herring <robh+dt@kernel.org>
> Cc: Mark Rutland <mark.rutland@arm.com>
> Cc: Palmer Dabbelt <palmer@sifive.com>
> Signed-off-by: Paul Walmsley <paul.walmsley@sifive.com>
> Signed-off-by: Paul Walmsley <paul@pwsan.com>
> ---
> .../bindings/serial/sifive-serial.txt | 21 +++++++++++++++++++
> 1 file changed, 21 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/serial/sifive-serial.txt
>
> diff --git a/Documentation/devicetree/bindings/serial/sifive-serial.txt b/Documentation/devicetree/bindings/serial/sifive-serial.txt
> new file mode 100644
> index 000000000000..8982338512f5
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/serial/sifive-serial.txt
> @@ -0,0 +1,21 @@
> +SiFive asynchronous serial interface (UART)
> +
> +Required properties:
> +
> +- compatible: should be "sifive,fu540-c000-uart0" or "sifive,uart0"
> +- reg: address and length of the register space
> +- interrupt-parent: should contain a phandle pointing to the SoC interrupt
> + controller device node that the UART interrupts are connected to
> +- interrupts: Should contain the UART interrupt identifier
> +- clocks: Should contain a clock identifier for the UART's parent clock
> +
> +
> +Example:
> +
> +uart0: serial@10010000 {
> + compatible = "sifive,uart0";
> + interrupt-parent = <&plic0>;
> + interrupts = <80>;
> + reg = <0x0 0x10010000 0x0 0x1000>;
> + clocks = <&prci PRCI_CLK_TLCLK>;
> +};
Reviewed-by: Palmer Dabbelt <palmer@sifive.com>
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2018-10-19 16:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20181018234352.26788-1-paul.walmsley@sifive.com>
2018-10-18 23:43 ` [PATCH 1/2] dt-bindings: serial: add documentation for the SiFive UART driver Paul Walmsley
2018-10-18 23:43 ` Paul Walmsley
2018-10-19 16:51 ` Palmer Dabbelt [this message]
2018-10-19 16:51 ` Palmer Dabbelt
2018-10-18 23:43 ` [PATCH 2/2] tty: serial: add driver for the SiFive UART Paul Walmsley
2018-10-18 23:43 ` Paul Walmsley
2018-10-19 9:55 ` kbuild test robot
2018-10-19 9:55 ` kbuild test robot
2018-10-19 10:40 ` kbuild test robot
2018-10-19 10:40 ` kbuild test robot
2018-11-09 16:59 ` Greg Kroah-Hartman
2018-11-09 16:59 ` Greg Kroah-Hartman
2018-11-09 17:00 ` Greg Kroah-Hartman
2018-11-09 17:00 ` Greg Kroah-Hartman
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=mhng-607b838d-f2e0-4c14-8274-9d696cbc7e78@palmer-si-x1c4 \
--to=palmer@sifive.com \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-serial@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=paul.walmsley@sifive.com \
--cc=paul@pwsan.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).