All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Colin Huang" <u8813345@gmail.com>
Cc: conor+dt@kernel.org, robh@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v7 02/11] ARM: dts: aspeed: anacapa: Add EVT2 devicetree inheriting EVT1
Date: Tue, 01 Sep 2026 12:28:52 +0000	[thread overview]
Message-ID: <20260901122853.23E641F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260901-anacapa-devlop-phase-devicetree-v7-2-0bd71d2e0105@gmail.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] Incorrect GPIO line name mapping due to a likely copy-paste error in the B-block of sgpiom0.
--

commit aa80bc774dd824dd074a3ccff2eaf0de685d5eb4
Author: Colin Huang <u8813345@gmail.com>

ARM: dts: aspeed: anacapa: Add EVT2 devicetree inheriting EVT1

This commit adds a development-phase devicetree for the Facebook Anacapa BMC
EVT2 hardware revision. It updates the Anacapa wrapper DTS to reference this
new EVT2 file instead of EVT1.

> 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
> new file mode 100644
> index 0000000000000..be7f17ad5f8ec
> --- /dev/null
> +++ b/arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-anacapa-evt2.dtsi
> @@ -0,0 +1,168 @@
> +// SPDX-License-Identifier: GPL-2.0-or-later
> +
> +/dts-v1/;
> +#include "aspeed-bmc-facebook-anacapa-evt1.dtsi"
> +
> +&sgpiom0 {
> +	gpio-line-names =

[ ... ]

> +	/* B0-B7 line 16-31 */
> +	"Channel0_leakage_EAM3", "FM_CPU_FPGA_JTAG_MUX_SEL",
> +	"Channel1_leakage_EAM0", "FM_SCM_JTAG_MUX_SEL",
> +	"Channel2_leakage_Manifold1", "FM_BRIDGE_JTAG_MUX_SEL",
> +	"Channel5_leakage_present_EAM1", "FM_CPU0_NMI_SYNC_FLOOD_N",

[Severity: Medium]
Does this code break the sequence of ChannelX_leakage pins?

It places a _present signal here instead of in the D or C blocks, which
strongly suggests a copy-paste error overwriting what should have been
Channel3_leakage.

If this is an unintended copy-paste error in the B-block of sgpiom0,
userspace tools monitoring hardware could read the wrong physical pin for
Channel 5's presence and fail to read Channel 3's leakage entirely,
breaking hardware monitoring logic.

> +	"Channel4_leakage_Manifold2", "BMC_AINIC0_WP_R2_L",
> +	"Channel5_leakage_EAM1", "BMC_AINIC1_WP_R2_L",
> +	"Channel6_leakage_CPU_DIMM", "CPLD_BUF_R_AGPIO330",
> +	"Channel7_leakage_EAM2", "CPLD_BUF_R_AGPIO331",

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260901-anacapa-devlop-phase-devicetree-v7-0-0bd71d2e0105@gmail.com?part=2

  reply	other threads:[~2026-09-01 12:28 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-01 12:15 [PATCH v7 00/11] ARM: dts: aspeed: anacapa: restructure devicetree for development-phase Colin Huang via B4 Relay
2026-09-01 12:15 ` Colin Huang
2026-09-01 12:15 ` [PATCH v7 01/11] ARM: dts: aspeed: anacapa: Add EVT1 devicetree and point wrapper to it Colin Huang via B4 Relay
2026-09-01 12:15   ` Colin Huang
2026-09-01 12:30   ` sashiko-bot
2026-09-02  8:06     ` Colin Huang
2026-09-01 12:15 ` [PATCH v7 02/11] ARM: dts: aspeed: anacapa: Add EVT2 devicetree inheriting EVT1 Colin Huang via B4 Relay
2026-09-01 12:15   ` Colin Huang
2026-09-01 12:28   ` sashiko-bot [this message]
2026-09-02  8:14     ` Colin Huang
2026-09-01 12:15 ` [PATCH v7 03/11] ARM: dts: aspeed: anacapa: Add DVT devicetree inheriting EVT2 Colin Huang via B4 Relay
2026-09-01 12:15   ` Colin Huang
2026-09-01 12:15 ` [PATCH v7 04/11] ARM: dts: aspeed: anacapa: Add additional EEPROM node for SCM Colin Huang via B4 Relay
2026-09-01 12:15   ` Colin Huang
2026-09-01 12:15 ` [PATCH v7 05/11] ARM: dts: aspeed: anacapa: Add eeprom device node for NFC adaptor board Colin Huang via B4 Relay
2026-09-01 12:15   ` Colin Huang
2026-09-01 12:15 ` [PATCH v7 06/11] ARM: dts: aspeed: anacapa: Align PDB fan GPIO numbering Colin Huang via B4 Relay
2026-09-01 12:15   ` Colin Huang
2026-09-01 12:15 ` [PATCH v7 07/11] ARM: dts: aspeed: anacapa: Enable MCTP and FRU for NIC Colin Huang via B4 Relay
2026-09-01 12:15   ` Colin Huang
2026-09-01 12:15 ` [PATCH v7 08/11] ARM: dts: aspeed: anacapa: evt2: Add shunt resistor values for HSC monitors Colin Huang via B4 Relay
2026-09-01 12:15   ` Colin Huang
2026-09-01 12:15 ` [PATCH v7 09/11] ARM: dts: aspeed: anacapa: Add LPDB fuse monitor GPIO expander Colin Huang via B4 Relay
2026-09-01 12:15   ` Colin Huang
2026-09-01 12:15 ` [PATCH v7 10/11] ARM: dts: aspeed: anacapa: Simplify leakage GPIO line names Colin Huang via B4 Relay
2026-09-01 12:15   ` Colin Huang
2026-09-01 12:15 ` [PATCH v7 11/11] ARM: dts: aspeed: anacapa: Add SPI flash VCC supply Colin Huang via B4 Relay
2026-09-01 12:15   ` Colin Huang

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=20260901122853.23E641F000E9@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.