On Tue, 2025-11-18 at 18:53 +0800, Kevin Tung wrote:
> Rename P0_I3C_APML_ALERT_L to FM_APML_CPU_ALERT_N for clarity.
Are user space components looking for these names? Will updating the
devicetree break older applications? I'd like to see more discussion of
these problems in the commit message.
Cheers,
Andrew
>
> Signed-off-by: Kevin Tung <kevin.tung.openbmc@gmail.com>
> ---
> arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-yosemite5.dts | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-yosemite5.dts b/arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-yosemite5.dts
> index 45b8ac2e8c65a4f672e64571631b7f6944f26213..060757b7211a6da777c51d9f0c886796cf2450a4 100644
> --- a/arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-yosemite5.dts
> +++ b/arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-yosemite5.dts
> @@ -964,7 +964,7 @@ &sgpiom0 {
> "FAULT_P3V3_NIC_N","",
> "FAULT_P12V_NIC_N","",
> "FAULT_P12V_SCM_N","",
> - "P0_I3C_APML_ALERT_L","",
> + "FM_APML_CPU_ALERT_N","",
> "ALERT_INLET_TEMP_N","",
> "FM_CPU_PROCHOT_R_N","",
> "FM_CPU_THERMTRIP_N","",