Linux Tegra architecture development
 help / color / mirror / Atom feed
From: Kartik Rajput <kkartik@nvidia.com>
To: <gregkh@linuxfoundation.org>, <jirislaby@kernel.org>,
	<robh@kernel.org>, <krzk+dt@kernel.org>, <conor+dt@kernel.org>,
	<thierry.reding@gmail.com>, <jonathanh@nvidia.com>,
	<hvilleneuve@dimonoff.com>, <arnd@kernel.org>,
	<geert+renesas@glider.be>, <robert.marko@sartura.hr>,
	<schnelle@linux.ibm.com>, <andriy.shevchenko@linux.intel.com>,
	<linux-kernel@vger.kernel.org>, <linux-serial@vger.kernel.org>,
	<devicetree@vger.kernel.org>, <linux-tegra@vger.kernel.org>
Subject: [PATCH 1/2] dt-bindings: serial: Add bindings for nvidia,tegra264-utc
Date: Tue, 28 Jan 2025 12:16:32 +0530	[thread overview]
Message-ID: <20250128064633.12381-2-kkartik@nvidia.com> (raw)
In-Reply-To: <20250128064633.12381-1-kkartik@nvidia.com>

The Tegra UTC (UART Trace Controller) is a HW based serial port that
allows multiplexing multiple data streams of up to 16 UTC clients into
a single hardware serial port.

Add bindings for the Tegra UTC client device.

Signed-off-by: Kartik Rajput <kkartik@nvidia.com>
---
 .../bindings/serial/nvidia,tegra264-utc.yaml  | 83 +++++++++++++++++++
 1 file changed, 83 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/serial/nvidia,tegra264-utc.yaml

diff --git a/Documentation/devicetree/bindings/serial/nvidia,tegra264-utc.yaml b/Documentation/devicetree/bindings/serial/nvidia,tegra264-utc.yaml
new file mode 100644
index 000000000000..63ba3655451f
--- /dev/null
+++ b/Documentation/devicetree/bindings/serial/nvidia,tegra264-utc.yaml
@@ -0,0 +1,83 @@
+# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/serial/nvidia,tegra264-utc.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: NVIDIA Tegra UART Trace Controller (UTC) client
+
+maintainers:
+  - Kartik Rajput <kkartik@nvidia.com>
+  - Thierry Reding <thierry.reding@gmail.com>
+  - Jonathan Hunter <jonathanh@nvidia.com>
+
+description:
+  The Tegra UTC (UART Trace Controller) is a hardware controller that
+  allows multiple systems within the Tegra SoC to share a hardware UART
+  interface. It supports up to 16 clients, with each client having its own
+  interrupt and a FIFO buffer for both RX (receive) and TX (transmit), each
+  capable of holding 128 characters.
+
+  The Tegra UTC uses 8-N-1 configuration and operates on a pre-configured
+  baudrate, which is configured by the bootloader.
+
+properties:
+  $nodename:
+    pattern: "^serial(@.*)?$"
+
+  compatible:
+    const: nvidia,tegra264-utc
+
+  reg:
+    items:
+      - description: Register region for TX client.
+      - description: Register region for RX client.
+    minItems: 2
+
+  reg-names:
+    items:
+      - const: tx
+      - const: rx
+    minItems: 2
+
+  interrupts:
+    maxItems: 1
+
+  current-speed:
+    $ref: /schemas/types.yaml#/definitions/uint32
+    description:
+      This property specifies the baudrate at which the Tegra UTC is
+      operating.
+
+  nvidia,utc-fifo-threshold:
+    $ref: /schemas/types.yaml#/definitions/uint32
+    description:
+      This property specifies the UTC TX and RX client FIFO threshold in
+      terms of occupancy.
+
+      This property should have the same value as the burst size (number
+      of characters read by the Tegra UTC hardware at a time from each
+      client) which is configured by the bootloader.
+
+required:
+  - compatible
+  - reg
+  - reg-names
+  - interrupts
+  - current-speed
+  - nvidia,utc-fifo-threshold
+
+additionalProperties: false
+
+examples:
+  - |
+    #include <dt-bindings/interrupt-controller/arm-gic.h>
+
+    tegra_utc: serial@c4e0000 {
+        compatible = "nvidia,tegra264-utc";
+        reg = <0xc4e0000 0x8000>, <0xc4e8000 0x8000>;
+        reg-names = "tx", "rx";
+        interrupts = <GIC_SPI 514 IRQ_TYPE_LEVEL_HIGH>;
+        current-speed = <115200>;
+        nvidia,utc-fifo-threshold = <4>;
+    };
-- 
2.43.0


  reply	other threads:[~2025-01-28  6:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-28  6:46 [PATCH 0/2] Add support for Tegra UART Trace Controller (UTC) client Kartik Rajput
2025-01-28  6:46 ` Kartik Rajput [this message]
2025-01-28  7:52   ` [PATCH 1/2] dt-bindings: serial: Add bindings for nvidia,tegra264-utc Krzysztof Kozlowski
2025-01-29  7:30     ` Kartik Rajput
2025-01-29 14:52       ` Thierry Reding
2025-01-28  6:46 ` [PATCH 2/2] serial: tegra-utc: Add driver for Tegra UART Trace Controller (UTC) Kartik Rajput
2025-01-29  7:07   ` Andy Shevchenko
2025-01-29  8:04     ` Kartik Rajput
2025-01-29 10:11       ` andriy.shevchenko

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=20250128064633.12381-2-kkartik@nvidia.com \
    --to=kkartik@nvidia.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=arnd@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=geert+renesas@glider.be \
    --cc=gregkh@linuxfoundation.org \
    --cc=hvilleneuve@dimonoff.com \
    --cc=jirislaby@kernel.org \
    --cc=jonathanh@nvidia.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=robert.marko@sartura.hr \
    --cc=robh@kernel.org \
    --cc=schnelle@linux.ibm.com \
    --cc=thierry.reding@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