From: Peter Yin <peteryin.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 11/11] ARM: dts: aspeed: Harma: remove pca9546
Date: Fri, 2 Aug 2024 00:01:35 +0800 [thread overview]
Message-ID: <20240801160136.1281291-12-peteryin.openbmc@gmail.com> (raw)
In-Reply-To: <20240801160136.1281291-1-peteryin.openbmc@gmail.com>
Remove pca9546 device from i2c bus 9.
Signed-off-by: Peter Yin <peteryin.openbmc@gmail.com>
---
.../dts/aspeed/aspeed-bmc-facebook-harma.dts | 31 -------------------
1 file changed, 31 deletions(-)
diff --git a/arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-harma.dts b/arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-harma.dts
index 4421822eb134..cf3f807a38fe 100644
--- a/arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-harma.dts
+++ b/arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-harma.dts
@@ -20,10 +20,6 @@ aliases {
i2c21 = &imux21;
i2c22 = &imux22;
i2c23 = &imux23;
- i2c24 = &imux24;
- i2c25 = &imux25;
- i2c26 = &imux26;
- i2c27 = &imux27;
i2c28 = &imux28;
i2c29 = &imux29;
i2c30 = &imux30;
@@ -409,33 +405,6 @@ gpio@31 {
"","","","";
};
- i2c-mux@71 {
- compatible = "nxp,pca9546";
- reg = <0x71>;
- #address-cells = <1>;
- #size-cells = <0>;
-
- imux24: i2c@0 {
- #address-cells = <1>;
- #size-cells = <0>;
- reg = <0>;
- };
- imux25: i2c@1 {
- #address-cells = <1>;
- #size-cells = <0>;
- reg = <1>;
- };
- imux26: i2c@2 {
- #address-cells = <1>;
- #size-cells = <0>;
- reg = <2>;
- };
- imux27: i2c@3 {
- #address-cells = <1>;
- #size-cells = <0>;
- reg = <3>;
- };
- };
// PTTV FRU
eeprom@52 {
compatible = "atmel,24c64";
--
2.25.1
prev parent reply other threads:[~2024-08-01 16:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-01 16:01 [PATCH v3 00/11] Revise Meta(Facebook) Harma BMC(AST2600) Peter Yin
2024-08-01 16:01 ` [PATCH v3 01/11] ARM: dts: aspeed: Harma: revise hsc chip Peter Yin
2024-08-01 16:01 ` [PATCH v3 02/11] ARM: dts: aspeed: Harma: add VR device Peter Yin
2024-08-02 6:36 ` Andrew Jeffery
2024-08-12 2:08 ` Andrew Jeffery
2024-08-01 16:01 ` [PATCH v3 03/11] ARM: dts: aspeed: Harma: add sgpio name Peter Yin
2024-08-01 16:01 ` [PATCH v3 04/11] ARM: dts: aspeed: Harma: add ina238 Peter Yin
2024-08-01 16:01 ` [PATCH v3 05/11] ARM: dts: aspeed: Harma: add power monitor xdp710 Peter Yin
2024-08-01 16:01 ` [PATCH v3 06/11] ARM: dts: aspeed: Harma: remove multi-host property Peter Yin
2024-08-01 16:01 ` [PATCH v3 07/11] ARM: dts: aspeed: Harma: add fru device Peter Yin
2024-08-01 16:01 ` [PATCH v3 08/11] ARM: dts: aspeed: Harma: add temperature device Peter Yin
2024-08-01 16:01 ` [PATCH v3 09/11] ARM: dts: aspeed: Harma: enable mctp controller Peter Yin
2024-08-01 16:01 ` [PATCH v3 10/11] ARM: dts: aspeed: Harma: fixed dtb_check warning Peter Yin
2024-08-01 16:01 ` Peter Yin [this message]
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=20240801160136.1281291-12-peteryin.openbmc@gmail.com \
--to=peteryin.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;
as well as URLs for NNTP newsgroup(s).