mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
* [PATCH 0/2] Add boot requirements for POE + cleanup booting.rst
@ 2026-11-19 18:02 Kevin Brodsky
  2026-11-19 18:02 ` [PATCH 1/2] docs: arm64: Fix RST formatting in booting.rst Kevin Brodsky
  2026-11-19 18:02 ` [PATCH 2/2] docs: arm64: Document booting requirements for POE at EL0 Kevin Brodsky
  0 siblings, 2 replies; 5+ messages in thread
From: Kevin Brodsky @ 2026-11-19 18:02 UTC (permalink / raw)
  To: linux-arm-kernel
  Cc: Kevin Brodsky, Catalin Marinas, Mark Brown, Mark Rutland,
	Will Deacon, linux-doc, linux-kernel

Mark Brown pointed out [1] that my series enabling POE at EL1 does
not update booting.rst. Turns out, we don't even have the
requirements for using POE at EL0 in booting.rst - let's fix that.

While looking at booting.rst, I realised the formatting was broken
in many places. Patch 1 attempts to fix that, while patch 2 actually
adds POE boot requirements.

Various bits generated by Codex (under close supervision :) ).

Signed-off-by: Kevin Brodsky <kevin.brodsky@arm.com>

[1] https://lore.kernel.org/r/3500936b-4177-4ba0-a9df-7eb9d9d75b0a@sirena.org.uk

---
To: linux-arm-kernel@lists.infradead.org
Cc: Catalin Marinas <catalin.marinas@arm.com>
Cc: Mark Brown <broonie@kernel.org>
Cc: Mark Rutland <mark.rutland@arm.com>
Cc: Will Deacon <will@kernel.org>
Cc: linux-doc@vger.kernel.org
Cc: linux-kernel@vger.kernel.org

---
Kevin Brodsky (2):
      docs: arm64: Fix RST formatting in booting.rst
      docs: arm64: Document booting requirements for POE at EL0

 Documentation/arch/arm64/booting.rst | 160 +++++++++++++++++++----------------
 1 file changed, 87 insertions(+), 73 deletions(-)
---
base-commit: aebb7274476403040d582c61478df8f4a7bf9cd3
change-id: 20261119-poe_booting_rst-dbd1b607aaea


^ permalink raw reply	[flat|nested] 5+ messages in thread

* [PATCH 1/2] docs: arm64: Fix RST formatting in booting.rst
  2026-11-19 18:02 [PATCH 0/2] Add boot requirements for POE + cleanup booting.rst Kevin Brodsky
@ 2026-11-19 18:02 ` Kevin Brodsky
  2026-11-19 19:06   ` Randy Dunlap
  2026-11-19 18:02 ` [PATCH 2/2] docs: arm64: Document booting requirements for POE at EL0 Kevin Brodsky
  1 sibling, 1 reply; 5+ messages in thread
From: Kevin Brodsky @ 2026-11-19 18:02 UTC (permalink / raw)
  To: linux-arm-kernel
  Cc: Kevin Brodsky, Catalin Marinas, Mark Brown, Mark Rutland,
	Will Deacon, linux-doc, linux-kernel

Inconsistent indentation and missing blank lines in booting.rst
generate unintended blockquotes and nesting under earlier entries.

Fix the lists indentation (use 2 spaces everywhere) and add missing
empty lines. Also make sure all feature introductions are standalone
paragraphs, and remove excess indentation from the flags field table
(which also generated a blockquote).

Signed-off-by: Kevin Brodsky <kevin.brodsky@arm.com>
---
 Documentation/arch/arm64/booting.rst | 148 ++++++++++++++++++-----------------
 1 file changed, 75 insertions(+), 73 deletions(-)

diff --git a/Documentation/arch/arm64/booting.rst b/Documentation/arch/arm64/booting.rst
index dae5ff9fae26..8f22aa7b2c0b 100644
--- a/Documentation/arch/arm64/booting.rst
+++ b/Documentation/arch/arm64/booting.rst
@@ -113,20 +113,20 @@ Header notes:
   Bit 0		Kernel endianness.  1 if BE, 0 if LE.
   Bit 1-2	Kernel Page size.
 
-			* 0 - Unspecified.
-			* 1 - 4K
-			* 2 - 16K
-			* 3 - 64K
+		* 0 - Unspecified.
+		* 1 - 4K
+		* 2 - 16K
+		* 3 - 64K
   Bit 3		Kernel physical placement
 
-			0
-			  2MB aligned base should be as close as possible
-			  to the base of DRAM, since memory below it is not
-			  accessible via the linear mapping
-			1
-			  2MB aligned base such that all image_size bytes
-			  counted from the start of the image are within
-			  the 48-bit addressable range of physical memory
+		0
+		  2MB aligned base should be as close as possible
+		  to the base of DRAM, since memory below it is not
+		  accessible via the linear mapping
+		1
+		  2MB aligned base such that all image_size bytes
+		  counted from the start of the image are within
+		  the 48-bit addressable range of physical memory
   Bits 4-63	Reserved.
   ============= ===============================================================
 
@@ -162,10 +162,10 @@ Before jumping into the kernel, the following conditions must be met:
 
 - Primary CPU general-purpose register settings:
 
-    - x0 = physical address of device tree blob (dtb) in system RAM.
-    - x1 = 0 (reserved for future use)
-    - x2 = 0 (reserved for future use)
-    - x3 = 0 (reserved for future use)
+  - x0 = physical address of device tree blob (dtb) in system RAM.
+  - x1 = 0 (reserved for future use)
+  - x2 = 0 (reserved for future use)
+  - x3 = 0 (reserved for future use)
 
 - CPU mode
 
@@ -212,6 +212,7 @@ Before jumping into the kernel, the following conditions must be met:
   state.
 
   For all systems:
+
   - If EL3 is present:
 
     - SCR_EL3.FIQ must have the same value across all CPUs the kernel is
@@ -227,56 +228,57 @@ Before jumping into the kernel, the following conditions must be met:
 
   - If the kernel is entered at EL1 and EL2 is present:
 
-      - ICH_HFGRTR_EL2.ICC_PPI_ACTIVERn_EL1 (bit 20) must be initialised to 0b1.
-      - ICH_HFGRTR_EL2.ICC_PPI_PRIORITYRn_EL1 (bit 19) must be initialised to 0b1.
-      - ICH_HFGRTR_EL2.ICC_PPI_PENDRn_EL1 (bit 18) must be initialised to 0b1.
-      - ICH_HFGRTR_EL2.ICC_PPI_ENABLERn_EL1 (bit 17) must be initialised to 0b1.
-      - ICH_HFGRTR_EL2.ICC_PPI_HMRn_EL1 (bit 16) must be initialised to 0b1.
-      - ICH_HFGRTR_EL2.ICC_IAFFIDR_EL1 (bit 7) must be initialised to 0b1.
-      - ICH_HFGRTR_EL2.ICC_ICSR_EL1 (bit 6) must be initialised to 0b1.
-      - ICH_HFGRTR_EL2.ICC_PCR_EL1 (bit 5) must be initialised to 0b1.
-      - ICH_HFGRTR_EL2.ICC_HPPIR_EL1 (bit 4) must be initialised to 0b1.
-      - ICH_HFGRTR_EL2.ICC_HAPR_EL1 (bit 3) must be initialised to 0b1.
-      - ICH_HFGRTR_EL2.ICC_CR0_EL1 (bit 2) must be initialised to 0b1.
-      - ICH_HFGRTR_EL2.ICC_IDRn_EL1 (bit 1) must be initialised to 0b1.
-      - ICH_HFGRTR_EL2.ICC_APR_EL1 (bit 0) must be initialised to 0b1.
-
-      - ICH_HFGWTR_EL2.ICC_PPI_ACTIVERn_EL1 (bit 20) must be initialised to 0b1.
-      - ICH_HFGWTR_EL2.ICC_PPI_PRIORITYRn_EL1 (bit 19) must be initialised to 0b1.
-      - ICH_HFGWTR_EL2.ICC_PPI_PENDRn_EL1 (bit 18) must be initialised to 0b1.
-      - ICH_HFGWTR_EL2.ICC_PPI_ENABLERn_EL1 (bit 17) must be initialised to 0b1.
-      - ICH_HFGWTR_EL2.ICC_ICSR_EL1 (bit 6) must be initialised to 0b1.
-      - ICH_HFGWTR_EL2.ICC_PCR_EL1 (bit 5) must be initialised to 0b1.
-      - ICH_HFGWTR_EL2.ICC_CR0_EL1 (bit 2) must be initialised to 0b1.
-      - ICH_HFGWTR_EL2.ICC_APR_EL1 (bit 0) must be initialised to 0b1.
-
-      - ICH_HFGITR_EL2.GICRCDNMIA (bit 10) must be initialised to 0b1.
-      - ICH_HFGITR_EL2.GICRCDIA (bit 9) must be initialised to 0b1.
-      - ICH_HFGITR_EL2.GICCDDI (bit 8) must be initialised to 0b1.
-      - ICH_HFGITR_EL2.GICCDEOI (bit 7) must be initialised to 0b1.
-      - ICH_HFGITR_EL2.GICCDHM (bit 6) must be initialised to 0b1.
-      - ICH_HFGITR_EL2.GICCDRCFG (bit 5) must be initialised to 0b1.
-      - ICH_HFGITR_EL2.GICCDPEND (bit 4) must be initialised to 0b1.
-      - ICH_HFGITR_EL2.GICCDAFF (bit 3) must be initialised to 0b1.
-      - ICH_HFGITR_EL2.GICCDPRI (bit 2) must be initialised to 0b1.
-      - ICH_HFGITR_EL2.GICCDDIS (bit 1) must be initialised to 0b1.
-      - ICH_HFGITR_EL2.GICCDEN (bit 0) must be initialised to 0b1.
+    - ICH_HFGRTR_EL2.ICC_PPI_ACTIVERn_EL1 (bit 20) must be initialised to 0b1.
+    - ICH_HFGRTR_EL2.ICC_PPI_PRIORITYRn_EL1 (bit 19) must be initialised to 0b1.
+    - ICH_HFGRTR_EL2.ICC_PPI_PENDRn_EL1 (bit 18) must be initialised to 0b1.
+    - ICH_HFGRTR_EL2.ICC_PPI_ENABLERn_EL1 (bit 17) must be initialised to 0b1.
+    - ICH_HFGRTR_EL2.ICC_PPI_HMRn_EL1 (bit 16) must be initialised to 0b1.
+    - ICH_HFGRTR_EL2.ICC_IAFFIDR_EL1 (bit 7) must be initialised to 0b1.
+    - ICH_HFGRTR_EL2.ICC_ICSR_EL1 (bit 6) must be initialised to 0b1.
+    - ICH_HFGRTR_EL2.ICC_PCR_EL1 (bit 5) must be initialised to 0b1.
+    - ICH_HFGRTR_EL2.ICC_HPPIR_EL1 (bit 4) must be initialised to 0b1.
+    - ICH_HFGRTR_EL2.ICC_HAPR_EL1 (bit 3) must be initialised to 0b1.
+    - ICH_HFGRTR_EL2.ICC_CR0_EL1 (bit 2) must be initialised to 0b1.
+    - ICH_HFGRTR_EL2.ICC_IDRn_EL1 (bit 1) must be initialised to 0b1.
+    - ICH_HFGRTR_EL2.ICC_APR_EL1 (bit 0) must be initialised to 0b1.
+
+    - ICH_HFGWTR_EL2.ICC_PPI_ACTIVERn_EL1 (bit 20) must be initialised to 0b1.
+    - ICH_HFGWTR_EL2.ICC_PPI_PRIORITYRn_EL1 (bit 19) must be initialised to 0b1.
+    - ICH_HFGWTR_EL2.ICC_PPI_PENDRn_EL1 (bit 18) must be initialised to 0b1.
+    - ICH_HFGWTR_EL2.ICC_PPI_ENABLERn_EL1 (bit 17) must be initialised to 0b1.
+    - ICH_HFGWTR_EL2.ICC_ICSR_EL1 (bit 6) must be initialised to 0b1.
+    - ICH_HFGWTR_EL2.ICC_PCR_EL1 (bit 5) must be initialised to 0b1.
+    - ICH_HFGWTR_EL2.ICC_CR0_EL1 (bit 2) must be initialised to 0b1.
+    - ICH_HFGWTR_EL2.ICC_APR_EL1 (bit 0) must be initialised to 0b1.
+
+    - ICH_HFGITR_EL2.GICRCDNMIA (bit 10) must be initialised to 0b1.
+    - ICH_HFGITR_EL2.GICRCDIA (bit 9) must be initialised to 0b1.
+    - ICH_HFGITR_EL2.GICCDDI (bit 8) must be initialised to 0b1.
+    - ICH_HFGITR_EL2.GICCDEOI (bit 7) must be initialised to 0b1.
+    - ICH_HFGITR_EL2.GICCDHM (bit 6) must be initialised to 0b1.
+    - ICH_HFGITR_EL2.GICCDRCFG (bit 5) must be initialised to 0b1.
+    - ICH_HFGITR_EL2.GICCDPEND (bit 4) must be initialised to 0b1.
+    - ICH_HFGITR_EL2.GICCDAFF (bit 3) must be initialised to 0b1.
+    - ICH_HFGITR_EL2.GICCDPRI (bit 2) must be initialised to 0b1.
+    - ICH_HFGITR_EL2.GICCDDIS (bit 1) must be initialised to 0b1.
+    - ICH_HFGITR_EL2.GICCDEN (bit 0) must be initialised to 0b1.
 
   - The DT or ACPI tables must describe a GICv5 interrupt controller.
 
   For systems with a GICv3 interrupt controller to be used in v3 mode:
+
   - If EL3 is present:
 
-      - ICC_SRE_EL3.Enable (bit 3) must be initialised to 0b1.
-      - ICC_SRE_EL3.SRE (bit 0) must be initialised to 0b1.
-      - ICC_CTLR_EL3.PMHE (bit 6) must be set to the same value across
-        all CPUs the kernel is executing on, and must stay constant
-        for the lifetime of the kernel.
+    - ICC_SRE_EL3.Enable (bit 3) must be initialised to 0b1.
+    - ICC_SRE_EL3.SRE (bit 0) must be initialised to 0b1.
+    - ICC_CTLR_EL3.PMHE (bit 6) must be set to the same value across
+      all CPUs the kernel is executing on, and must stay constant
+      for the lifetime of the kernel.
 
   - If the kernel is entered at EL1:
 
-      - ICC_SRE_EL2.Enable (bit 3) must be initialised to 0b1
-      - ICC_SRE_EL2.SRE (bit 0) must be initialised to 0b1.
+    - ICC_SRE_EL2.Enable (bit 3) must be initialised to 0b1
+    - ICC_SRE_EL2.SRE (bit 0) must be initialised to 0b1.
 
   - The DT or ACPI tables must describe a GICv3 interrupt controller.
 
@@ -285,11 +287,11 @@ Before jumping into the kernel, the following conditions must be met:
 
   - If EL3 is present:
 
-      ICC_SRE_EL3.SRE (bit 0) must be initialised to 0b0.
+    - ICC_SRE_EL3.SRE (bit 0) must be initialised to 0b0.
 
   - If the kernel is entered at EL1:
 
-      ICC_SRE_EL2.SRE (bit 0) must be initialised to 0b0.
+    - ICC_SRE_EL2.SRE (bit 0) must be initialised to 0b0.
 
   - The DT or ACPI tables must describe a GICv2 interrupt controller.
 
@@ -380,7 +382,7 @@ Before jumping into the kernel, the following conditions must be met:
     - SMCR_EL3.LEN must be initialised to the same value for all CPUs the
       kernel will execute on.
 
- - If the kernel is entered at EL1 and EL2 is present:
+  - If the kernel is entered at EL1 and EL2 is present:
 
     - CPTR_EL2.TSM (bit 12) must be initialised to 0b0.
 
@@ -405,7 +407,7 @@ Before jumping into the kernel, the following conditions must be met:
 
     - SMCR_EL3.FA64 (bit 31) must be initialised to 0b1.
 
- - If the kernel is entered at EL1 and EL2 is present:
+  - If the kernel is entered at EL1 and EL2 is present:
 
     - SMCR_EL2.FA64 (bit 31) must be initialised to 0b1.
 
@@ -425,7 +427,7 @@ Before jumping into the kernel, the following conditions must be met:
 
     - SMCR_EL3.EZT0 (bit 30) must be initialised to 0b1.
 
- - If the kernel is entered at EL1 and EL2 is present:
+  - If the kernel is entered at EL1 and EL2 is present:
 
     - SMCR_EL2.EZT0 (bit 30) must be initialised to 0b1.
 
@@ -452,11 +454,11 @@ Before jumping into the kernel, the following conditions must be met:
 
   For CPUs with the Performance Monitors Extension (FEAT_PMUv3p9):
 
- - If EL3 is present:
+  - If EL3 is present:
 
     - MDCR_EL3.EnPM2 (bit 7) must be initialised to 0b1.
 
- - If the kernel is entered at EL1 and EL2 is present:
+  - If the kernel is entered at EL1 and EL2 is present:
 
     - HDFGRTR2_EL2.nPMICNTR_EL0 (bit 2) must be initialised to 0b1.
     - HDFGRTR2_EL2.nPMICFILTR_EL0 (bit 3) must be initialised to 0b1.
@@ -493,7 +495,7 @@ Before jumping into the kernel, the following conditions must be met:
 
     - SCR_EL3.TCR2En (bit 43) must be initialised to 0b1.
 
- - If the kernel is entered at EL1 and EL2 is present:
+  - If the kernel is entered at EL1 and EL2 is present:
 
     - HCRX_EL2.TCR2En (bit 14) must be initialised to 0b1.
 
@@ -513,7 +515,7 @@ Before jumping into the kernel, the following conditions must be met:
 
     - HFGRWR_EL2.nPIRE0_EL1 (bit 57) must be initialised to 0b1.
 
- - For CPUs with Guarded Control Stacks (FEAT_GCS):
+  For CPUs with Guarded Control Stacks (FEAT_GCS):
 
   - GCSCR_EL1 must be initialised to 0.
 
@@ -527,7 +529,7 @@ Before jumping into the kernel, the following conditions must be met:
 
     - GCSCR_EL2 must be initialised to 0.
 
- - If the kernel is entered at EL1 and EL2 is present:
+  - If the kernel is entered at EL1 and EL2 is present:
 
     - HCRX_EL2.GCSEn must be initialised to 0b1.
 
@@ -545,17 +547,17 @@ Before jumping into the kernel, the following conditions must be met:
 
     - HFGWTR_EL2.nGCS_EL0 (bit 52) must be initialised to 0b1.
 
- - For CPUs with debug architecture i.e FEAT_Debugv8pN (all versions):
+  For CPUs with debug architecture i.e FEAT_Debugv8pN (all versions):
 
- - If EL3 is present:
+  - If EL3 is present:
 
-   - MDCR_EL3.TDA (bit 9) must be initialized to 0b0
+    - MDCR_EL3.TDA (bit 9) must be initialized to 0b0
 
- - For CPUs with FEAT_PMUv3:
+  For CPUs with FEAT_PMUv3:
 
- - If EL3 is present:
+  - If EL3 is present:
 
-   - MDCR_EL3.TPM (bit 6) must be initialized to 0b0
+    - MDCR_EL3.TPM (bit 6) must be initialized to 0b0
 
   For CPUs with support for 64-byte loads and stores without status (FEAT_LS64):
 

-- 
2.56.0


^ permalink raw reply	[flat|nested] 5+ messages in thread

* [PATCH 2/2] docs: arm64: Document booting requirements for POE at EL0
  2026-11-19 18:02 [PATCH 0/2] Add boot requirements for POE + cleanup booting.rst Kevin Brodsky
  2026-11-19 18:02 ` [PATCH 1/2] docs: arm64: Fix RST formatting in booting.rst Kevin Brodsky
@ 2026-11-19 18:02 ` Kevin Brodsky
  2026-11-19 20:17   ` Mark Brown
  1 sibling, 1 reply; 5+ messages in thread
From: Kevin Brodsky @ 2026-11-19 18:02 UTC (permalink / raw)
  To: linux-arm-kernel
  Cc: Kevin Brodsky, Catalin Marinas, Mark Brown, Mark Rutland,
	Will Deacon, linux-doc, linux-kernel

Add missing boot requirements for the kernel to enable FEAT_S1POE at
EL0 (POE is currently unused at EL1). SCR_EL3.PIEn controls trapping
for both PIE and POE registers.

Suggested-by: Mark Brown <broonie@kernel.org>
Signed-off-by: Kevin Brodsky <kevin.brodsky@arm.com>
---
 Documentation/arch/arm64/booting.rst | 12 ++++++++++++
 1 file changed, 12 insertions(+)

diff --git a/Documentation/arch/arm64/booting.rst b/Documentation/arch/arm64/booting.rst
index 8f22aa7b2c0b..3f31eedd8551 100644
--- a/Documentation/arch/arm64/booting.rst
+++ b/Documentation/arch/arm64/booting.rst
@@ -515,6 +515,18 @@ Before jumping into the kernel, the following conditions must be met:
 
     - HFGRWR_EL2.nPIRE0_EL1 (bit 57) must be initialised to 0b1.
 
+  For CPUs with the Stage 1 Permission Overlay Extension feature (FEAT_S1POE):
+
+  - If EL3 is present:
+
+    - SCR_EL3.PIEn (bit 45) must be initialised to 0b1.
+
+  - If the kernel is entered at EL1 and EL2 is present:
+
+    - HFGRTR_EL2.nPOR_EL0 (bit 59) must be initialised to 0b1.
+
+    - HFGWTR_EL2.nPOR_EL0 (bit 59) must be initialised to 0b1.
+
   For CPUs with Guarded Control Stacks (FEAT_GCS):
 
   - GCSCR_EL1 must be initialised to 0.

-- 
2.56.0


^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [PATCH 1/2] docs: arm64: Fix RST formatting in booting.rst
  2026-11-19 18:02 ` [PATCH 1/2] docs: arm64: Fix RST formatting in booting.rst Kevin Brodsky
@ 2026-11-19 19:06   ` Randy Dunlap
  0 siblings, 0 replies; 5+ messages in thread
From: Randy Dunlap @ 2026-11-19 19:06 UTC (permalink / raw)
  To: Kevin Brodsky, linux-arm-kernel
  Cc: Catalin Marinas, Mark Brown, Mark Rutland, Will Deacon,
	linux-doc, linux-kernel



On 11/19/26 10:02 AM, Kevin Brodsky wrote:
> Inconsistent indentation and missing blank lines in booting.rst
> generate unintended blockquotes and nesting under earlier entries.
> 
> Fix the lists indentation (use 2 spaces everywhere) and add missing
> empty lines. Also make sure all feature introductions are standalone
> paragraphs, and remove excess indentation from the flags field table
> (which also generated a blockquote).
> 
> Signed-off-by: Kevin Brodsky <kevin.brodsky@arm.com>
> ---
>  Documentation/arch/arm64/booting.rst | 148 ++++++++++++++++++-----------------
>  1 file changed, 75 insertions(+), 73 deletions(-)

Much needed cleanup - looks much better now. Thanks.

Acked-by: Randy Dunlap <rdunlap@infradead.org>
Tested-by: Randy Dunlap <rdunlap@infradead.org>

-- 
~Randy

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [PATCH 2/2] docs: arm64: Document booting requirements for POE at EL0
  2026-11-19 18:02 ` [PATCH 2/2] docs: arm64: Document booting requirements for POE at EL0 Kevin Brodsky
@ 2026-11-19 20:17   ` Mark Brown
  0 siblings, 0 replies; 5+ messages in thread
From: Mark Brown @ 2026-11-19 20:17 UTC (permalink / raw)
  To: Kevin Brodsky
  Cc: linux-arm-kernel, Catalin Marinas, Mark Rutland, Will Deacon,
	linux-doc, linux-kernel

[-- Attachment #1: Type: text/plain, Size: 714 bytes --]

On Thu, Nov 19, 2026 at 06:02:43PM +0000, Kevin Brodsky wrote:
> Add missing boot requirements for the kernel to enable FEAT_S1POE at
> EL0 (POE is currently unused at EL1). SCR_EL3.PIEn controls trapping
> for both PIE and POE registers.

> +  For CPUs with the Stage 1 Permission Overlay Extension feature (FEAT_S1POE):
> +
> +  - If EL3 is present:
> +
> +    - SCR_EL3.PIEn (bit 45) must be initialised to 0b1.
> +
> +  - If the kernel is entered at EL1 and EL2 is present:
> +
> +    - HFGRTR_EL2.nPOR_EL0 (bit 59) must be initialised to 0b1.
> +
> +    - HFGWTR_EL2.nPOR_EL0 (bit 59) must be initialised to 0b1.
> +

Looks like everything I'd expect is covered:

Reviewed-by: Mark Brown <broonie@kernel.org>

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2026-11-19 20:17 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2026-11-19 18:02 [PATCH 0/2] Add boot requirements for POE + cleanup booting.rst Kevin Brodsky
2026-11-19 18:02 ` [PATCH 1/2] docs: arm64: Fix RST formatting in booting.rst Kevin Brodsky
2026-11-19 19:06   ` Randy Dunlap
2026-11-19 18:02 ` [PATCH 2/2] docs: arm64: Document booting requirements for POE at EL0 Kevin Brodsky
2026-11-19 20:17   ` Mark Brown

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®