From: Fred Chen <fredchen.openbmc@gmail.com>
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>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: [PATCH v3 2/5] ARM: dts: aspeed: santabarbara: Disable power monitor nodes
Date: Fri, 7 Aug 2026 16:34:05 +0800 [thread overview]
Message-ID: <20260807083415.672008-3-fredchen.openbmc@gmail.com> (raw)
In-Reply-To: <20260807083415.672008-1-fredchen.openbmc@gmail.com>
Due to a design change, this power monitor IC now has multiple
sources, and different vendors' parts require different drivers.
Disable these nodes so the kernel does not auto-probe a driver, and
let userspace instantiate the correct driver based on the part
actually populated on the board.
Signed-off-by: Fred Chen <fredchen.openbmc@gmail.com>
---
arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-santabarbara.dts | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-santabarbara.dts b/arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-santabarbara.dts
index 2a822e38f091..04fa9a5e0d04 100644
--- a/arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-santabarbara.dts
+++ b/arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-santabarbara.dts
@@ -585,24 +585,28 @@ power-monitor@40 {
compatible = "ti,ina230";
reg = <0x40>;
shunt-resistor = <2000>;
+ status = "disabled";
};
power-monitor@41 {
compatible = "ti,ina230";
reg = <0x41>;
shunt-resistor = <2000>;
+ status = "disabled";
};
power-monitor@44 {
compatible = "ti,ina230";
reg = <0x44>;
shunt-resistor = <2000>;
+ status = "disabled";
};
power-monitor@45 {
compatible = "ti,ina230";
reg = <0x45>;
shunt-resistor = <2000>;
+ status = "disabled";
};
};
--
2.52.0
next prev parent reply other threads:[~2026-08-07 8:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-07 8:34 [PATCH v3 0/5] ARM: dts: aspeed: santabarbara: Add system monitoring GPIOs Fred Chen
2026-08-07 8:34 ` [PATCH v3 1/5] " Fred Chen
2026-08-07 8:34 ` Fred Chen [this message]
2026-08-07 8:34 ` [PATCH v3 3/5] ARM: dts: aspeed: santabarbara: Add JTAG GPIO line names Fred Chen
2026-08-07 8:34 ` [PATCH v3 4/5] ARM: dts: aspeed: santabarbara: Add SGPIO " Fred Chen
2026-08-07 8:34 ` [PATCH v3 5/5] ARM: dts: aspeed: santabarbara: Add leak cable present IO expander Fred Chen
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=20260807083415.672008-3-fredchen.openbmc@gmail.com \
--to=fredchen.openbmc@gmail.com \
--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