From: "Rob Herring (Arm)" <robh@kernel.org>
To: Changhuang Liang <changhuang.liang@starfivetech.com>
Cc: Jani Nikula <jani.nikula@intel.com>,
Hanjun Guo <guohanjun@huawei.com>,
Mukesh Rathor <mrathor@linux.microsoft.com>,
Jakub Kicinski <kuba@kernel.org>, Jason Gunthorpe <jgg@ziepe.ca>,
Joel Stanley <joel@jms.id.au>,
Andrew Jeffery <andrew@codeconstruct.com.au>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Karthikeyan KS <karthiproffesional@gmail.com>,
Paolo Abeni <pabeni@redhat.com>,
Pengpeng Hou <pengpeng@iscas.ac.cn>,
openbmc@lists.ozlabs.org, devicetree@vger.kernel.org,
linux-aspeed@lists.ozlabs.org,
Vladimir Oltean <vladimir.oltean@nxp.com>,
Dan Williams <djbw@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Dave Penkler <dpenkler@gmail.com>,
Shuah Khan <skhan@linuxfoundation.org>,
linux-kernel@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
James Morse <james.morse@arm.com>,
Jonathan Cameron <jic23@kernel.org>,
linux-doc@vger.kernel.org,
Alexandra Winter <wintera@linux.ibm.com>,
Philipp Zabel <p.zabel@pengutronix.de>,
Jonathan Corbet <corbet@lwn.net>,
Breno Leitao <leitao@debian.org>,
Stephen Hemminger <stephen@networkplumber.org>,
linux-arm-kernel@lists.infradead.org,
Chia-Wei Wang <chiawei_wang@aspeedtech.com>,
Julian Braha <julianbraha@gmail.com>,
Alexander Usyskin <alexander.usyskin@intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
Oskar Senft <osk@google.com>, Vitaly Lubart <lubvital@gmail.com>
Subject: Re: [PATCH v3 3/4] dt-bindings: soc: starfive: Add StarFive JHB100 UART routing
Date: Wed, 7 Oct 2026 16:00:58 -0500 [thread overview]
Message-ID: <179140685827.281341.11055156225840359821.robh@kernel.org> (raw)
In-Reply-To: <20260925050947.9900-4-changhuang.liang@starfivetech.com>
On Thu, 24 Sep 2026 22:09:46 -0700, Changhuang Liang wrote:
> Add device tree binding 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>
> ---
> .../soc/starfive/starfive,uart-routing.yaml | 46 +++++++++++++++++++
> 1 file changed, 46 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/soc/starfive/starfive,uart-routing.yaml
>
Reviewed-by: Rob Herring (Arm) <robh@kernel.org>
next prev parent reply other threads:[~2026-10-07 21:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-25 5:09 [PATCH v3 0/4] Add support for StarFive JHB100 UART Routing Changhuang Liang
2026-09-25 5:09 ` [PATCH v3 1/4] uart-routing: Add common UART routing framework Changhuang Liang
2026-09-25 5:09 ` [PATCH v3 2/4] soc: aspeed: Move UART routing driver to drivers/uart-routing Changhuang Liang
2026-09-25 5:09 ` [PATCH v3 3/4] dt-bindings: soc: starfive: Add StarFive JHB100 UART routing Changhuang Liang
2026-10-07 21:00 ` Rob Herring (Arm) [this message]
2026-09-25 5:09 ` [PATCH v3 4/4] uart-routing: Add UART Routing driver for StarFive JHB100 SoC 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=179140685827.281341.11055156225840359821.robh@kernel.org \
--to=robh@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=alexander.usyskin@intel.com \
--cc=andrew@codeconstruct.com.au \
--cc=changhuang.liang@starfivetech.com \
--cc=chiawei_wang@aspeedtech.com \
--cc=conor+dt@kernel.org \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=djbw@kernel.org \
--cc=dpenkler@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=guohanjun@huawei.com \
--cc=james.morse@arm.com \
--cc=jani.nikula@intel.com \
--cc=jgg@ziepe.ca \
--cc=jic23@kernel.org \
--cc=joel@jms.id.au \
--cc=julianbraha@gmail.com \
--cc=karthiproffesional@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=leitao@debian.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lubvital@gmail.com \
--cc=mrathor@linux.microsoft.com \
--cc=openbmc@lists.ozlabs.org \
--cc=osk@google.com \
--cc=p.zabel@pengutronix.de \
--cc=pabeni@redhat.com \
--cc=pengpeng@iscas.ac.cn \
--cc=skhan@linuxfoundation.org \
--cc=stephen@networkplumber.org \
--cc=vladimir.oltean@nxp.com \
--cc=wintera@linux.ibm.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