mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Barebox List <barebox@lists.infradead.org>
Cc: Steffen Trumtrar <str@pengutronix.de>
Subject: [PATCH] ARM: ARMv5: make PTE_SMALL_AP_UNO_SRO work
Date: Thu,  2 Apr 2026 16:01:29 +0200	[thread overview]
Message-ID: <20260402140129.1108000-1-s.hauer@pengutronix.de> (raw)

On ARMv4/5 we have the SCTLR.S and SCTLR.R bits. We set the former which
is deprecated and has implementation defined behaviour on ARMv5. We
clear the latter which has the effect that AP=0b00 as used in PTE_SMALL_AP_UNO_SRO
means "no access".

Clear SCTLR.S and set SCTLR.R instead. With this AP=0b00 maps to
read-only access as intended.

Do not touch any of these bits for >= ARMv6 as both are reserved there.

Fixes: 5916385fae ("ARM: MMU: map text segment ro and data segments execute never")
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
---
 arch/arm/cpu/lowlevel_32.S | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/arch/arm/cpu/lowlevel_32.S b/arch/arm/cpu/lowlevel_32.S
index 3b1dea5c67..517cefa7b4 100644
--- a/arch/arm/cpu/lowlevel_32.S
+++ b/arch/arm/cpu/lowlevel_32.S
@@ -59,7 +59,7 @@ THUMB(	orr	r12, r12, #PSR_T_BIT	)
 	/* disable MMU stuff and data/unified caches */
 	mrc	p15, 0, r12, c1, c0, 0		/* SCTLR */
 	bic	r12, r12, #(CR_M | CR_C | CR_B)
-	bic	r12, r12, #(CR_S | CR_R | CR_V)
+	bic	r12, r12, #CR_V
 
 #ifndef CONFIG_ARCH_IMX_EXTERNAL_BOOT_NAND
 	/* enable instruction cache */
@@ -70,7 +70,8 @@ THUMB(	orr	r12, r12, #PSR_T_BIT	)
 	orr	r12, r12, #CR_U
 	bic	r12, r12, #CR_A
 #else
-	orr	r12, r12, #CR_S
+	bic	r12, r12, #CR_S
+	orr	r12, r12, #CR_R
 	orr	r12, r12, #CR_A
 #endif
 
-- 
2.47.3




                 reply	other threads:[~2026-04-02 14:02 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20260402140129.1108000-1-s.hauer@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=str@pengutronix.de \
    /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