[PATCH] arm64/sysreg: Correct the values for GICv4.1
Marc Zyngier
maz at kernel.org
Fri Jul 19 00:55:37 PDT 2024
On Thu, 18 Jul 2024 22:55:32 +0100,
Raghavendra Rao Ananta <rananta at google.com> wrote:
>
> Currently, sysreg has value as 0b0010 for the presence of GICv4.1 in
> ID_PFR1_EL1 and ID_AA64PFR0_EL1, instead of 0b0011 as per ARM ARM.
> Hence, correct them to reflect ARM ARM.
>
> Signed-off-by: Raghavendra Rao Ananta <rananta at google.com>
> ---
> arch/arm64/tools/sysreg | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/arch/arm64/tools/sysreg b/arch/arm64/tools/sysreg
> index a4c1dd4741a47..7ceaa1e0b4bc2 100644
> --- a/arch/arm64/tools/sysreg
> +++ b/arch/arm64/tools/sysreg
> @@ -149,7 +149,7 @@ Res0 63:32
> UnsignedEnum 31:28 GIC
> 0b0000 NI
> 0b0001 GICv3
> - 0b0010 GICv4p1
> + 0b0011 GICv4p1
> EndEnum
> UnsignedEnum 27:24 Virt_frac
> 0b0000 NI
> @@ -903,7 +903,7 @@ EndEnum
> UnsignedEnum 27:24 GIC
> 0b0000 NI
> 0b0001 IMP
> - 0b0010 V4P1
> + 0b0011 V4P1
I wonder why we have different naming schemes for the same feature...
> EndEnum
> SignedEnum 23:20 AdvSIMD
> 0b0000 IMP
>
Yup, this looks correct and checks out against revision H.b of the GICv3
spec, revision K.a of the ARM ARM, and even I.a (which the original
patches were referencing).
Once more, it shows that these dumps should be automatically generated
from the XML instead of (creatively) hand-written.
Reviewed-by: Marc Zyngier <maz at kernel.org>
M.
--
Without deviation from the norm, progress is not possible.
More information about the linux-arm-kernel
mailing list