devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bryan@bryanhinton.com
To: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org
Cc: angelogioacchino.delregno@collabora.com, conor+dt@kernel.org,
	krzk+dt@kernel.org, matthias.bgg@gmail.com, robh@kernel.org,
	Bryan Hinton <bryan@bryanhinton.com>
Subject: [PATCH 0/2] arm64: dts: mt7981/openwrt-one: UART labels and console
Date: Fri, 19 Sep 2025 19:06:10 -0500	[thread overview]
Message-ID: <20250920000619.2643457-1-bryan@bryanhinton.com> (raw)

This series makes two small updates for MT7981:

- Patch 1/2: Add stable labels (uart0, uart1, uart2) in the SoC dtsi so
  that board dts files can reference them directly.
- Patch 2/2: Update the OpenWrt One board dts to define serial0 alias,
  configure chosen stdout-path, and set correct UART current-speed.

Both patches were build-tested (dtbs) and boot-tested: 
mainline Image+DTB built and loaded via U-Boot on MT7981 hardware,
with serial console output verified.

Thanks,
Bryan

---

Bryan Hinton (2):
  arm64: dts: mediatek: mt7981b: add labels for UART0/1/2 nodes
  arm64: dts: mediatek: mt7981b: OpenWrt One: set console UART to 115200

 .../arm64/boot/dts/mediatek/mt7981b-openwrt-one.dts | 13 +++++++++++++
 arch/arm64/boot/dts/mediatek/mt7981b.dtsi           |  6 +++---
 2 files changed, 16 insertions(+), 3 deletions(-)


base-commit: 1522b530ac3e2dadd75ccb351b88d3c7c4cf584e
-- 
2.51.0


             reply	other threads:[~2025-09-20  0:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-20  0:06 bryan [this message]
2025-09-20  0:06 ` [PATCH 1/2] arm64: dts: mediatek: mt7981b: add labels for UART0/1/2 nodes bryan
2025-09-20  0:06 ` [PATCH 2/2] arm64: dts: mediatek: mt7981b: OpenWrt One: set console UART to 115200 bryan
2025-09-20  2:36   ` Daniel Golle

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=20250920000619.2643457-1-bryan@bryanhinton.com \
    --to=bryan@bryanhinton.com \
    --cc=angelogioacchino.delregno@collabora.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=matthias.bgg@gmail.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;
as well as URLs for NNTP newsgroup(s).