From: Linu Cherian <linu.cherian@arm.com>
To: Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Ryan Roberts <ryan.roberts@arm.com>,
Kevin Brodsky <kevin.brodsky@arm.com>,
Anshuman Khandual <anshuman.khandual@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Mark Rutland <mark.rutland@arm.com>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Linu Cherian <linu.cherian@arm.com>
Subject: [PATCH v2 0/6] Add BBML3 cpu feature
Date: Wed, 8 Jul 2026 20:13:25 +0530 [thread overview]
Message-ID: <20260708144331.679816-1-linu.cherian@arm.com> (raw)
- Patches 1, 2 and 3 adds more cpus to the bbml2_noabort
support list. bbml2_noabort would eventually gets renamed
to bbml3 in a subsequent patch as they are functionally
equivalent.
- Patches 4, 5 & 6 introduces BBML3 cpu feature
Changelog from v1:
* Patches associated with adding cpus to BBML2_NOABORT,
support list, were kept at bottom in v1 is now moved
up in this version, for ease of backporting.
* Adding BBM_3 definition in sysreg moved into a separate patch
* MMFR2_ID check for BBM_3 has been changed from == BBM_3 to
>= BBM_3, so that BBML3 cpu feature gets enabled for BBM_4 as well.
* For feature detection, MMFR2_ID check comes first followed by
midr check for code readability
* Errata details for C1-Ultra and C1-Premium added to commit message
Linu Cherian (6):
arm64: cputype: Add Cortex-A520AE definitions
arm64: cputype: Add C1-Nano definitions
arm64: cpufeature: Extend bbml2_noabort support list
arm64: sysreg: Add BBM_3
arm64: cpufeature: Add BBML3
arm64: cpufeature: Detect BBML3 based on MMFR2 ID
arch/arm64/include/asm/cpufeature.h | 6 ++--
arch/arm64/include/asm/cputype.h | 4 +++
arch/arm64/kernel/cpufeature.c | 54 ++++++++++++++---------------
arch/arm64/mm/contpte.c | 21 +++++------
arch/arm64/mm/mmu.c | 52 +++++++++++++--------------
arch/arm64/mm/proc.S | 4 +--
arch/arm64/tools/cpucaps | 2 +-
arch/arm64/tools/sysreg | 1 +
8 files changed, 71 insertions(+), 73 deletions(-)
--
2.43.0
next reply other threads:[~2026-07-08 14:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-08 14:43 Linu Cherian [this message]
2026-07-08 14:43 ` [PATCH v2 1/6] arm64: cputype: Add Cortex-A520AE definitions Linu Cherian
2026-07-10 6:37 ` Anshuman Khandual
2026-07-08 14:43 ` [PATCH v2 2/6] arm64: cputype: Add C1-Nano definitions Linu Cherian
2026-07-10 6:37 ` Anshuman Khandual
2026-07-08 14:43 ` [PATCH v2 3/6] arm64: cpufeature: Extend bbml2_noabort support list Linu Cherian
2026-07-08 14:53 ` Suzuki K Poulose
2026-07-10 6:24 ` Anshuman Khandual
2026-07-08 14:43 ` [PATCH v2 4/6] arm64: sysreg: Add BBM_3 Linu Cherian
2026-07-10 6:46 ` Anshuman Khandual
2026-07-08 14:43 ` [PATCH v2 5/6] arm64: cpufeature: Add BBML3 Linu Cherian
2026-07-10 7:00 ` Anshuman Khandual
2026-07-08 14:43 ` [PATCH v2 6/6] arm64: cpufeature: Detect BBML3 based on MMFR2 ID Linu Cherian
2026-07-10 7:11 ` Anshuman Khandual
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=20260708144331.679816-1-linu.cherian@arm.com \
--to=linu.cherian@arm.com \
--cc=anshuman.khandual@arm.com \
--cc=catalin.marinas@arm.com \
--cc=kevin.brodsky@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=ryan.roberts@arm.com \
--cc=suzuki.poulose@arm.com \
--cc=will@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