Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Adrian Ng Ho Yin" <adrian.ho.yin.ng@altera.com>
Cc: devicetree@vger.kernel.org, conor+dt@kernel.org, robh@kernel.org
Subject: Re: [PATCH] arm64: dts: socfpga: agilex5: enable i3c0 and i3c1
Date: Tue, 26 May 2026 07:22:03 +0000	[thread overview]
Message-ID: <20260526072204.1A5881F000E9@smtp.kernel.org> (raw)
In-Reply-To: <219d67474c90843f4768cba2598e79cfafcc1ac2.1779778817.git.adrian.ho.yin.ng@altera.com>

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

Pre-existing issues:
- [High] The i3c0 and i3c1 nodes are enabled but lack the required `resets` and `reset-names` properties, structurally exposing the system to initialization failures or kernel panics.
--

commit f5368d005c11d976c73173b7cd6fde413ccc26cb
Author: Adrian Ng Ho Yin <adrian.ho.yin.ng@altera.com>

arm64: dts: socfpga: agilex5: enable i3c0 and i3c1

This commit enables the i3c0 and i3c1 nodes for the Agilex5 development kit
by setting their status to okay.

> diff --git a/arch/arm64/boot/dts/intel/socfpga_agilex5_socdk.dts b/arch/arm64/boot/dts/intel/socfpga_agilex5_socdk.dts
> index 262bb3e8e5c72..7f6fab5068676 100644
> --- a/arch/arm64/boot/dts/intel/socfpga_agilex5_socdk.dts
> +++ b/arch/arm64/boot/dts/intel/socfpga_agilex5_socdk.dts
[ ... ]
> @@ -61,6 +61,14 @@ &gpio1 {
>  	status = "okay";
>  };
>  
> +&i3c0 {
> +	status = "okay";
> +};
> +
> +&i3c1 {
> +	status = "okay";
> +};

[Severity: High]
This is a pre-existing issue, but the i3c0 and i3c1 nodes defined in the
base socfpga_agilex5.dtsi file lack the resets and reset-names properties.

By enabling the nodes here, does this expose the system to initialization
failures or a bus hang during probe?

The Synopsys DesignWare I3C driver requests an optional reset control named
core_rst via devm_reset_control_get_optional_exclusive_deasserted(). If the
bootloader leaves these peripherals in reset, the driver will receive NULL
for the reset control and proceed without deasserting the reset line, which
can cause an AXI bus hang when accessing registers.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/219d67474c90843f4768cba2598e79cfafcc1ac2.1779778817.git.adrian.ho.yin.ng@altera.com?part=1

  reply	other threads:[~2026-05-26  7:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-26  7:03 [PATCH] arm64: dts: socfpga: agilex5: enable i3c0 and i3c1 Adrian Ng Ho Yin
2026-05-26  7:22 ` sashiko-bot [this message]
2026-05-27  3:53 ` Dinh Nguyen

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=20260526072204.1A5881F000E9@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=adrian.ho.yin.ng@altera.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --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