On 03/07/26 9:45 AM, Linu Cherian wrote:

Hi Suzuki,

On Fri, Jul 03, 2026 at 08:47:01AM +0530, Linu Cherian wrote:

quoted

Hi Suzuki,

On Wed, Jul 01, 2026 at 11:11:35AM +0100, Suzuki K Poulose wrote:

quoted

On 01/07/2026 10:41, Linu Cherian wrote:

quoted

Patches 1 and 2 introduces BBML3 cpu feature
Patches 3, 4 and 5 adds more cpus to the BBML3 support list,
	which dont advertise themselves through the standard
	MMFR2_ID registers.

Linu Cherian (5):
   arm64: cpufeature: Add BBML3
   arm64: cpufeature: Detect BBML3 based on MMFR2 ID

quoted

   arm64: cputype: Add Cortex-A520AE definitions
   arm64: cputype: Add C1-Nano definitions
   arm64: cpufeature: Extend bbml3 support list

If you could move the last 3 patches to the top, would be easier
for people to back port the "enable" BBLM3 for those CPUs, without
the renaming conflicts.

IMHO, if we change the order, "arm64: cpufeature: Extend bbml3 support list"
title need to be tweaked and might not go well with this BBML3 support series.
Also, backporting issue wouldnt be a problem if the whole series is
backported and not just 3 patches in isolation ?

After looking further on this, i definitely agree that moving those patches up has an
advantage, w.r.t avoiding dependency on other patches.

A possible patch order could be

  arm64/tools/sysreg: Update ID_AA64MMFR2_EL1
  arm64/cputype: Add Cortex-A520AE definitions
  arm64/cputype: Add C1-Nano definitions
  arm64/cpufeature: Extend supports_bbml2_noabort_list
  arm64/cpufeature: Add BBML3
  arm64/cpufeature: Detect BBML3 based on MMFR2 ID