Devicetree
 help / color / mirror / Atom feed
From: Colin Huang via B4 Relay <devnull+u8813345.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>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	 linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org,
	 colin.huang2@amd.com, Colin Huang <u8813345@gmail.com>,
	 Rex Fu <rex.fu.amd@gmail.com>
Subject: [PATCH v5 07/15] ARM: dts: aspeed: anacapa: Align PDB fan GPIO numbering
Date: Thu, 13 Aug 2026 19:59:37 +0800	[thread overview]
Message-ID: <20260813-anacapa-devlop-phase-devicetree-v5-7-c7058f63dc67@gmail.com> (raw)
In-Reply-To: <20260813-anacapa-devlop-phase-devicetree-v5-0-c7058f63dc67@gmail.com>

From: Rex Fu <rex.fu.amd@gmail.com>

Update the LPDB and RPDB fan GPIO line names to align with the platform
fan numbering scheme.

The LPDB fan GPIOs are named FAN0 through FAN4, while the RPDB fan GPIOs
are named FAN5 through FAN8. This keeps the GPIO line names consistent
with the fan inventory and platform-level fan numbering.

Signed-off-by: Rex Fu <rex.fu.amd@gmail.com>
Signed-off-by: Colin Huang <u8813345@gmail.com>
---
 .../aspeed/aspeed-bmc-facebook-anacapa-evt2.dts    | 33 ++++++++++++++++++++++
 1 file changed, 33 insertions(+)

diff --git a/arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-anacapa-evt2.dts b/arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-anacapa-evt2.dts
index c7bffa7c6557..ff393ad7cdb7 100644
--- a/arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-anacapa-evt2.dts
+++ b/arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-anacapa-evt2.dts
@@ -8,6 +8,39 @@ / {
 	compatible = "facebook,anacapa-bmc-evt2", "aspeed,ast2600";
 };
 
+// MB - PDB
+&i2c8 {
+	i2c-mux@72 {
+		i2c8mux0ch0: i2c@0 {
+			gpio@24 {
+				gpio-line-names =
+					"RPDB_EAM2_PRSNT_MOS_N_R", "RPDB_EAM3_PRSNT_MOS_N_R",
+					"RPDB_PWRGD_P50V_HSC4_SYS_R",
+					"RPDB_PWRGD_P50V_STBY_SYS_BUF_R",
+					"RPDB_P50V_FAN5_R2_PG", "RPDB_P50V_FAN6_R2_PG",
+					"RPDB_P50V_FAN7_R2_PG", "RPDB_P50V_FAN8_R2_PG",
+					"", "RPDB_FAN5_PRSNT_N_R",
+					"", "RPDB_FAN6_PRSNT_N_R",
+					"RPDB_FAN7_PRSNT_N_R", "RPDB_FAN8_PRSNT_N_R",
+					"", "";
+			};
+		};
+		i2c8mux0ch1: i2c@1 {
+			gpio@24 {
+				gpio-line-names =
+					"LPDB_P50V_FAN0_R2_PG","LPDB_P50V_FAN1_R2_PG",
+					"LPDB_P50V_FAN2_R2_PG","LPDB_P50V_FAN3_R2_PG",
+					"LPDB_P50V_FAN4_R2_PG","LPDB_FAN0_PRSNT_N_R",
+					"LPDB_FAN1_PRSNT_N_R","LPDB_FAN2_PRSNT_N_R",
+					"LPDB_FAN3_PRSNT_N_R","LPDB_FAN4_PRSNT_N_R",
+					"","",
+					"","",
+					"","";
+			};
+		};
+	};
+};
+
 // SCM
 &i2c9 {
 

-- 
2.34.1



  parent reply	other threads:[~2026-08-13 12:00 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-13 11:59 [PATCH v5 00/15] ARM: dts: aspeed: anacapa: restructure devicetree for development-phase Colin Huang via B4 Relay
2026-08-13 11:59 ` [PATCH v5 01/15] dt-bindings: arm: aspeed: Add Anacapa EVT1 EVT2 DVT board Colin Huang via B4 Relay
2026-08-13 11:59 ` [PATCH v5 02/15] ARM: dts: aspeed: anacapa: Add EVT1 devicetree and point wrapper to it Colin Huang via B4 Relay
2026-08-13 12:10   ` sashiko-bot
2026-08-13 11:59 ` [PATCH v5 03/15] ARM: dts: aspeed: anacapa: Add EVT2 devicetree inheriting EVT1 Colin Huang via B4 Relay
2026-08-13 11:59 ` [PATCH v5 04/15] ARM: dts: aspeed: anacapa: Add DVT devicetree inheriting EVT2 Colin Huang via B4 Relay
2026-08-13 11:59 ` [PATCH v5 05/15] ARM: dts: aspeed: anacapa: Add additional EEPROM node for SCM Colin Huang via B4 Relay
2026-08-13 11:59 ` [PATCH v5 06/15] ARM: dts: aspeed: anacapa: Add eeprom device node for NFC adaptor board Colin Huang via B4 Relay
2026-08-13 11:59 ` Colin Huang via B4 Relay [this message]
2026-08-13 11:59 ` [PATCH v5 08/15] ARM: dts: aspeed: anacapa: Enable MCTP and FRU for NIC Colin Huang via B4 Relay
2026-08-13 11:59 ` [PATCH v5 09/15] ARM: dts: aspeed: anacapa: evt2: Add shunt resistor values for HSC monitors Colin Huang via B4 Relay
2026-08-13 12:04   ` sashiko-bot
2026-08-13 11:59 ` [PATCH v5 10/15] ARM: dts: aspeed: anacapa: Add LPDB fuse monitor GPIO expander Colin Huang via B4 Relay
2026-08-13 11:59 ` [PATCH v5 11/15] ARM: dts: aspeed: anacapa: Simplify leakage GPIO line names Colin Huang via B4 Relay
2026-08-13 11:59 ` [PATCH v5 12/15] ARM: dts: aspeed: anacapa: Add SPI flash VCC supply Colin Huang via B4 Relay
2026-08-13 11:59 ` [PATCH v5 13/15] ARM: dts: aspeed: anacapa: fix dt-check-style strict violations Colin Huang via B4 Relay
2026-08-13 11:59 ` [PATCH v5 14/15] ARM: dts: aspeed: anacapa: Use default SPI2 memory mapping Colin Huang via B4 Relay
2026-08-13 11:59 ` [PATCH v5 15/15] ARM: dts: aspeed: anacapa: Remove redundant vhub pinctrl-names Colin Huang via B4 Relay
2026-08-13 15:12 ` [PATCH v5 00/15] ARM: dts: aspeed: anacapa: restructure devicetree for development-phase Tan Siewert

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=20260813-anacapa-devlop-phase-devicetree-v5-7-c7058f63dc67@gmail.com \
    --to=devnull+u8813345.gmail.com@kernel.org \
    --cc=andrew@codeconstruct.com.au \
    --cc=colin.huang2@amd.com \
    --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=rex.fu.amd@gmail.com \
    --cc=robh@kernel.org \
    --cc=u8813345@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