public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Ninad Palsule <ninad@linux.ibm.com>
To: eajames@linux.ibm.com, robh@kernel.org, krzk+dt@kernel.org,
	conor+dt@kernel.org, joel@jms.id.au, andrew@codeconstruct.com.au,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org
Cc: Andrew Geissler <geissonator@yahoo.com>, ninad@linux.ibm.com
Subject: [PATCH v1 5/7] ARM: dts: aspeed: system1: disable NCSI net port
Date: Tue, 21 Apr 2026 17:45:42 -0500	[thread overview]
Message-ID: <20260421224551.1611818-6-ninad@linux.ibm.com> (raw)
In-Reply-To: <20260421224551.1611818-1-ninad@linux.ibm.com>

From: Andrew Geissler <geissonator@yahoo.com>

There appears to be a hardware issue on system1 with the shared NCSI
network port, eth2. Our use cases don't require the use of this shared
network port by the BMC so just remove it from our device tree.

The symptom is that intermittently the entire BMC network stack will
stop working during a chassis power on or off. Any active ssh sessions
to the BMC will completely hang, and then come back after 5-60 seconds.

Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Signed-off-by: Ninad Palsule <ninad@linux.ibm.com>
---
 arch/arm/boot/dts/aspeed/aspeed-bmc-ibm-system1.dts | 10 ----------
 1 file changed, 10 deletions(-)

diff --git a/arch/arm/boot/dts/aspeed/aspeed-bmc-ibm-system1.dts b/arch/arm/boot/dts/aspeed/aspeed-bmc-ibm-system1.dts
index a5252cec9903..3ccf932832f1 100644
--- a/arch/arm/boot/dts/aspeed/aspeed-bmc-ibm-system1.dts
+++ b/arch/arm/boot/dts/aspeed/aspeed-bmc-ibm-system1.dts
@@ -519,16 +519,6 @@ &mac2 {
 	use-ncsi;
 };
 
-&mac3 {
-	status = "okay";
-	pinctrl-names = "default";
-	pinctrl-0 = <&pinctrl_rmii4_default>;
-	clocks = <&syscon ASPEED_CLK_GATE_MAC4CLK>,
-		 <&syscon ASPEED_CLK_MAC4RCLK>;
-	clock-names = "MACCLK", "RCLK";
-	use-ncsi;
-};
-
 &wdt1 {
 	aspeed,reset-type = "none";
 	aspeed,external-signal;
-- 
2.51.0



  parent reply	other threads:[~2026-04-21 22:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-21 22:45 [PATCH v1 0/7] DTS updates for system1 BMC Ninad Palsule
2026-04-21 22:45 ` [PATCH v1 1/7] ARM: dts: aspeed: system1: Disable vuart2 Ninad Palsule
2026-04-21 22:45 ` [PATCH v1 2/7] ARM: dts: aspeed: system1: Enable video engine Ninad Palsule
2026-04-21 22:45 ` [PATCH v1 3/7] ARM: dts: aspeed: system1: Add usb virtual hub dev Ninad Palsule
2026-04-21 22:45 ` [PATCH v1 4/7] ARM: dts: aspeed: system1: Enable temp sensors Ninad Palsule
2026-04-21 22:45 ` Ninad Palsule [this message]
2026-04-21 22:45 ` [PATCH v1 6/7] ARM: dts: aspeed: system1: Added status LEDs Ninad Palsule
2026-04-21 22:45 ` [PATCH v1 7/7] ARM: dts: aspeed: system1: DTS updates Ninad Palsule

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=20260421224551.1611818-6-ninad@linux.ibm.com \
    --to=ninad@linux.ibm.com \
    --cc=andrew@codeconstruct.com.au \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=eajames@linux.ibm.com \
    --cc=geissonator@yahoo.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=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