From: Vikas Manocha <vikas.manocha@st.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 4/4] stm32f7: configure mpu valid for f7 family
Date: Wed, 3 May 2017 16:38:57 -0700 [thread overview]
Message-ID: <1493854737-4961-5-git-send-email-vikas.manocha@st.com> (raw)
In-Reply-To: <1493854737-4961-1-git-send-email-vikas.manocha@st.com>
This configuration should be valid for all F7 family devices in general.
Here is the regions info:
- Region0 : 4GB : cacheable & executable.
- Region1 : 512MB : text area : strogly ordered & executable.
- Region2 : 512MB : peripherals : device memory & non-executable.
- Region3 : 512MB : peripherals : device memory & non-executable.
- Region4 : 512MB : cortexM area: strongly ordered & non-executable.
Higher region number overrides the lower region configuration.
Signed-off-by: Vikas Manocha <vikas.manocha@st.com>
---
arch/arm/mach-stm32/stm32f7/soc.c | 15 ++++++++++++---
1 file changed, 12 insertions(+), 3 deletions(-)
diff --git a/arch/arm/mach-stm32/stm32f7/soc.c b/arch/arm/mach-stm32/stm32f7/soc.c
index 3586133..74a9350 100644
--- a/arch/arm/mach-stm32/stm32f7/soc.c
+++ b/arch/arm/mach-stm32/stm32f7/soc.c
@@ -19,10 +19,19 @@ int arch_cpu_init(void)
{
struct mpu_region_config stm32_region_config[] = {
{ 0x00000000, REGION_0, XN_DIS, PRIV_RW_USR_RW,
- STRONG_ORDER, REGION_4GB },
+ O_I_WB_RD_WR_ALLOC, REGION_4GB },
- { 0xC0000000, REGION_1, XN_DIS, PRIV_RW_USR_RW,
- O_I_WB_RD_WR_ALLOC, REGION_8MB },
+ { 0x00000000, REGION_1, XN_DIS, PRIV_RW_USR_RW,
+ STRONG_ORDER, REGION_512MB },
+
+ { 0x40000000, REGION_2, XN_EN, PRIV_RW_USR_RW,
+ DEVICE_NON_SHARED, REGION_512MB },
+
+ { 0xA0000000, REGION_3, XN_EN, PRIV_RW_USR_RW,
+ DEVICE_NON_SHARED, REGION_512MB },
+
+ { 0xE0000000, REGION_4, XN_EN, PRIV_RW_USR_RW,
+ STRONG_ORDER, REGION_512MB },
};
disable_mpu();
--
1.9.1
next prev parent reply other threads:[~2017-05-03 23:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-03 23:38 [U-Boot] [PATCH 0/4] armv7m: add memory protection unit support Vikas Manocha
2017-05-03 23:38 ` [U-Boot] [PATCH 1/4] armv7m: correct mpu region size define for 8MB size Vikas Manocha
2017-05-12 17:20 ` [U-Boot] [U-Boot, " Tom Rini
2017-05-03 23:38 ` [U-Boot] [PATCH 2/4] armv7m: add MPU configuration support Vikas Manocha
2017-05-12 17:20 ` [U-Boot] [U-Boot,2/4] " Tom Rini
2017-05-03 23:38 ` [U-Boot] [PATCH 3/4] stm32: use armv7m " Vikas Manocha
2017-05-12 17:20 ` [U-Boot] [U-Boot, " Tom Rini
2017-05-03 23:38 ` Vikas Manocha [this message]
2017-05-12 17:20 ` [U-Boot] [U-Boot, 4/4] stm32f7: configure mpu valid for f7 family Tom Rini
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=1493854737-4961-5-git-send-email-vikas.manocha@st.com \
--to=vikas.manocha@st.com \
--cc=u-boot@lists.denx.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