From: Denis Benato <benato.denis96@gmail.com>
To: Russell King <linux@armlinux.org.uk>
Cc: Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
linux-arm-kernel@lists.infradead.org, imx@lists.linux.dev,
linux-kernel@vger.kernel.org,
Denis Benato <benato.denis96@gmail.com>
Subject: [PATCH 0/3] arm: fix imx_* defconfig
Date: Sat, 10 May 2025 03:18:03 +0200 [thread overview]
Message-ID: <20250510011806.13470-1-benato.denis96@gmail.com> (raw)
Compiling the kernel using affected imx defconfigs lead
to a hard CPU crash that reaches a state where each register,
including PC ends up in 0xDEADBEEF.
That is because the SoC support depending on CONFIG_ARCH_MXC
gets disabled since CONFIG_ARCH_NXP is not defined while
said feature depends on it.
The default arm defconfig is unaffected as it defines
CONFIG_ARCH_NXP=y correctly as excepted.
These patches solve the crash causing my confusion:
https://lore.kernel.org/all/c84e8246-8104-4409-8d95-389d61bc07af@gmail.com
Denis Benato (3):
ARM: imx_v4_v5_defconfig: define CONFIG_ARCH_NXP
ARM: imx_v6_v7_defconfig: define CONFIG_ARCH_NXP
ARM: imxrt_defconfig: define CONFIG_ARCH_NXP
arch/arm/configs/imx_v4_v5_defconfig | 1 +
arch/arm/configs/imx_v6_v7_defconfig | 1 +
arch/arm/configs/imxrt_defconfig | 1 +
3 files changed, 3 insertions(+)
--
2.49.0
next reply other threads:[~2025-05-10 1:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-10 1:18 Denis Benato [this message]
2025-05-10 1:18 ` [PATCH 1/3] ARM: imx_v4_v5_defconfig: define CONFIG_ARCH_NXP Denis Benato
2025-05-10 17:57 ` Fabio Estevam
2025-05-10 1:18 ` [PATCH 2/3] ARM: imx_v6_v7_defconfig: " Denis Benato
2025-05-10 1:18 ` [PATCH 3/3] ARM: imxrt_defconfig: " Denis Benato
2025-05-12 6:03 ` [PATCH 0/3] arm: fix imx_* defconfig Sascha Hauer
2025-05-12 18:09 ` Denis Benato
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=20250510011806.13470-1-benato.denis96@gmail.com \
--to=benato.denis96@gmail.com \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
/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
all inboxes | Powered by JetHome®