From: Will Deacon <will@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
Jonathan Corbet <corbet@lwn.net>, Marc Zyngier <maz@kernel.org>,
Oliver Upton <oliver.upton@linux.dev>,
Joey Gouly <joey.gouly@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Shuah Khan <shuah@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
kvmarm@lists.linux.dev, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH v4 5/9] arm64/sysreg: Update ID_AA64SMFR0_EL1 to DDI0601 2024-09
Date: Tue, 7 Jan 2025 15:13:24 +0000 [thread overview]
Message-ID: <20250107151323.GA7368@willie-the-truck> (raw)
In-Reply-To: <20241211-arm64-2024-dpisa-v4-5-0fd403876df2@kernel.org>
On Wed, Dec 11, 2024 at 01:02:50AM +0000, Mark Brown wrote:
> DDI0601 2024-09 introduces SME 2.2 as well as a few new optional features,
> update sysreg to reflect the changes in ID_AA64SMFR0_EL1 enumerating them.
>
> Signed-off-by: Mark Brown <broonie@kernel.org>
> ---
> arch/arm64/tools/sysreg | 32 +++++++++++++++++++++++++++++++-
> 1 file changed, 31 insertions(+), 1 deletion(-)
>
> diff --git a/arch/arm64/tools/sysreg b/arch/arm64/tools/sysreg
> index c792bd3b0afbb5fb7e438a4d760d9f2d15621eee..d78b12c59658b480739ae797f5ea2c2f14d8d765 100644
> --- a/arch/arm64/tools/sysreg
> +++ b/arch/arm64/tools/sysreg
> @@ -1105,6 +1105,7 @@ UnsignedEnum 59:56 SMEver
> 0b0000 SME
> 0b0001 SME2
> 0b0010 SME2p1
> + 0b0011 SME2p2
> 0b0000 IMP
> EndEnum
> UnsignedEnum 55:52 I16I64
> @@ -1169,7 +1170,36 @@ UnsignedEnum 28 SF8DP2
> 0b0 NI
> 0b1 IMP
> EndEnum
> -Res0 27:0
> +UnsignedEnum 27 SF8MM8
> + 0b0 NI
> + 0b1 IMP
> +EndEnum
> +UnsignedEnum 26 SF8MM4
> + 0b0 NI
> + 0b1 IMP
> +EndEnum
afaict, bits 27 and 26 are still RES0 in all the documentation I can
find...
Will
next prev parent reply other threads:[~2025-01-07 15:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-11 1:02 [PATCH v4 0/9] arm64: Support 2024 dpISA extensions Mark Brown
2024-12-11 1:02 ` [PATCH v4 1/9] arm64/sysreg: Update ID_AA64PFR2_EL1 to DDI0601 2024-09 Mark Brown
2024-12-11 1:02 ` [PATCH v4 2/9] arm64/sysreg: Update ID_AA64ISAR3_EL1 " Mark Brown
2024-12-11 1:02 ` [PATCH v4 3/9] arm64/sysreg: Update ID_AA64FPFR0_EL1 " Mark Brown
2024-12-11 1:02 ` [PATCH v4 4/9] arm64/sysreg: Update ID_AA64ZFR0_EL1 " Mark Brown
2024-12-11 1:02 ` [PATCH v4 5/9] arm64/sysreg: Update ID_AA64SMFR0_EL1 " Mark Brown
2025-01-07 15:13 ` Will Deacon [this message]
2025-01-07 15:26 ` Mark Brown
2025-01-07 15:39 ` Will Deacon
2024-12-11 1:02 ` [PATCH v4 6/9] arm64/sysreg: Update ID_AA64ISAR2_EL1 " Mark Brown
2024-12-11 1:02 ` [PATCH v4 7/9] arm64/hwcap: Describe 2024 dpISA extensions to userspace Mark Brown
2024-12-11 1:02 ` [PATCH v4 8/9] KVM: arm64: Allow control of dpISA extensions in ID_AA64ISAR3_EL1 Mark Brown
2025-01-07 17:16 ` Marc Zyngier
2024-12-11 1:02 ` [PATCH v4 9/9] kselftest/arm64: Add 2024 dpISA extensions to hwcap test Mark Brown
2025-01-07 16:42 ` [PATCH v4 0/9] arm64: Support 2024 dpISA extensions Will Deacon
2025-01-07 17:18 ` Marc Zyngier
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=20250107151323.GA7368@willie-the-truck \
--to=will@kernel.org \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=corbet@lwn.net \
--cc=joey.gouly@arm.com \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=maz@kernel.org \
--cc=oliver.upton@linux.dev \
--cc=shuah@kernel.org \
--cc=suzuki.poulose@arm.com \
/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