From: Eric Yang via B4 Relay <devnull+eric.yang.wiwynn.gmail.com@kernel.org>
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>,
Ryan Chen <ryan_chen@aspeedtech.com>,
Billy Tsai <billy_tsai@aspeedtech.com>,
patrick@stwcx.xyz
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org,
Sean He <sean.he.wiwynn@gmail.com>,
Eric Yang <eric.yang.wiwynn@gmail.com>
Subject: [PATCH] ARM: dts: aspeed: yosemite4: Remove Floating Falls board nodes
Date: Thu, 05 Nov 2026 09:49:21 +0000 [thread overview]
Message-ID: <20261105-yv4-remove-ff-nodes-v1-1-aa707a9577b7@gmail.com> (raw)
From: Sean He <sean.he.wiwynn@gmail.com>
The Floating Falls (FF) board carries a pca9537 GPIO expander at address
0x49 and a FRU EEPROM at address 0x50 on each slot I2C bus. FF was
planned in the early Yosemite 4 design but has not been used since the
DVT stage, so these addresses never acknowledge. The pca953x driver
fails to probe all eight pca9537 nodes on every boot, and the at24
driver does not bind to the eight EEPROM nodes either. Remove the nodes
for both devices.
Signed-off-by: Sean He <sean.he.wiwynn@gmail.com>
Signed-off-by: Eric Yang <eric.yang.wiwynn@gmail.com>
---
The changelog was drafted with an AI assistant (Claude Code) and
reviewed by the submitter.
Tested on two Yosemite 4 BMCs, baseline vs patched image: the eight
pca9537 nodes and the sixteen 0x49/0x50 slot-bus clients are gone, while
the 0x51/0x54 clients, gpio chips and FRU objects are unchanged.
CHECK_DTBS=y W=1 shows no new warnings and the DTB diff is exactly the
sixteen removed nodes.
---
.../dts/aspeed/aspeed-bmc-facebook-yosemite4.dts | 96 ----------------------
1 file changed, 96 deletions(-)
diff --git a/arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-yosemite4.dts b/arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-yosemite4.dts
index e4172be84..4c7c96ce4 100644
--- a/arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-yosemite4.dts
+++ b/arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-yosemite4.dts
@@ -604,18 +604,6 @@ imux16: i2c@0 {
reg = <0>;
#address-cells = <1>;
#size-cells = <0>;
- gpio@49 {
- compatible = "nxp,pca9537";
- reg = <0x49>;
- gpio-controller;
- #gpio-cells = <2>;
- };
-
- eeprom@50 {
- compatible = "atmel,24c128";
- reg = <0x50>;
- };
-
eeprom@51 {
compatible = "atmel,24c128";
reg = <0x51>;
@@ -631,18 +619,6 @@ imux17: i2c@1 {
reg = <1>;
#address-cells = <1>;
#size-cells = <0>;
- gpio@49 {
- compatible = "nxp,pca9537";
- reg = <0x49>;
- gpio-controller;
- #gpio-cells = <2>;
- };
-
- eeprom@50 {
- compatible = "atmel,24c128";
- reg = <0x50>;
- };
-
eeprom@51 {
compatible = "atmel,24c128";
reg = <0x51>;
@@ -658,18 +634,6 @@ imux18: i2c@2 {
reg = <2>;
#address-cells = <1>;
#size-cells = <0>;
- gpio@49 {
- compatible = "nxp,pca9537";
- reg = <0x49>;
- gpio-controller;
- #gpio-cells = <2>;
- };
-
- eeprom@50 {
- compatible = "atmel,24c128";
- reg = <0x50>;
- };
-
eeprom@51 {
compatible = "atmel,24c128";
reg = <0x51>;
@@ -685,18 +649,6 @@ imux19: i2c@3 {
reg = <3>;
#address-cells = <1>;
#size-cells = <0>;
- gpio@49 {
- compatible = "nxp,pca9537";
- reg = <0x49>;
- gpio-controller;
- #gpio-cells = <2>;
- };
-
- eeprom@50 {
- compatible = "atmel,24c128";
- reg = <0x50>;
- };
-
eeprom@51 {
compatible = "atmel,24c128";
reg = <0x51>;
@@ -726,18 +678,6 @@ imux20: i2c@0 {
reg = <0>;
#address-cells = <1>;
#size-cells = <0>;
- gpio@49 {
- compatible = "nxp,pca9537";
- reg = <0x49>;
- gpio-controller;
- #gpio-cells = <2>;
- };
-
- eeprom@50 {
- compatible = "atmel,24c128";
- reg = <0x50>;
- };
-
eeprom@51 {
compatible = "atmel,24c128";
reg = <0x51>;
@@ -753,18 +693,6 @@ imux21: i2c@1 {
reg = <1>;
#address-cells = <1>;
#size-cells = <0>;
- gpio@49 {
- compatible = "nxp,pca9537";
- reg = <0x49>;
- gpio-controller;
- #gpio-cells = <2>;
- };
-
- eeprom@50 {
- compatible = "atmel,24c128";
- reg = <0x50>;
- };
-
eeprom@51 {
compatible = "atmel,24c128";
reg = <0x51>;
@@ -780,18 +708,6 @@ imux22: i2c@2 {
reg = <2>;
#address-cells = <1>;
#size-cells = <0>;
- gpio@49 {
- compatible = "nxp,pca9537";
- reg = <0x49>;
- gpio-controller;
- #gpio-cells = <2>;
- };
-
- eeprom@50 {
- compatible = "atmel,24c128";
- reg = <0x50>;
- };
-
eeprom@51 {
compatible = "atmel,24c128";
reg = <0x51>;
@@ -807,18 +723,6 @@ imux23: i2c@3 {
reg = <3>;
#address-cells = <1>;
#size-cells = <0>;
- gpio@49 {
- compatible = "nxp,pca9537";
- reg = <0x49>;
- gpio-controller;
- #gpio-cells = <2>;
- };
-
- eeprom@50 {
- compatible = "atmel,24c128";
- reg = <0x50>;
- };
-
eeprom@51 {
compatible = "atmel,24c128";
reg = <0x51>;
---
base-commit: 6628e7d4c6b25c8d18f1345e3a20d21829aae7e4
change-id: 20261103-yv4-remove-ff-nodes-9e20104d2362
Best regards,
--
Eric Yang <eric.yang.wiwynn@gmail.com>
next reply other threads:[~2026-11-05 9:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-05 9:49 Eric Yang via B4 Relay [this message]
2026-11-06 5:16 ` 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=20261105-yv4-remove-ff-nodes-v1-1-aa707a9577b7@gmail.com \
--to=devnull+eric.yang.wiwynn.gmail.com@kernel.org \
--cc=andrew@codeconstruct.com.au \
--cc=billy_tsai@aspeedtech.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=eric.yang.wiwynn@gmail.com \
--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=patrick@stwcx.xyz \
--cc=robh@kernel.org \
--cc=ryan_chen@aspeedtech.com \
--cc=sean.he.wiwynn@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
all inboxes | Powered by JetHome®