From: sashiko-bot@kernel.org
To: "Stefano Radaelli" <stefano.radaelli21@gmail.com>
Cc: robh@kernel.org, Frank.Li@kernel.org, imx@lists.linux.dev,
devicetree@vger.kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH v1 1/1] arm64: dts: freescale: imx95-var-dart: enable NETC block control
Date: Fri, 03 Jul 2026 15:00:45 +0000 [thread overview]
Message-ID: <20260703150045.971DB1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260703144922.231608-1-stefano.r@variscite.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [High] Missing dependency for `netc_blk_ctrl` causing a potential system hang on boot.
--
commit 14e353bd1da7516058662c0b4b79b720409b4211
Author: Stefano Radaelli <stefano.r@variscite.com>
arm64: dts: freescale: imx95-var-dart: enable NETC block control
This commit enables the NETC block control node on the DART-MX95 SoM,
which is necessary for the NETC Ethernet ports to function.
> diff --git a/arch/arm64/boot/dts/freescale/imx95-var-dart.dtsi b/arch/arm64/boot/dts/freescale/imx95-var-dart.dtsi
> index a20fadacaa6d8..7c29082a40c5b 100644
> --- a/arch/arm64/boot/dts/freescale/imx95-var-dart.dtsi
> +++ b/arch/arm64/boot/dts/freescale/imx95-var-dart.dtsi
> @@ -176,6 +176,10 @@ &mu7 {
> status = "okay";
> };
>
> +&netc_blk_ctrl {
> + status = "okay";
> +};
> +
[Severity: High]
Does missing the netcmix_blk_ctrl dependency here risk a system hang on boot?
The nxp,imx95-netc-blk-ctrl driver maps the netcmix memory block and writes
to it unconditionally during probe. Accessing this region safely requires
the IMX95_CLK_BUSNETCMIX bus clock to be enabled.
Since that clock is exclusively requested and managed by the
nxp,imx95-netcmix-blk-ctrl clock controller driver, leaving netcmix_blk_ctrl
disabled means the kernel won't enable the required bus clock.
If the bootloader leaves the clock off, this will crash with an SError /
asynchronous external abort during netc_blk_ctrl_probe(). Even if the
bootloader leaves it on, clk_disable_unused() might turn it off later,
crashing the system on any subsequent accesses.
Should netcmix_blk_ctrl be enabled alongside netc_blk_ctrl to satisfy this
hardware dependency?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260703144922.231608-1-stefano.r@variscite.com?part=1
prev parent reply other threads:[~2026-07-03 15:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-03 14:49 [PATCH v1 1/1] arm64: dts: freescale: imx95-var-dart: enable NETC block control Stefano Radaelli
2026-07-03 15:00 ` 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=20260703150045.971DB1F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=Frank.Li@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=imx@lists.linux.dev \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=stefano.radaelli21@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox