From: Andrew Jeffery <andrew@codeconstruct.com.au>
To: Rex.Fu@amd.com, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Joel Stanley <joel@jms.id.au>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ARM: dts: aspeed: anacapa: name EDSFF and thermtrip SGPIO lines
Date: Mon, 18 May 2026 16:17:59 +0930 [thread overview]
Message-ID: <bae3a186da639118d88ad2632c5edf8963946dc1.camel@codeconstruct.com.au> (raw)
In-Reply-To: <20260430-anacapa-sgpio-edsff-thermtrip-v1-1-2fd5e72435d0@amd.com>
Hello Rex,
On Thu, 2026-04-30 at 13:44 +0800, Rex Fu via B4 Relay wrote:
> From: Rex Fu <Rex.Fu@amd.com>
>
> Name the Anacapa SGPIO lines used for EDSFF power-good and thermtrip
> assertion signals.
>
> The affected lines replace legacy
>
Which are legacy?
> or unused
>
Which are unused?
> CPU-related names with the
> platform signal names used by userspace monitoring.
This is the kind of change that has the potential to break old
userspace. Why is it appropriate? I'd like a more precise discussion in
the commit message.
Was there some other underlying change (e.g. a new revision of the
platform design)?
Andrew
>
> Signed-off-by: Rex Fu <Rex.Fu@amd.com>
> ---
> arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-anacapa.dts | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-anacapa.dts b/arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-anacapa.dts
> index 2cb7bd128d24..fe960bb7bc27 100644
> --- a/arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-anacapa.dts
> +++ b/arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-anacapa.dts
> @@ -912,7 +912,7 @@ &sgpiom0 {
> "PWRGD_PVDDIO_P0", "",
> "PWRGD_PVDDIO_MEM_S3_P0", "",
> "PWRGD_CHMP_CPU0_FPGA", "",
> - "PWRGD_CHIL_CPU0_FPGA", "",
> + "HPM_EDSFF_PG", "",
> "PWRGD_CHEH_CPU0_FPGA", "",
> "PWRGD_CHAD_CPU0_FPGA", "FM_BMC_READY_PLD",
> "", "",
> @@ -957,8 +957,8 @@ &sgpiom0 {
> "PDB_ALERT_R_N", "",
>
> /* L0-L7 line 176-191 */
> - "CPU0_SP7R1", "", "CPU0_SP7R2", "",
> - "CPU0_SP7R3", "", "CPU0_SP7R4", "",
> + "L_EDSFF2_PG", "", "L_EDSFF3_PG", "",
> + "R_EDSFF2_PG", "", "R_EDSFF3_PG", "",
> "CPU0_CORETYPE0", "", "CPU0_CORETYPE1", "",
> "CPU0_CORETYPE2", "", "FM_BIOS_POST_CMPLT_R_N", "",
>
> @@ -984,8 +984,8 @@ &sgpiom0 {
> "HPM_PWR_FAIL", "Port80_b0",
> "FM_DIMM_IP_FAIL", "Port80_b1",
> "FM_DIMM_AH_FAIL", "Port80_b2",
> - "HPM_AMC_THERMTRIP_R_L", "Port80_b3",
> - "FM_CPU0_THERMTRIP_N", "Port80_b4",
> + "AMC_THERMTRIP_ASSERT", "Port80_b3",
> + "CPU_THERMTRIP_ASSERT", "Port80_b4",
> "PVDDCR_SOC_P0_OCP_L", "Port80_b5",
> "CPLD_SGPIO_RDY", "Port80_b6",
> "", "Port80_b7",
>
> ---
> base-commit: 9974969c14031a097d6b45bcb7a06bb4aa525c40
> change-id: 20260430-anacapa-sgpio-edsff-thermtrip-acb228bf61be
>
> Best regards,
> --
> Rex Fu <Rex.Fu@amd.com>
>
next prev parent reply other threads:[~2026-05-18 6:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-30 5:44 [PATCH] ARM: dts: aspeed: anacapa: name EDSFF and thermtrip SGPIO lines Rex Fu via B4 Relay
2026-05-18 6:47 ` Andrew Jeffery [this message]
2026-05-18 9:01 ` Fu, Rex
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=bae3a186da639118d88ad2632c5edf8963946dc1.camel@codeconstruct.com.au \
--to=andrew@codeconstruct.com.au \
--cc=Rex.Fu@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 \
/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