From: Judith Mendez <jm@ti.com>
To: Judith Mendez <jm@ti.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Kevin Hilman <khilman@baylibre.com>
Cc: Jiri Slaby <jirislaby@kernel.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
<linux-kernel@vger.kernel.org>, <linux-serial@vger.kernel.org>,
Hari Nagalla <hnagalla@ti.com>
Subject: [PATCH RFC 1/2] dt-bindings: serial: add binding documentation for TI PRUSS UART
Date: Wed, 30 Apr 2025 19:31:12 -0500 [thread overview]
Message-ID: <20250501003113.1609342-2-jm@ti.com> (raw)
In-Reply-To: <20250501003113.1609342-1-jm@ti.com>
From: Bin Liu <b-liu@ti.com>
This adds the YAML DT binding for PRUSS UART on TI SoCs.
Signed-off-by: Bin Liu <b-liu@ti.com>
Signed-off-by: Judith Mendez <jm@ti.com>
---
.../bindings/serial/ti,pruss-uart.yaml | 54 +++++++++++++++++++
1 file changed, 54 insertions(+)
create mode 100644 Documentation/devicetree/bindings/serial/ti,pruss-uart.yaml
diff --git a/Documentation/devicetree/bindings/serial/ti,pruss-uart.yaml b/Documentation/devicetree/bindings/serial/ti,pruss-uart.yaml
new file mode 100644
index 000000000000..f7f660688f7e
--- /dev/null
+++ b/Documentation/devicetree/bindings/serial/ti,pruss-uart.yaml
@@ -0,0 +1,54 @@
+# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/serial/ti,pruss-uart.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: TI PRUSS serial UART
+
+maintainers:
+ - Bin Liu <b-liu@ti.com>
+
+description: |
+ The PRU-ICSS module has a serial UART peripheral, which is based on
+ industry standard TL16C550, with 16-bytes TX/RX FIFOs.
+
+allOf:
+ - $ref: /schemas/serial.yaml#
+
+properties:
+ compatible:
+ items:
+ - const: ti,pruss-uart
+
+ reg:
+ maxItems: 1
+
+ clocks:
+ maxItems: 1
+
+ interrupts:
+ maxItems: 1
+ description: |
+ PRU UART interrupt mappings, containing an entry of 3 cell-values.
+ The first is the PRU System Event ID for PRU UART Interrupt Request.
+ The second is the PRU interrupt channel ID.
+ The third is the PRU host interrupt ID.
+
+required:
+ - compatible
+ - reg
+ - clocks
+ - interrupts
+
+additionalProperties: true
+
+examples:
+ - |
+ pruss_uart: serial@28000 {
+ compatible = "ti,pruss-uart";
+ reg = <0x28000 0x40>;
+ clocks = <&k3_clks 81 13>;
+ interrupt-parent = <&pruss_intc>;
+ interrupts = <6 4 4>;
+ };
--
2.49.0
next prev parent reply other threads:[~2025-05-01 0:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-01 0:31 [PATCH RFC 0/2] Introduce PRU UART driver Judith Mendez
2025-05-01 0:31 ` Judith Mendez [this message]
2025-05-01 0:31 ` [PATCH RFC 2/2] serial: 8250: Add PRUSS " Judith Mendez
2025-05-01 16:28 ` Andrew Davis
2025-05-08 22:11 ` Judith Mendez
2025-05-02 9:50 ` Andy Shevchenko
2025-05-08 22:09 ` Judith Mendez
2025-05-09 11:43 ` Andy Shevchenko
2025-05-13 0:06 ` Judith Mendez
2025-05-01 5:18 ` [PATCH RFC 0/2] Introduce PRU " Greg Kroah-Hartman
2025-05-01 14:47 ` Judith Mendez
2025-05-02 9:51 ` Andy Shevchenko
2025-05-02 22:07 ` Judith Mendez
2025-05-02 9:38 ` Andy Shevchenko
2025-05-07 16:31 ` Judith Mendez
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=20250501003113.1609342-2-jm@ti.com \
--to=jm@ti.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=hnagalla@ti.com \
--cc=jirislaby@kernel.org \
--cc=khilman@baylibre.com \
--cc=linux-kernel@vger.kernel.org \
--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