From: Vladimir Zapolskiy <vz@kernel.org>
To: Frank.Li@oss.nxp.com, Arnd Bergmann <arnd@arndb.de>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Stefan Agner <stefan@agner.ch>,
Fabio Estevam <festevam@gmail.com>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Russell King <linux@armlinux.org.uk>,
Abel Vesa <abelvesa@kernel.org>, Peng Fan <peng.fan@nxp.com>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
Brian Masney <bmasney@redhat.com>,
Dong Aisheng <aisheng.dong@nxp.com>, Jacky Bai <ping.bai@nxp.com>,
NXP S32 Linux Team <s32@nxp.com>,
Linus Walleij <linusw@kernel.org>,
Piotr Wojtaszczyk <piotr.wojtaszczyk@timesys.com>,
Kees Cook <kees@kernel.org>,
"Gustavo A. R. Silva" <gustavoars@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org, imx@lists.linux.dev,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-clk@vger.kernel.org, linux-gpio@vger.kernel.org,
linux-hardening@vger.kernel.org, Frank Li <Frank.Li@nxp.com>
Subject: Re: [PATCH 00/11] ARM: NXP: Drop NOMMU platform support
Date: Fri, 19 Jun 2026 19:07:59 +0300 [thread overview]
Message-ID: <7d946861-c3cb-4512-9d5f-9f4cb9b7ee8a@kernel.org> (raw)
In-Reply-To: <20260619-dts_cleanup_arm_mcore-v1-0-0101795a2662@nxp.com>
Hello Frank.
On 6/19/26 18:40, Frank.Li@oss.nxp.com wrote:
> 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
> Freescale/nxp platform code.
>
> Some driver code still be kept and may clean up later since it is possible
> reused by other SoC.
>
> Signed-off-by: Frank Li <Frank.Li@nxp.com>
This change is a bit too early to happen, I prefer to get it orchestrated
by Arnd. So, as for today I NAK the change for its NXP LPC part.
> ---
> Frank Li (11):
> ARM: dts: vf610m4: Remove NOMMU platform support
> ARM: dts: imxrt1050: Remove NOMMU platform support
> ARM: imx: Remove NOMMU platform support
> clk: imx: imxrt1050: Remove NOMMU platform support
> pinctrl: freescale: IMXRT: Remove NOMMU platform support
> ARM: imxrt_defconfig: Remove NOMMU platform support
> ARM: dts: lpc: Remove NOMMU platform support
> ARM: mach-lpc: Remove NOMMU platform support
> ARM: configs: lpc*: Remove NOMMU platform support
> clk: nxp: lpc: Remove NOMMU platform support
> pinctrl: nxp: lpc: Remove NOMMU platform support
>
> .../devicetree/bindings/pinctrl/fsl,imxrt1050.yaml | 79 -
> .../devicetree/bindings/pinctrl/fsl,imxrt1170.yaml | 77 -
> arch/arm/Kconfig | 12 -
> arch/arm/Makefile | 2 -
> arch/arm/boot/dts/nxp/Makefile | 1 -
> arch/arm/boot/dts/nxp/imx/Makefile | 2 -
> arch/arm/boot/dts/nxp/imx/imxrt1050-evk.dts | 72 -
> arch/arm/boot/dts/nxp/imx/imxrt1050-pinfunc.h | 993 ------------
> arch/arm/boot/dts/nxp/imx/imxrt1050.dtsi | 160 --
> arch/arm/boot/dts/nxp/imx/imxrt1170-pinfunc.h | 1561 -------------------
> arch/arm/boot/dts/nxp/lpc/Makefile | 9 -
> arch/arm/boot/dts/nxp/lpc/lpc18xx.dtsi | 543 -------
> arch/arm/boot/dts/nxp/lpc/lpc3250-ea3250.dts | 273 ----
> arch/arm/boot/dts/nxp/lpc/lpc3250-phy3250.dts | 236 ---
> arch/arm/boot/dts/nxp/lpc/lpc32xx.dtsi | 540 -------
NXP LPC32xx is ARMv5 and it has MMU, hence it's plainly out of scope of
the proposed "dropping NOMMU platform support".
--
Best wishes,
Vladimir
next prev parent reply other threads:[~2026-06-19 16:08 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
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 ` Vladimir Zapolskiy [this message]
2026-06-19 19:17 ` [PATCH 00/11] ARM: NXP: Drop " 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=7d946861-c3cb-4512-9d5f-9f4cb9b7ee8a@kernel.org \
--to=vz@kernel.org \
--cc=Frank.Li@nxp.com \
--cc=Frank.Li@oss.nxp.com \
--cc=abelvesa@kernel.org \
--cc=aisheng.dong@nxp.com \
--cc=arnd@arndb.de \
--cc=bmasney@redhat.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=gustavoars@kernel.org \
--cc=imx@lists.linux.dev \
--cc=kees@kernel.org \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mturquette@baylibre.com \
--cc=peng.fan@nxp.com \
--cc=ping.bai@nxp.com \
--cc=piotr.wojtaszczyk@timesys.com \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=s32@nxp.com \
--cc=sboyd@kernel.org \
--cc=stefan@agner.ch \
/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