From: Jammy Huang <jammy_huang@aspeedtech.com>
To: Joel Stanley <joel@jms.id.au>,
Andrew Jeffery <andrew@codeconstruct.com.au>,
Rob Herring <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
"Oskar Senft" <osk@google.com>,
Chia-Wei Wang <chiawei_wang@aspeedtech.com>
Cc: <linux-arm-kernel@lists.infradead.org>,
<linux-aspeed@lists.ozlabs.org>, <linux-kernel@vger.kernel.org>,
<devicetree@vger.kernel.org>,
Jammy Huang <jammy_huang@aspeedtech.com>
Subject: [PATCH 0/2] Add Aspeed G7 uart routing support
Date: Tue, 3 Feb 2026 11:55:07 +0800 [thread overview]
Message-ID: <20260203-upstream_uart_routing-v1-0-6bd5dd75ee3b@aspeedtech.com> (raw)
The Aspeed 7th generation SoC supports dual node. Which means there are
2 group of uart routing.
* 0: uart0/1/2/3/9
* 1: uart5/6/7/8/10
Signed-off-by: Jammy Huang <jammy_huang@aspeedtech.com>
---
Chia-Wei Wang (1):
soc: aspeed: uart-routing: Add AST27xx dual node support
Jammy Huang (1):
dt-bindings: soc: aspeed: add aspeed,ast2700nx-uart-routing compatible
.../bindings/soc/aspeed/uart-routing.yaml | 2 +
drivers/soc/aspeed/aspeed-uart-routing.c | 424 +++++++++++++++++++++
2 files changed, 426 insertions(+)
---
base-commit: 4d310797262f0ddf129e76c2aad2b950adaf1fda
change-id: 20260130-upstream_uart_routing-1382b12e1bfb
Best regards,
--
Jammy Huang <jammy_huang@aspeedtech.com>
next reply other threads:[~2026-02-03 3:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-03 3:55 Jammy Huang [this message]
2026-02-03 3:55 ` [PATCH 1/2] dt-bindings: soc: aspeed: add aspeed,ast2700nx-uart-routing compatible Jammy Huang
2026-02-04 17:54 ` Conor Dooley
2026-02-03 3:55 ` [PATCH 2/2] soc: aspeed: uart-routing: Add AST27xx dual node support Jammy Huang
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=20260203-upstream_uart_routing-v1-0-6bd5dd75ee3b@aspeedtech.com \
--to=jammy_huang@aspeedtech.com \
--cc=andrew@codeconstruct.com.au \
--cc=chiawei_wang@aspeedtech.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=joel@jms.id.au \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=osk@google.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox