From: Tan Siewert <tan@siewert.io>
To: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Joel Stanley <joel@jms.id.au>,
Andrew Jeffery <andrew@codeconstruct.com.au>
Cc: Tan Siewert <tan@siewert.io>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/4] ARM: dts: aspeed: Convert remaining ASRock systems to NVMEM layout syntax
Date: Sun, 3 Aug 2025 17:18:16 +0200 [thread overview]
Message-ID: <20250803151822.68080-1-tan@siewert.io> (raw)
Hi,
While investigating an issue with an ASRock Rack platform, I noticed
that most of the ASPEED device trees using NVMEM cells to populate
MAC addresses still rely on a deprecated NVMEM binding syntax.
As a result, the MAC addresses are not populated from the
device tree/NVMEM cells properly, and an address from "the chip" is
being used instead.
Commit 76c5533925434 ("ARM: dts: aspeed: convert ASRock SPC621D8HM3
NVMEM content to layout syntax") was the only system that had previously
been converted to the new layout syntax.
This patch series converts all remaining ASRock Rack systems in the ASPEED
device trees to use the new NVMEM layout syntax.
Tan Siewert (4):
ARM: dts: aspeed: e3c246d4i: convert NVMEM content to layout syntax
ARM: dts: aspeed: e3c256d4i: convert NVMEM content to layout syntax
ARM: dts: aspeed: romed8hm3: convert NVMEM content to layout syntax
ARM: dts: aspeed: x570d4u: convert NVMEM content to layout syntax
.../dts/aspeed/aspeed-bmc-asrock-e3c246d4i.dts | 12 ++++++++----
.../dts/aspeed/aspeed-bmc-asrock-e3c256d4i.dts | 12 ++++++++----
.../dts/aspeed/aspeed-bmc-asrock-romed8hm3.dts | 12 ++++++++----
.../dts/aspeed/aspeed-bmc-asrock-x570d4u.dts | 18 +++++++++++-------
4 files changed, 35 insertions(+), 19 deletions(-)
--
2.43.0
next reply other threads:[~2025-08-03 15:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-03 15:18 Tan Siewert [this message]
2025-08-03 15:19 ` [PATCH 1/4] ARM: dts: aspeed: e3c246d4i: convert NVMEM content to " Tan Siewert
2025-08-03 15:19 ` [PATCH 2/4] ARM: dts: aspeed: e3c256d4i: " Tan Siewert
2025-08-03 15:19 ` [PATCH 3/4] ARM: dts: aspeed: romed8hm3: " Tan Siewert
2025-08-03 15:19 ` [PATCH 4/4] ARM: dts: aspeed: x570d4u: " Tan Siewert
2025-08-04 0:33 ` [PATCH 0/4] ARM: dts: aspeed: Convert remaining ASRock systems to NVMEM " Zev Weiss
2025-08-06 1:06 ` Andrew Jeffery
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=20250803151822.68080-1-tan@siewert.io \
--to=tan@siewert.io \
--cc=andrew@codeconstruct.com.au \
--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=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
all inboxes | Powered by JetHome®