From: Changhuang Liang <changhuang.liang@starfivetech.com>
To: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
Changhuang Liang <changhuang.liang@starfivetech.com>
Subject: [PATCH v1 1/2] dt-bindings: soc: starfive: Add JHB100 UART routing controller
Date: Sat, 29 Aug 2026 23:51:17 -0700 [thread overview]
Message-ID: <20260830065118.51551-2-changhuang.liang@starfivetech.com> (raw)
In-Reply-To: <20260830065118.51551-1-changhuang.liang@starfivetech.com>
Add device tree bindings for the StarFive JHB100 UART routing controller.
This controller allows dynamic routing of inputs between built-in UARTs
and physical serial I/O ports, enabling use cases such as Host <-> BMC
communication via UARTs.
The clocks property exists in the hardware, but the driver does not use
it.
Signed-off-by: Changhuang Liang <changhuang.liang@starfivetech.com>
---
.../starfive,jhb100-uart-routing.yaml | 46 +++++++++++++++++++
1 file changed, 46 insertions(+)
create mode 100644 Documentation/devicetree/bindings/soc/starfive/starfive,jhb100-uart-routing.yaml
diff --git a/Documentation/devicetree/bindings/soc/starfive/starfive,jhb100-uart-routing.yaml b/Documentation/devicetree/bindings/soc/starfive/starfive,jhb100-uart-routing.yaml
new file mode 100644
index 000000000000..6719ae59b9dc
--- /dev/null
+++ b/Documentation/devicetree/bindings/soc/starfive/starfive,jhb100-uart-routing.yaml
@@ -0,0 +1,46 @@
+# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/soc/starfive/starfive,jhb100-uart-routing.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: StarFive JHB100 UART Routing Controller
+
+maintainers:
+ - Changhuang Liang <changhuang.liang@starfivetech.com>
+
+description: >
+ The StarFive JHB100 UART routing controller allows dynamic routing of the
+ inputs for the built-in UARTs and the physical serial I/O ports.
+
+ This allows, for example, connecting the output of one UART to another
+ UART, which can be used to enable Host <-> BMC communication over UARTs,
+ e.g. to give the BMC access to the Host's serial console.
+
+properties:
+ compatible:
+ const: starfive,jhb100-uart-routing
+
+ reg:
+ maxItems: 1
+
+ clocks:
+ maxItems: 1
+
+ resets:
+ maxItems: 1
+
+required:
+ - compatible
+ - reg
+ - resets
+
+additionalProperties: false
+
+examples:
+ - |
+ uart-routing@11a42a00 {
+ compatible = "starfive,jhb100-uart-routing";
+ reg = <0x11a42a00 0x100>;
+ resets = <&per0crg 74>;
+ };
--
2.25.1
next prev parent reply other threads:[~2026-08-30 6:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-30 6:51 [PATCH v1 0/2] Add support for StarFive JHB100 UART Routing Changhuang Liang
2026-08-30 6:51 ` Changhuang Liang [this message]
2026-08-30 6:51 ` [PATCH v1 2/2] soc: starfive: Add JHB100 UART Routing driver Changhuang Liang
2026-08-30 8:35 ` Krzysztof Kozlowski
2026-08-31 1:35 ` Changhuang Liang
2026-08-31 5:54 ` Krzysztof Kozlowski
2026-08-31 6:01 ` Changhuang Liang
2026-08-31 17:24 ` Conor Dooley
2026-09-01 1:38 ` Changhuang Liang
2026-09-03 9:32 ` Krzysztof Kozlowski
2026-09-03 11:29 ` Changhuang Liang
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=20260830065118.51551-2-changhuang.liang@starfivetech.com \
--to=changhuang.liang@starfivetech.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.