From: Qingfang Deng <qingfang.deng@linux.dev>
To: Russell King <linux@armlinux.org.uk>,
Arnd Bergmann <arnd@arndb.de>, Linus Walleij <linusw@kernel.org>,
"Russell King (Oracle)" <rmk+kernel@armlinux.org.uk>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Andrew Morton <akpm@linux-foundation.org>,
"Lorenzo Stoakes (ARM)" <ljs@kernel.org>,
Thomas Weissschuh <thomas.weissschuh@linutronix.de>,
Thomas Gleixner <tglx@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Cc: Mark Rutland <mark.rutland@arm.com>,
Qingfang Deng <qingfang.deng@linux.dev>
Subject: [PATCH v2] ARM: errata: document Cortex-A9 from r2 as affected by erratum 754322
Date: Tue, 22 Sep 2026 09:52:03 +0800 [thread overview]
Message-ID: <20260922015205.253872-1-qingfang.deng@linux.dev> (raw)
The Cortex-A9 r4 Software Developers Errata Notice (ARM UAN 0009D),
section 2.3.3, lists erratum 754322 as open (unresolved) and affecting
all r2, r3 and r4 revisions. The Kconfig help text currently mentions
only r2 and r3.
Update the help text to include all revisions from r2p0 so that users
configuring Cortex-A9 r4 systems know that the workaround also applies
to them.
Link: https://documentation-service.arm.com/static/608118675e70d934bc69f143
Signed-off-by: Qingfang Deng <qingfang.deng@linux.dev>
---
v2:
Drop fixes tag, and mention that it affects all revisions from r2.
v1: https://lore.kernel.org/linux-arm-kernel/20260920032926.452884-1-qingfang.deng@linux.dev/
---
arch/arm/Kconfig | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/arm/Kconfig b/arch/arm/Kconfig
index 0cc289a7184a..ec0c6191161f 100644
--- a/arch/arm/Kconfig
+++ b/arch/arm/Kconfig
@@ -707,8 +707,8 @@ config ARM_ERRATA_754322
bool "ARM errata: possible faulty MMU translations following an ASID switch"
depends on CPU_V7
help
- This option enables the workaround for the 754322 Cortex-A9 (r2p*,
- r3p*) erratum. A speculative memory access may cause a page table walk
+ This option enables the workaround for the 754322 Cortex-A9 (r2p* and
+ later) erratum. A speculative memory access may cause a page table walk
which starts prior to an ASID switch but completes afterwards. This
can populate the micro-TLB with a stale entry which may be hit with
the new ASID. This workaround places two dsb instructions in the mm
--
2.43.0
reply other threads:[~2026-09-22 1:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20260922015205.253872-1-qingfang.deng@linux.dev \
--to=qingfang.deng@linux.dev \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=bigeasy@linutronix.de \
--cc=linusw@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=ljs@kernel.org \
--cc=mark.rutland@arm.com \
--cc=rmk+kernel@armlinux.org.uk \
--cc=tglx@kernel.org \
--cc=thomas.weissschuh@linutronix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox