From: Lee Yongjun <jun85566@gmail.com>
To: Florian Fainelli <florian.fainelli@broadcom.com>
Cc: Ray Jui <rjui@broadcom.com>,
Scott Branden <sbranden@broadcom.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
bcm-kernel-feedback-list@broadcom.com,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, Lee Yongjun <jun85566@gmail.com>
Subject: [PATCH v2] arm64: dts: broadcom: ns2-svk: Rename at25 node to eeprom
Date: Thu, 29 Jan 2026 09:28:10 +0900 [thread overview]
Message-ID: <20260129002810.10261-1-jun85566@gmail.com> (raw)
The AT25 EEPROM node on the Northstar 2 SVK board uses a non-standard
node name, which triggers dtbs_check warnings.
Update the node to follow the dt-schema by renaming the node from
at25@0 to eeprom@0.
Note that other legacy property updates (byte-len, page-size, addr-mode)
are handled by a separate patch.
Signed-off-by: Lee Yongjun <jun85566@gmail.com>
---
Changes in v2:
- Dropped property updates (size, pagesize, etc) as they are handled by another patch.
- Renamed the node as requested by the maintainer.
arch/arm64/boot/dts/broadcom/northstar2/ns2-svk.dts | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm64/boot/dts/broadcom/northstar2/ns2-svk.dts b/arch/arm64/boot/dts/broadcom/northstar2/ns2-svk.dts
index 5939d342aec7..ce1b099a8804 100644
--- a/arch/arm64/boot/dts/broadcom/northstar2/ns2-svk.dts
+++ b/arch/arm64/boot/dts/broadcom/northstar2/ns2-svk.dts
@@ -127,7 +127,7 @@ slic@0 {
&ssp1 {
status = "okay";
- at25@0 {
+ eeprom@0 {
compatible = "atmel,at25";
reg = <0>;
spi-max-frequency = <5000000>;
--
2.34.1
next reply other threads:[~2026-01-29 0:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-29 0:28 Lee Yongjun [this message]
2026-01-30 16:38 ` [PATCH v2] arm64: dts: broadcom: ns2-svk: Rename at25 node to eeprom Ray Jui
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=20260129002810.10261-1-jun85566@gmail.com \
--to=jun85566@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=florian.fainelli@broadcom.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjui@broadcom.com \
--cc=robh@kernel.org \
--cc=sbranden@broadcom.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