Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Grégoire Layet" <gregoire.layet@9elements.com>
Cc: robh@kernel.org, conor+dt@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v3 2/2] ARM: dts: aspeed-g6: add pcie-kcs4
Date: Mon, 27 Jul 2026 07:42:40 +0000	[thread overview]
Message-ID: <20260727074240.B59651F000E9@smtp.kernel.org> (raw)
In-Reply-To: <1dac6b9ae1565a2265e87537141e46c988d16de3.1785135437.git.gregoire.layet@9elements.com>

Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:

New issues:
- [Low] The `pcie_kcs4` device tree node is missing the `clocks` property.

Pre-existing issues:
- [High] The `kcs_bmc_aspeed` driver accesses hardware registers without requesting or enabling the required clock.
--

--- Patch [2]: [PATCH v3 2/2] ARM: dts: aspeed-g6: add pcie-kcs4 ---
commit 206a33dca85271dba16c0470168b764c592b52a0
Author: Grégoire Layet <gregoire.layet@9elements.com>

ARM: dts: aspeed-g6: add pcie-kcs4

This commit adds the pcie_kcs4 node to the LPC bus in the ast2600 g6
common dtsi. It enables a KCS-compatible interface exposed over PCIe
for IPMI communication with the host.

> diff --git a/arch/arm/boot/dts/aspeed/aspeed-g6.dtsi b/arch/arm/boot/dts/aspeed/aspeed-g6.dtsi
> --- a/arch/arm/boot/dts/aspeed/aspeed-g6.dtsi
> +++ b/arch/arm/boot/dts/aspeed/aspeed-g6.dtsi

[ ... ]

> @@ -656,6 +656,14 @@ ibt: ibt@140 {
>  					clocks = <&syscon ASPEED_CLK_GATE_LCLK>;
>  					status = "disabled";
>  				};
> +
> +				pcie_kcs4: kcs@914 {
> +					compatible = "aspeed,ast2600-kcs-bmc";
> +					reg = <0x914 0x1>, <0x918 0x1>, <0x91c 0x1>;
> +					interrupts = <GIC_SPI 177 IRQ_TYPE_LEVEL_HIGH>;

[Severity: Low]
Should this node include a clocks property? Neighboring KCS nodes include 
clocks = <&syscon ASPEED_CLK_GATE_LCLK>;. Leaving this out could result in 
an incomplete hardware description in the device tree.

[Severity: High]
This is a pre-existing issue, but does the kcs_bmc_aspeed driver need
to request and enable the required LCLK before accessing these registers?

When aspeed_kcs_probe() in drivers/char/ipmi/kcs_bmc_aspeed.c is called,
it issues regmap writes to the LPC controller registers via 
aspeed_kcs_set_address():

drivers/char/ipmi/kcs_bmc_aspeed.c:aspeed_kcs_probe() {
        ...
        rc = aspeed_kcs_set_address(kcs_bmc, addrs, nr_addrs);
        if (rc)
                return rc;

        /* Host to BMC IRQ */
        rc = aspeed_kcs_config_downstream_irq(kcs_bmc, pdev);
        ...
}

If the bootloader leaves the ASPEED_CLK_GATE_LCLK disabled, or if the clock
framework dynamically disables unused clocks, accessing these registers
without enabling the clock might cause a synchronous external abort or
system hang.

> +
> +					status = "disabled";
> +				};
>  			};

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/cover.1785135437.git.gregoire.layet@9elements.com?part=2

      reply	other threads:[~2026-07-27  7:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-27  7:27 [PATCH v3 0/2] ipmi: kcs_bmc_aspeed: g6: Add KCS Channel 4 over PCIe Grégoire Layet
2026-07-27  7:27 ` [PATCH v3 1/2] " Grégoire Layet
2026-07-27  7:40   ` sashiko-bot
2026-07-27  7:27 ` [PATCH v3 2/2] ARM: dts: aspeed-g6: add pcie-kcs4 Grégoire Layet
2026-07-27  7:42   ` sashiko-bot [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=20260727074240.B59651F000E9@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=gregoire.layet@9elements.com \
    --cc=robh@kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    /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