From: Daniel Schultz <d.schultz@phytec.de>
To: <trini@konsulko.com>, <kishon@ti.com>,
<alexander.sverdlin@siemens.com>, <s-vadapalli@ti.com>,
<c-vankar@ti.com>, <bb@ti.com>, <u-boot@lists.denx.de>
Cc: <upstream@lists.phytec.de>, Daniel Schultz <d.schultz@phytec.de>
Subject: [PATCH] arm: mach-k3: am625: Unlock MMR registers again
Date: Fri, 15 Aug 2025 09:02:40 -0700 [thread overview]
Message-ID: <20250815160240.3575140-1-d.schultz@phytec.de> (raw)
The watchdog requires to have the MCU ESM error source enabled to
trigger a system reboot. When booting HS-SE (security enforced)
devices, the MMR registers are locked again and all write commands
are simply ignored.
Unlock the MMR registers again to successfully enable the MCU ESM
source.
Signed-off-by: Daniel Schultz <d.schultz@phytec.de>
---
arch/arm/mach-k3/am62x/am625_init.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/arch/arm/mach-k3/am62x/am625_init.c b/arch/arm/mach-k3/am62x/am625_init.c
index a422919fab1..498bbe45b38 100644
--- a/arch/arm/mach-k3/am62x/am625_init.c
+++ b/arch/arm/mach-k3/am62x/am625_init.c
@@ -84,6 +84,9 @@ static void ctrl_mmr_unlock(void)
static __maybe_unused void enable_mcu_esm_reset(void)
{
+ /* CTRLMMR_MCU_RST registers are locked again on HS-SE devices */
+ mmr_unlock(MCU_CTRL_MMR0_BASE, 6);
+
/* Set CTRLMMR_MCU_RST_CTRL:MCU_ESM_ERROR_RST_EN_Z to '0' (low active) */
u32 stat = readl(CTRLMMR_MCU_RST_CTRL);
--
2.25.1
next reply other threads:[~2025-08-15 16:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-15 16:02 Daniel Schultz [this message]
2025-08-21 16:21 ` [PATCH] arm: mach-k3: am625: Unlock MMR registers again Sverdlin, Alexander
2025-09-10 11:50 ` Daniel Schultz
2025-09-10 12:08 ` bb
2025-09-10 12:27 ` Sverdlin, Alexander
2025-09-10 12:53 ` bb
2025-09-10 13:01 ` Sverdlin, Alexander
2025-09-10 13:26 ` bb
2025-09-10 14:06 ` Daniel Schultz
2026-01-12 3:04 ` [Upstream] " Wadim Egorov
2026-01-13 3:02 ` bb
2026-01-12 7:31 ` Sverdlin, Alexander
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=20250815160240.3575140-1-d.schultz@phytec.de \
--to=d.schultz@phytec.de \
--cc=alexander.sverdlin@siemens.com \
--cc=bb@ti.com \
--cc=c-vankar@ti.com \
--cc=kishon@ti.com \
--cc=s-vadapalli@ti.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=upstream@lists.phytec.de \
/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.