From: sashiko-bot@kernel.org
To: "Arnd Bergmann" <arnd@kernel.org>
Cc: conor+dt@kernel.org, devicetree@vger.kernel.org,
imx@lists.linux.dev, Frank.Li@kernel.org, robh@kernel.org
Subject: Re: [PATCH 10/13] ARM: stm32: remove stm32f4/f7/h7 MCU support
Date: Tue, 08 Sep 2026 15:43:46 +0000 [thread overview]
Message-ID: <20260908154346.CDA0D1F00A3A@smtp.kernel.org> (raw)
In-Reply-To: <20260908152808.3928630-11-arnd@kernel.org>
Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
- [Medium] Incomplete removal of STM32 MCU platform leaves orphaned drivers and dangling Kconfig references
- [Low] Grammatical typo in documentation update
--
commit b3d9699b653730bdc87f076ae9ec5792bb7764a3
Author: Arnd Bergmann <arnd@arndb.de>
ARM: stm32: remove stm32f4/f7/h7 MCU support
The stm32 platform started out as a Cortex-M based microcontoller
platform in 2007, with a few of the older products gaining Linux kernel
support in 2016. These days, the only relevant chips for Linux are the
stm32mp1 (Cortex-A7) and stm32mp2 (Cortex-A35) product lines, with the
microcontrollers running smaller RTOSs on new products.
The microcontrollers were marked as deprecated in the linux-7.3LTS
release, which will remain supported for a few more years and
is expected to be sufficient for any of the remaining original users.
Remove the MCU support now, leaving only the stm32mp SoCs in the platform.
> diff --git a/Documentation/arch/arm/stm32/overview.rst b/Documentation/arch/arm/stm32/overview.rst
> index 85cfc84107983..b63aa875cb485 100644
> --- a/Documentation/arch/arm/stm32/overview.rst
> +++ b/Documentation/arch/arm/stm32/overview.rst
> @@ -5,15 +5,13 @@ STM32 ARM Linux Overview
> Introduction
> ------------
>
> -The STMicroelectronics STM32 family of Cortex-A microprocessors (MPUs) and
> -Cortex-M microcontrollers (MCUs) are supported by the 'STM32' platform of
> -ARM Linux.
> +The STMicroelectronics STM32 family of Cortex-A microprocessors (MPUs) is
> +supported by the 'STM32' platform of ARM Linux, support for the Cortex-M
> +based MCUs is has been removed.
[Severity: Low]
Is there a grammatical typo here? Should it be "has been removed" instead of
"is has been removed"?
[ ... ]
> diff --git a/arch/arm/mach-stm32/Kconfig b/arch/arm/mach-stm32/Kconfig
> index 4ac3384e397aa..6ca8507f94512 100644
> --- a/arch/arm/mach-stm32/Kconfig
> +++ b/arch/arm/mach-stm32/Kconfig
> @@ -1,17 +1,15 @@
> # SPDX-License-Identifier: GPL-2.0-only
> menuconfig ARCH_STM32
> bool "STMicroelectronics STM32 family"
> - depends on ARM_SINGLE_ARMV7M || ARCH_MULTI_V7
> - select ARMV7M_SYSTICK if ARM_SINGLE_ARMV7M
> - select HAVE_ARM_ARCH_TIMER if ARCH_MULTI_V7
> - select ARM_GIC if ARCH_MULTI_V7
> - select ARM_PSCI if ARCH_MULTI_V7
> + depends on ARCH_MULTI_V7
> + select HAVE_ARM_ARCH_TIMER
> + select ARM_GIC
> + select ARM_PSCI
> select ARM_AMBA
> select ARCH_HAS_RESET_CONTROLLER
> select CLKSRC_STM32
> select PINCTRL
> select RESET_CONTROLLER
> - select STM32_EXTI if ARM_SINGLE_ARMV7M
[Severity: Medium]
This is a pre-existing issue, but does removing this selection of STM32_EXTI
permanently disable the irq-stm32-exti.c driver?
Looking at drivers/irqchip/Kconfig on line 485, STM32_EXTI is defined as an
invisible boolean config symbol. Without being selected here, the driver will
never be built. Could the corresponding driver and Kconfig entry be removed as
well?
> select STM32_FIREWALL
> help
> Support for STMicroelectronics STM32MP1 processors using Cortex-A7
> @@ -20,32 +18,6 @@ menuconfig ARCH_STM32
>
> if ARCH_STM32
>
> -if ARM_SINGLE_ARMV7M
> -
> -config MACH_STM32F429
> - bool "STMicroelectronics STM32F429 (DEPRECATED)"
> - default y
> -
> -config MACH_STM32F469
> - bool "STMicroelectronics STM32F469 (DEPRECATED)"
> - default y
> -
> -config MACH_STM32F746
> - bool "STMicroelectronics STM32F746 (DEPRECATED)"
> - default y
> -
> -config MACH_STM32F769
> - bool "STMicroelectronics STM32F769 (DEPRECATED)"
> - default y
> -
> -config MACH_STM32H743
> - bool "STMicroelectronics STM32H743 (DEPRECATED)"
> - default y
[Severity: Medium]
This isn't a bug introduced by this patch, but doesn't removing these MCU
and debug configs leave dangling references in other files?
For instance, in drivers/clk/Kconfig at line 442, COMMON_CLK_STM32F relies
on these now-undefined symbols:
def_bool COMMON_CLK && (MACH_STM32F429 || MACH_STM32F469 || MACH_STM32F746)
This silently disables the clock driver and leaves it as dead code. Similarly,
drivers/pinctrl/stm32/Kconfig on line 14 uses MACH_STM32F429 in its visibility
condition for PINCTRL_STM32F429. In arch/arm/include/debug/stm32.S on line 7,
the preprocessor directive checks for CONFIG_STM32F4_DEBUG_UART, which was
also removed in this patch.
Could these remaining orphaned drivers and dead references be cleaned up as
well?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260908152808.3928630-1-arnd@kernel.org?part=10
next prev parent reply other threads:[~2026-09-08 15:43 UTC|newest]
Thread overview: 103+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-08 15:27 [PATCH 00/13] ARM: deprecated platform removal Arnd Bergmann
2026-09-08 15:27 ` [PATCH 01/13] ARM: remove sa1100 platform Arnd Bergmann
2026-09-08 16:26 ` Guenter Roeck
2026-09-08 17:23 ` Linus Walleij
2026-09-08 19:39 ` Karl Mehltretter
2026-09-08 20:09 ` Arnd Bergmann
2026-09-08 20:36 ` Nicolas Pitre
2026-09-08 21:26 ` David Laight
2026-09-08 21:32 ` Arnd Bergmann
2026-09-09 12:38 ` Alexandre Belloni
2026-09-08 15:27 ` [PATCH 02/13] ARM: remove footbridge Arnd Bergmann
2026-09-08 15:55 ` sashiko-bot
2026-09-08 17:57 ` Arnd Bergmann
2026-09-08 17:27 ` Linus Walleij
2026-09-09 15:09 ` Ralph Siemsen
2026-09-08 15:27 ` [PATCH 03/13] ARM: remove riscpc Arnd Bergmann
2026-09-08 15:52 ` sashiko-bot
2026-09-08 16:10 ` Arnd Bergmann
2026-09-09 8:04 ` Thomas Zimmermann
2026-09-09 16:42 ` Bart Van Assche
2026-09-09 20:09 ` Arnd Bergmann
2026-09-11 3:44 ` Ethan Nelson-Moore
2026-09-11 9:07 ` Linus Walleij
2026-09-11 13:25 ` Bart Van Assche
2026-09-11 13:37 ` Linus Walleij
2026-09-13 9:43 ` Arnd Bergmann
2026-09-11 14:38 ` Daniel Palmer
2026-09-11 18:14 ` Linus Walleij
2026-09-12 1:29 ` Daniel Palmer
2026-09-13 18:13 ` Linus Walleij
2026-09-11 18:42 ` Karl Mehltretter
2026-09-12 2:08 ` Ethan Nelson-Moore
2026-09-12 3:59 ` Ethan Nelson-Moore
2026-09-08 15:27 ` [PATCH 04/13] ARM: remove legacy pxa board files Arnd Bergmann
2026-09-08 16:01 ` sashiko-bot
2026-09-08 18:06 ` Arnd Bergmann
2026-09-08 17:30 ` Linus Walleij
2026-09-08 18:32 ` Daniel Mack
2026-09-08 15:27 ` [PATCH 05/13] ARM: orion/dove/mv78xx0: remove all " Arnd Bergmann
2026-09-08 15:34 ` Mark Brown
2026-09-08 16:11 ` sashiko-bot
2026-09-08 18:21 ` Arnd Bergmann
2026-09-09 12:42 ` [PATCH 05.2/13] ARM: orion5x: fold plat-orion/pcie.c and hw_pci into pci.c Arnd Bergmann
2026-09-08 16:12 ` [PATCH 05/13] ARM: orion/dove/mv78xx0: remove all board files Ulf Hansson
2026-09-08 16:18 ` Andrew Lunn
2026-09-08 17:33 ` Linus Walleij
2026-09-08 20:14 ` Niklas Cassel
2026-09-09 12:54 ` Gregory CLEMENT
2026-09-11 10:22 ` Daniel Lezcano
2026-09-08 15:27 ` [PATCH 06/13] ARM: omap2: remove omap24xx support Arnd Bergmann
2026-09-08 17:18 ` Aaro Koskinen
2026-09-08 17:35 ` Linus Walleij
2026-09-08 19:21 ` Karl Mehltretter
2026-09-08 19:42 ` Arnd Bergmann
2026-09-09 8:06 ` Thomas Zimmermann
2026-09-08 15:27 ` [PATCH 07/13] ARM: imx: remove i.MX31 SoC support Arnd Bergmann
2026-09-08 16:05 ` sashiko-bot
2026-09-08 18:01 ` Arnd Bergmann
2026-09-09 8:24 ` Vladimir Zapolskiy
2026-09-09 8:26 ` Daniel Baluta
2026-09-10 15:11 ` Frank Li
2026-09-08 15:27 ` [PATCH 08/13] ARM: imx: remove nommu support Arnd Bergmann
2026-09-08 15:43 ` sashiko-bot
2026-09-09 20:17 ` Fabio Estevam
2026-09-09 20:21 ` Fabio Estevam
2026-09-10 13:08 ` Jesse T
2026-09-10 16:08 ` Giulio Benetti
2026-09-10 15:14 ` Frank Li
2026-09-08 15:27 ` [PATCH 09/13] ARM: lpc18xx: remove entire platform Arnd Bergmann
2026-09-08 15:41 ` sashiko-bot
2026-09-08 15:43 ` Arnd Bergmann
2026-09-08 17:36 ` Linus Walleij
2026-09-09 8:28 ` Vladimir Zapolskiy
2026-09-08 15:28 ` [PATCH 10/13] ARM: stm32: remove stm32f4/f7/h7 MCU support Arnd Bergmann
2026-09-08 15:43 ` sashiko-bot [this message]
2026-09-08 15:54 ` Arnd Bergmann
2026-09-08 17:36 ` Linus Walleij
2026-09-11 15:46 ` Alexandre TORGUE
2026-09-08 15:28 ` [PATCH 11/13] ARM: versatile: remove mps2 support Arnd Bergmann
2026-09-08 15:41 ` Vladimir Murzin
2026-09-08 15:51 ` sashiko-bot
2026-09-08 17:37 ` Linus Walleij
2026-09-08 19:49 ` Sudeep Holla
2026-09-08 19:51 ` Arnd Bergmann
2026-09-08 19:58 ` Sudeep Holla
2026-09-08 19:54 ` Sudeep Holla
2026-09-08 15:28 ` [PATCH 12/13] ARM: at91: remove samv7 support Arnd Bergmann
2026-09-08 15:55 ` sashiko-bot
2026-09-08 16:40 ` Arnd Bergmann
2026-09-08 17:39 ` Linus Walleij
2026-09-08 21:09 ` Rob Herring
2026-09-08 21:30 ` Arnd Bergmann
2026-09-10 12:25 ` Nicolas Ferre
2026-09-10 12:23 ` Nicolas Ferre
2026-09-08 15:28 ` [PATCH 13/13] ARM: axxia: remove entire platform Arnd Bergmann
2026-09-08 15:55 ` sashiko-bot
2026-09-08 17:40 ` Linus Walleij
2026-09-08 18:23 ` Krzysztof Kozlowski
2026-09-08 20:02 ` Sverdlin, Alexander
2026-09-08 16:53 ` [PATCH 00/13] ARM: deprecated platform removal Randy Dunlap
2026-09-08 16:56 ` Randy Dunlap
2026-09-08 18:33 ` Arnd Bergmann
2026-09-08 18:39 ` Randy Dunlap
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=20260908154346.CDA0D1F00A3A@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=Frank.Li@kernel.org \
--cc=arnd@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 \
/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