From: Mark Brown <broonie@kernel.org>
To: Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>
Cc: Fuad Tabba <tabba@google.com>, Joey Gouly <joey.gouly@arm.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Mark Brown <broonie@kernel.org>
Subject: [PATCH 11/13] arm64/sysreg: Update HCRX_EL2 definition for DDI0601 2023-09
Date: Sat, 09 Dec 2023 01:02:57 +0000 [thread overview]
Message-ID: <20231209-b4-arm64-sysreg-additions-v1-11-45284e538474@kernel.org> (raw)
In-Reply-To: <20231209-b4-arm64-sysreg-additions-v1-0-45284e538474@kernel.org>
DDI0601 2023-09 defines new fields in HCRX_EL2 controlling access to new
system registers, update our definition of HCRX_EL2 to reflect this.
Signed-off-by: Mark Brown <broonie@kernel.org>
---
arch/arm64/tools/sysreg | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/arch/arm64/tools/sysreg b/arch/arm64/tools/sysreg
index 4137179e7570..1acec8f5c37d 100644
--- a/arch/arm64/tools/sysreg
+++ b/arch/arm64/tools/sysreg
@@ -2458,7 +2458,9 @@ Fields ZCR_ELx
EndSysreg
Sysreg HCRX_EL2 3 4 1 2 2
-Res0 63:23
+Res0 63:25
+Field 24 PACMEn
+Field 23 EnFPM
Field 22 GCSEn
Field 21 EnIDCP128
Field 20 EnSDERR
--
2.39.2
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-12-09 1:04 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-09 1:02 [PATCH 00/13] arm64/sysreg: System register updates from the 2023-09 XML release broonie
2023-12-09 1:02 ` [PATCH 01/13] arm64/sysreg: Update HFGITR_EL2 definiton to DDI0601 2023-09 broonie
2023-12-09 1:02 ` [PATCH 02/13] arm64/sysreg: Add definition for HAFGRTR_EL2 broonie
2023-12-09 1:02 ` [PATCH 03/13] arm64/sysreg: add system register POR_EL{0,1} broonie
2023-12-09 1:02 ` [PATCH 04/13] arm64/sysreg: update CPACR_EL1 register broonie
2023-12-09 1:02 ` [PATCH 05/13] arm64/sysreg: Add definition for ID_AA64PFR2_EL1 Mark Brown
2023-12-11 8:59 ` Fuad Tabba
2023-12-09 1:02 ` [PATCH 06/13] arm64/sysreg: Update ID_AA64ISAR2_EL1 defintion for DDI0601 2023-09 Mark Brown
2023-12-11 9:07 ` Fuad Tabba
2023-12-12 9:10 ` Will Deacon
2023-12-12 10:24 ` Fuad Tabba
2023-12-12 12:56 ` Mark Brown
2023-12-09 1:02 ` [PATCH 07/13] arm64/sysreg: Add definition for ID_AA64ISAR3_EL1 Mark Brown
2023-12-11 9:14 ` Fuad Tabba
2023-12-09 1:02 ` [PATCH 08/13] arm64/sysreg: Add definition for ID_AA64FPFR0_EL1 Mark Brown
2023-12-11 9:18 ` Fuad Tabba
2023-12-09 1:02 ` [PATCH 09/13] arm64/sysreg: Update ID_AA64SMFR0_EL1 definition for DDI0601 2023-09 Mark Brown
2023-12-11 9:17 ` Fuad Tabba
2023-12-09 1:02 ` [PATCH 10/13] arm64/sysreg: Update SCTLR_EL1 " Mark Brown
2023-12-11 9:19 ` Fuad Tabba
2023-12-09 1:02 ` Mark Brown [this message]
2023-12-11 9:26 ` [PATCH 11/13] arm64/sysreg: Update HCRX_EL2 definition " Fuad Tabba
2023-12-09 1:02 ` [PATCH 12/13] arm64/sysreg: Add definition for FPMR Mark Brown
2023-12-11 9:28 ` Fuad Tabba
2023-12-09 1:02 ` [PATCH 13/13] arm64/sysreg: Add new system registers for GCS Mark Brown
2023-12-11 9:38 ` Fuad Tabba
2023-12-11 20:27 ` [PATCH 00/13] arm64/sysreg: System register updates from the 2023-09 XML release Will Deacon
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=20231209-b4-arm64-sysreg-additions-v1-11-45284e538474@kernel.org \
--to=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=joey.gouly@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tabba@google.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