All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: Frank.Li@oss.nxp.com
Cc: Frank.Li@kernel.org, robh@kernel.org, conor+dt@kernel.org,
	devicetree@vger.kernel.org, imx@lists.linux.dev
Subject: Re: [PATCH 07/11] ARM: dts: lpc: Remove NOMMU platform support
Date: Fri, 19 Jun 2026 15:50:56 +0000	[thread overview]
Message-ID: <20260619155057.06AA31F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260619-dts_cleanup_arm_mcore-v1-7-0101795a2662@nxp.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [High] Unintended removal of the MMU-capable LPC32xx platform under the false premise of removing NOMMU support, along with an inaccurate commit message.
--

commit d19b47e78b74813c8413198ab7ec32784181d8d8
Author: Frank Li <Frank.Li@nxp.com>
Subject: ARM: dts: lpc: Remove NOMMU platform support

This commit removes the arch/arm/boot/dts/nxp/lpc directory, stating the
intention is to remove unused NOMMU platform support. It drops the build
targets for LPC platforms to simplify the codebase.

>     ARM: dts: lpc: Remove NOMMU platform support
>     
>     Commercial users and hardware vendors migrated to Zephyr or other RTOS
>     solutions years ago, leaving the NOMMU platform support effectively
>     unused and unmaintained.
>     
>     Remove the obsolete support to reduce maintenance burden and simplify the
>     i.MX platform code.

[Severity: High]
Does this commit unintentionally remove the MMU-capable LPC32xx platform?
While the LPC18xx and LPC43xx series are Cortex-M NOMMU parts, the LPC32xx
series uses an ARM926EJ-S processor, which features a full MMU and runs a
standard Linux kernel.

This mistake appears to cascade through the rest of the patch series, where
mach-lpc32xx is also deleted under the same 'NOMMU' premise.

Also, this isn't a bug, but there appears to be a copy-paste error in the
commit message where it mentions simplifying the "i.MX platform code" instead
of LPC.

> diff --git a/arch/arm/boot/dts/nxp/lpc/Makefile b/arch/arm/boot/dts/nxp/lpc/Makefile
> deleted file mode 100644
> index 56b9a0ebb9179..0000000000000
> --- a/arch/arm/boot/dts/nxp/lpc/Makefile
> +++ /dev/null
> @@ -1,9 +0,0 @@
> -# SPDX-License-Identifier: GPL-2.0
> -dtb-$(CONFIG_ARCH_LPC18XX) += \
> -	lpc4337-ciaa.dtb \
> -	lpc4350-hitex-eval.dtb \
> -	lpc4357-ea4357-devkit.dtb \
> -	lpc4357-myd-lpc4357.dtb
> -dtb-$(CONFIG_ARCH_LPC32XX) += \
> -	lpc3250-ea3250.dtb \
> -	lpc3250-phy3250.dtb

[Severity: High]
Does the removal of these targets improperly disable the LPC32XX platform,
which relies on an MMU-capable core?

> diff --git a/arch/arm/boot/dts/nxp/lpc/lpc32xx.dtsi b/arch/arm/boot/dts/nxp/lpc/lpc32xx.dtsi
> deleted file mode 100644
> index e94df78def18a..0000000000000
> --- a/arch/arm/boot/dts/nxp/lpc/lpc32xx.dtsi
> +++ /dev/null
> @@ -1,540 +0,0 @@
[ ... ]
> -	cpus {
> -		#address-cells = <1>;
> -		#size-cells = <0>;
> -
> -		cpu@0 {
> -			compatible = "arm,arm926ej-s";
> -			device_type = "cpu";
> -			reg = <0x0>;
> -		};
> -	};

[Severity: High]
Since this node defines cpu@0 as an ARM926EJ-S, a core that features a full
MMU, does this contradict the commit's justification for removing this
platform as 'NOMMU'?

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260619-dts_cleanup_arm_mcore-v1-0-0101795a2662@nxp.com?part=7

  reply	other threads:[~2026-06-19 15:50 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-19 15:40 [PATCH 00/11] ARM: NXP: Drop NOMMU platform support Frank.Li
2026-06-19 15:40 ` [PATCH 01/11] ARM: dts: vf610m4: Remove " Frank.Li
2026-06-19 15:52   ` sashiko-bot
2026-06-19 15:40 ` [PATCH 02/11] ARM: dts: imxrt1050: " Frank.Li
2026-06-19 15:41 ` [PATCH 03/11] ARM: imx: " Frank.Li
2026-06-19 15:41 ` [PATCH 04/11] clk: imx: imxrt1050: " Frank.Li
2026-06-19 15:54   ` sashiko-bot
2026-06-19 15:41 ` [PATCH 05/11] pinctrl: freescale: IMXRT: " Frank.Li
2026-06-19 15:41 ` [PATCH 06/11] ARM: imxrt_defconfig: " Frank.Li
2026-06-19 15:55   ` sashiko-bot
2026-06-19 15:41 ` [PATCH 07/11] ARM: dts: lpc: " Frank.Li
2026-06-19 15:50   ` sashiko-bot [this message]
2026-06-19 15:41 ` [PATCH 08/11] ARM: mach-lpc: " Frank.Li
2026-06-19 16:00   ` sashiko-bot
2026-06-19 15:41 ` [PATCH 09/11] ARM: configs: lpc*: " Frank.Li
2026-06-19 15:53   ` sashiko-bot
2026-06-19 15:41 ` [PATCH 10/11] clk: nxp: lpc: " Frank.Li
2026-06-19 15:58   ` sashiko-bot
2026-06-19 15:41 ` [PATCH 11/11] pinctrl: " Frank.Li
2026-06-19 16:07 ` [PATCH 00/11] ARM: NXP: Drop " Vladimir Zapolskiy
2026-06-19 19:17   ` Arnd Bergmann

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=20260619155057.06AA31F000E9@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=Frank.Li@kernel.org \
    --cc=Frank.Li@oss.nxp.com \
    --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 \
    /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.