All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Colin Huang" <u8813345@gmail.com>
Cc: robh@kernel.org, devicetree@vger.kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH v6 03/12] ARM: dts: aspeed: anacapa: Add EVT2 devicetree inheriting EVT1
Date: Tue, 25 Aug 2026 10:59:07 +0000	[thread overview]
Message-ID: <20260825105907.C5AF81F00A3A@smtp.kernel.org> (raw)
In-Reply-To: <20260825-anacapa-devlop-phase-devicetree-v6-3-9059a2a279ce@gmail.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] Redundant redefinition of inherited properties in the `evt2.dts` file.
--

--- Patch [3]: [PATCH v6 03/12] ARM: dts: aspeed: anacapa: Add EVT2 devicetree inheriting EVT1 ---
commit 6b89a922e36e90ce204fd77dd1e9b16cb96a0684
Author: Colin Huang <u8813345@gmail.com>

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

Add a development-phase devicetree for the Facebook Anacapa BMC EVT2
hardware revision and update the Anacapa wrapper DTS to reference it.

> 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
> new file mode 100644
> index 0000000000000..075ac39f369f7
> --- /dev/null
> +++ b/arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-anacapa-evt2.dts
> @@ -0,0 +1,178 @@
> +// SPDX-License-Identifier: GPL-2.0-or-later
> +
> +/dts-v1/;
> +#include "aspeed-bmc-facebook-anacapa-evt1.dts"
> +
> +/ {
> +	compatible = "facebook,anacapa-bmc-evt2", "aspeed,ast2600";
> +	model = "Facebook Anacapa BMC";

[Severity: Low]
This isn't a bug, but since this file includes
aspeed-bmc-facebook-anacapa-evt1.dts, is redefining the model string here
redundant? It appears to be identical to the inherited value from evt1.dts.

> +};
> +
> +&sgpiom0 {
> +	bus-frequency = <2000000>;

[Severity: Low]
This isn't a bug, but does redefining bus-frequency create a minor
maintainability hazard? This property seems to exactly match the one
inherited from the evt1.dts file.

[ ... ]

> +	"AMC_FAIL", "HPM_CPLD_RISCV_RST",
> +	"S0_ON", "";
> +
> +	ngpios = <128>;
> +
> +	status = "okay";

[Severity: Low]
This isn't a bug, but are ngpios and status also redundantly redefined? 
These exactly match the properties already inherited via Devicetree's node
merging from evt1.dts.

> +};

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260825-anacapa-devlop-phase-devicetree-v6-0-9059a2a279ce@gmail.com?part=3

  reply	other threads:[~2026-08-25 10:59 UTC|newest]

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

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=20260825105907.C5AF81F00A3A@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.