From: Colin Huang <u8813345@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>,
Ryan Chen <ryan_chen@aspeedtech.com>,
Billy Tsai <billy_tsai@aspeedtech.com>
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>
Subject: [PATCH v10 16/16] ARM: dts: aspeed: anacapa: Rename FM_CPU0_PWRGD to host0-ready
Date: Thu, 29 Oct 2026 21:38:45 +0800 [thread overview]
Message-ID: <20261029-anacapa-devlop-phase-devicetree-v10-16-26ee3cf9d9d0@gmail.com> (raw)
In-Reply-To: <20261029-anacapa-devlop-phase-devicetree-v10-0-26ee3cf9d9d0@gmail.com>
phosphor-state-manager uses the "host0-ready" GPIO line to determine
whether the host is running. The current "FM_CPU0_PWRGD" line name is
not recognized for this purpose.
Rename the GPIO line to "host0-ready" so that phosphor-state-manager
can correctly determine the host state.
Signed-off-by: Colin Huang <u8813345@gmail.com>
---
arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-anacapa-dvt.dtsi | 2 +-
arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-anacapa-evt1.dtsi | 2 +-
arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-anacapa-evt2.dtsi | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-anacapa-dvt.dtsi b/arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-anacapa-dvt.dtsi
index 698308049c38..3685d47fb6f0 100644
--- a/arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-anacapa-dvt.dtsi
+++ b/arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-anacapa-dvt.dtsi
@@ -250,7 +250,7 @@ &sgpiom0 {
/* P0-P7 line 240-255 */
"CPU0_SLP_S5_N_R", "NFC_VEN",
"CPU0_SLP_S3_N_R", "",
- "FM_CPU0_PWRGD", "",
+ "host0-ready", "",
"PWRGD_RMC", "",
"FM_RST_CPU0_RESET_N", "RBB_CPLD_RISCV_RST",
"FM_PWRGD_CPU0_PWROK", "LBB_CPLD_RISCV_RST",
diff --git a/arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-anacapa-evt1.dtsi b/arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-anacapa-evt1.dtsi
index 7745802d3640..6a526a7de2a3 100644
--- a/arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-anacapa-evt1.dtsi
+++ b/arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-anacapa-evt1.dtsi
@@ -1084,7 +1084,7 @@ &sgpiom0 {
/* P0-P7 line 240-255 */
"CPU0_SLP_S5_N_R", "NFC_VEN",
"CPU0_SLP_S3_N_R", "",
- "FM_CPU0_PWRGD", "",
+ "host0-ready", "",
"PWRGD_RMC", "",
"FM_RST_CPU0_RESET_N", "",
"FM_PWRGD_CPU0_PWROK", "",
diff --git a/arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-anacapa-evt2.dtsi b/arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-anacapa-evt2.dtsi
index 766aa26b6cea..f14985883291 100644
--- a/arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-anacapa-evt2.dtsi
+++ b/arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-anacapa-evt2.dtsi
@@ -458,7 +458,7 @@ &sgpiom0 {
/* P0-P7 line 240-255 */
"CPU0_SLP_S5_N_R", "NFC_VEN",
"CPU0_SLP_S3_N_R", "",
- "FM_CPU0_PWRGD", "",
+ "host0-ready", "",
"PWRGD_RMC", "",
"FM_RST_CPU0_RESET_N", "RBB_CPLD_RISCV_RST",
"FM_PWRGD_CPU0_PWROK", "LBB_CPLD_RISCV_RST",
--
2.34.1
prev parent reply other threads:[~2026-10-29 13:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-29 13:38 [PATCH v10 00/16] ARM: dts: aspeed: anacapa: restructure devicetree for development-phase Colin Huang
2026-10-29 13:38 ` [PATCH v10 01/16] ARM: dts: aspeed: anacapa: Add EVT1 devicetree and point wrapper to it Colin Huang
2026-10-29 13:38 ` [PATCH v10 02/16] ARM: dts: aspeed: anacapa: Add EVT2 devicetree inheriting EVT1 Colin Huang
2026-10-29 13:38 ` [PATCH v10 03/16] ARM: dts: aspeed: anacapa: Add DVT devicetree inheriting EVT2 Colin Huang
2026-10-29 13:38 ` [PATCH v10 04/16] ARM: dts: aspeed: anacapa: Add additional EEPROM node for SCM Colin Huang
2026-10-29 13:38 ` [PATCH v10 05/16] ARM: dts: aspeed: anacapa: Add eeprom device node for NFC adaptor board Colin Huang
2026-10-29 13:43 ` Krzysztof Kozlowski
2026-10-29 13:38 ` [PATCH v10 06/16] ARM: dts: aspeed: anacapa: Align PDB fan GPIO numbering Colin Huang
2026-10-29 13:38 ` [PATCH v10 07/16] ARM: dts: aspeed: anacapa: Enable MCTP and FRU for NIC Colin Huang
2026-10-29 13:38 ` [PATCH v10 08/16] ARM: dts: aspeed: anacapa: evt2: Add shunt resistor values for HSC monitors Colin Huang
2026-10-29 13:38 ` [PATCH v10 09/16] ARM: dts: aspeed: anacapa: Add LPDB fuse monitor GPIO expander Colin Huang
2026-10-29 13:38 ` [PATCH v10 10/16] ARM: dts: aspeed: anacapa: Simplify leakage GPIO line names Colin Huang
2026-10-29 13:38 ` [PATCH v10 11/16] ARM: dts: aspeed: anacapa: Add SPI flash VCC supply Colin Huang
2026-10-29 13:38 ` [PATCH v10 12/16] ARM: dts: aspeed: anacapa: Add NCT7363 fan controllers Colin Huang
2026-10-29 13:38 ` [PATCH v10 13/16] ARM: dts: aspeed: anacapa: Remove LTC4287 power monitors Colin Huang
2026-10-29 13:38 ` [PATCH v10 14/16] ARM: dts: aspeed: anacapa: Update EDSFF power status signals Colin Huang
2026-10-29 13:38 ` [PATCH v10 15/16] ARM: dts: aspeed: anacapa: Add E1.S FRU EEPROMs Colin Huang
2026-10-29 13:38 ` Colin Huang [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=20261029-anacapa-devlop-phase-devicetree-v10-16-26ee3cf9d9d0@gmail.com \
--to=u8813345@gmail.com \
--cc=andrew@codeconstruct.com.au \
--cc=billy_tsai@aspeedtech.com \
--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=robh@kernel.org \
--cc=ryan_chen@aspeedtech.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®