From: Linu Cherian <linu.cherian@arm.com>
To: Mark Rutland <mark.rutland@arm.com>
Cc: 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>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 5/5] arm64: cpufeature: Extend bbml3 support list
Date: Fri, 3 Jul 2026 08:33:09 +0530 [thread overview]
Message-ID: <akcmbZHGMo_56Z2R@a079125.arm.com> (raw)
In-Reply-To: <akZBqNTTGXch6I9n@J2N7QTR9R3>
Hi Mark,
On Thu, Jul 02, 2026 at 11:47:04AM +0100, Mark Rutland wrote:
> On Wed, Jul 01, 2026 at 03:11:31PM +0530, Linu Cherian wrote:
> > Add below cpus to the midr list, which supports
> > BBML3 but don't advertise through MMFR2 ID.
> >
> > Cortex A520(AE)
> > Cortex A715
> > Cortex A720(AE)
> > Cortex A725
> > Neoverse N3
> > C1-Nano
> > C1-Pro
> > C1-Ultra
> > C1-Premium
> >
> > Signed-off-by: Linu Cherian <linu.cherian@arm.com>
> > ---
> > arch/arm64/kernel/cpufeature.c | 9 +++++++++
> > 1 file changed, 9 insertions(+)
> >
> > diff --git a/arch/arm64/kernel/cpufeature.c b/arch/arm64/kernel/cpufeature.c
> > index d754b1b7da77..9b806c1c60aa 100644
> > --- a/arch/arm64/kernel/cpufeature.c
> > +++ b/arch/arm64/kernel/cpufeature.c
> > @@ -2142,6 +2142,15 @@ bool cpu_supports_bbml3(void)
> > MIDR_ALL_VERSIONS(MIDR_NVIDIA_OLYMPUS),
> > MIDR_ALL_VERSIONS(MIDR_AMPERE1),
> > MIDR_ALL_VERSIONS(MIDR_AMPERE1A),
> > + MIDR_ALL_VERSIONS(MIDR_CORTEX_A520AE),
> > + MIDR_ALL_VERSIONS(MIDR_CORTEX_A715),
> > + MIDR_ALL_VERSIONS(MIDR_CORTEX_A720AE),
> > + MIDR_ALL_VERSIONS(MIDR_CORTEX_A725),
> > + MIDR_ALL_VERSIONS(MIDR_NEOVERSE_N3),
> > + MIDR_ALL_VERSIONS(MIDR_C1_NANO),
> > + MIDR_ALL_VERSIONS(MIDR_C1_PRO),
> > + MIDR_REV_RANGE(MIDR_C1_ULTRA, 1, 1, 0xf),
> > + MIDR_REV_RANGE(MIDR_C1_PREMIUM, 1, 1, 0xf),
>
> Why do these two have a range? The commit message didn't mention this.
C1 ultra and C1 Premium has BBM related errata until r1p0.
Will mention that in commit message.
Thanks,
Linu Cherian.
next prev parent reply other threads:[~2026-07-03 3:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-01 9:41 [PATCH 0/5] Add BBML3 cpu feature Linu Cherian
2026-07-01 9:41 ` [PATCH 1/5] arm64: cpufeature: Add BBML3 Linu Cherian
2026-07-01 9:41 ` [PATCH 2/5] arm64: cpufeature: Detect BBML3 based on MMFR2 ID Linu Cherian
2026-07-02 10:45 ` Mark Rutland
2026-07-03 3:06 ` Linu Cherian
2026-07-03 4:36 ` Anshuman Khandual
2026-07-01 9:41 ` [PATCH 3/5] arm64: cputype: Add Cortex-A520AE definitions Linu Cherian
2026-07-03 5:07 ` Anshuman Khandual
2026-07-01 9:41 ` [PATCH 4/5] arm64: cputype: Add C1-Nano definitions Linu Cherian
2026-07-03 5:10 ` Anshuman Khandual
2026-07-01 9:41 ` [PATCH 5/5] arm64: cpufeature: Extend bbml3 support list Linu Cherian
2026-07-02 10:47 ` Mark Rutland
2026-07-03 3:03 ` Linu Cherian [this message]
2026-07-01 10:11 ` [PATCH 0/5] Add BBML3 cpu feature Suzuki K Poulose
2026-07-03 3:16 ` Linu Cherian
2026-07-03 4:15 ` Linu Cherian
2026-07-03 4:42 ` 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=akcmbZHGMo_56Z2R@a079125.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