From: vladimir.murzin@arm.com (Vladimir Murzin)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4/7] ARM: NOMMU: Disallow MPU for XIP
Date: Tue, 13 Jun 2017 10:05:04 +0100 [thread overview]
Message-ID: <1497344707-14446-5-git-send-email-vladimir.murzin@arm.com> (raw)
In-Reply-To: <1497344707-14446-1-git-send-email-vladimir.murzin@arm.com>
It seems that MPU never worked with XIP, so we just disallow such
combination.
Tested-by: Szemz? Andr?s <sza@esh.hu>
Signed-off-by: Vladimir Murzin <vladimir.murzin@arm.com>
---
arch/arm/Kconfig-nommu | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/Kconfig-nommu b/arch/arm/Kconfig-nommu
index b757634..6d18395 100644
--- a/arch/arm/Kconfig-nommu
+++ b/arch/arm/Kconfig-nommu
@@ -52,7 +52,7 @@ config REMAP_VECTORS_TO_RAM
config ARM_MPU
bool 'Use the ARM v7 PMSA Compliant MPU'
- depends on CPU_V7
+ depends on !XIP_KERNEL && CPU_V7
default y
help
Some ARM systems without an MMU have instead a Memory Protection
--
2.0.0
next prev parent reply other threads:[~2017-06-13 9:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-13 9:05 [PATCH 0/7] ARM: NOMMU: MPU updates Vladimir Murzin
2017-06-13 9:05 ` [PATCH 1/7] ARM: NOMMU: Move out MPU setup in separate module Vladimir Murzin
2017-06-13 9:05 ` [PATCH 2/7] ARM: NOMMU: Update MPU accessors to use cp15 helpers Vladimir Murzin
2017-06-13 9:05 ` [PATCH 3/7] ARM: NOMMU: Rework MPU to be mostly done in C Vladimir Murzin
2017-06-13 9:05 ` Vladimir Murzin [this message]
2017-06-13 9:05 ` [PATCH 5/7] ARM: Kconfig: Kill CONFIG_VECTORS_BASE Vladimir Murzin
2017-06-13 9:05 ` [PATCH 6/7] ARM: V7M: Add support for MPU to M-class Vladimir Murzin
2017-06-13 9:05 ` [PATCH 7/7] ARM: NOMMU: Use more MPU regions to cover memory Vladimir Murzin
2017-06-20 8:30 ` [PATCH 0/7] ARM: NOMMU: MPU updates Vladimir Murzin
2017-06-27 8:33 ` Vladimir Murzin
2017-07-07 10:39 ` Vladimir Murzin
2017-07-28 15:51 ` Alexandre Torgue
2017-08-11 16:06 ` Vladimir Murzin
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=1497344707-14446-5-git-send-email-vladimir.murzin@arm.com \
--to=vladimir.murzin@arm.com \
--cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.