From: Chen-Yu Tsai <wenst@chromium.org>
To: Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>
Cc: Chen-Yu Tsai <wenst@chromium.org>,
linux-mediatek@lists.infradead.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/4] arm64: dts: mediatek: random Chromebook cleanups
Date: Thu, 14 May 2026 18:12:48 +0800 [thread overview]
Message-ID: <20260514101254.2749300-1-wenst@chromium.org> (raw)
Hi,
Here are some random DT cleanups that are not directly related to other
topics I'm working on, but came up when checking for warnings.
The regulator related changes overlap with my other "Regulator cleanup
for Chromebooks" series [1].
Please have a look.
Thanks
ChenYu
[1] https://lore.kernel.org/all/20260505101408.1796563-1-wenst@chromium.org/
Chen-Yu Tsai (4):
arm64: dts: mediatek: mt8192-asurada: Fix SPI-NOR flash compatible
arm64: dts: mediatek: mt8192-asurada: Add (BT|WIFI)_KILL_1V8_L GPIO
line names
arm64: dts: mediatek: mt8195-cherry: Fix names for EC controlled
regulators
arm64: dts: mediatek: mt8195-cherry: Sort top level nodes correctly
.../boot/dts/mediatek/mt8192-asurada.dtsi | 6 +-
.../boot/dts/mediatek/mt8195-cherry.dtsi | 106 +++++++++---------
2 files changed, 56 insertions(+), 56 deletions(-)
--
2.54.0.563.g4f69b47b94-goog
next reply other threads:[~2026-05-14 10:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-14 10:12 Chen-Yu Tsai [this message]
2026-05-14 10:12 ` [PATCH 1/4] arm64: dts: mediatek: mt8192-asurada: Fix SPI-NOR flash compatible Chen-Yu Tsai
2026-05-14 10:12 ` [PATCH 2/4] arm64: dts: mediatek: mt8192-asurada: Add (BT|WIFI)_KILL_1V8_L GPIO line names Chen-Yu Tsai
2026-05-14 10:12 ` [PATCH 3/4] arm64: dts: mediatek: mt8195-cherry: Fix names for EC controlled regulators Chen-Yu Tsai
2026-05-14 10:12 ` [PATCH 4/4] arm64: dts: mediatek: mt8195-cherry: Sort top level nodes correctly Chen-Yu Tsai
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=20260514101254.2749300-1-wenst@chromium.org \
--to=wenst@chromium.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=devicetree@vger.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 \
/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