From: Alexandre Torgue <alexandre.torgue@st.com>
To: Maxime Coquelin <mcoquelin.stm32@gmail.com>,
arnd@arndb.de, robh+dt@kernel.org, mark.rutland@arm.com,
linux@armlinux.org.uk, patrice.chotard@st.com,
lee.jones@linaro.org
Cc: devicetree@vger.kernel.org, vladimir.murzin@arm.com,
Alexandre Torgue <alexandre.torgue@st.com>,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 3/4] ARM: stm32: Select ARM_MPU for cortex-M7 machines
Date: Wed, 28 Feb 2018 14:10:57 +0100 [thread overview]
Message-ID: <1519823458-27734-4-git-send-email-alexandre.torgue@st.com> (raw)
In-Reply-To: <1519823458-27734-1-git-send-email-alexandre.torgue@st.com>
STM32 MCUs embed a Memory Protection Unit. Enabling ARM_MPU flag will
allow the Kernel to configure the MPU according to the devicetree.
Signed-off-by: Alexandre Torgue <alexandre.torgue@st.com>
diff --git a/arch/arm/mach-stm32/Kconfig b/arch/arm/mach-stm32/Kconfig
index 713c068..c2ad8e9 100644
--- a/arch/arm/mach-stm32/Kconfig
+++ b/arch/arm/mach-stm32/Kconfig
@@ -29,15 +29,18 @@ config MACH_STM32F469
config MACH_STM32F746
bool "STMicroelectronics STM32F746"
select ARM_AMBA
+ select ARM_MPU
default y
config MACH_STM32F769
bool "STMicroelectronics STM32F769"
select ARM_AMBA
+ select ARM_MPU
default y
config MACH_STM32H743
bool "STMicroelectronics STM32H743"
+ select ARM_MPU
default y
endif # ARMv7-M
--
2.7.4
next prev parent reply other threads:[~2018-02-28 13:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-28 13:10 [PATCH v2 0/4] Enable DMA on STM32 MCU based on cortex-M7 Alexandre Torgue
2018-02-28 13:10 ` [PATCH v2 1/4] ARM: dts: stm32: add DMA memory pool on MCU which embed a cortex-M7 Alexandre Torgue
2018-02-28 13:10 ` [PATCH v2 2/4] ARM: configs: stm32: remove XIP configuration Alexandre Torgue
2018-02-28 13:10 ` Alexandre Torgue [this message]
2018-02-28 13:10 ` [PATCH v2 4/4] ARM: dts: stm32: enable dma on MCU which embed a cortex-M7 Alexandre Torgue
2018-02-28 13:22 ` [PATCH v2 0/4] Enable DMA on STM32 MCU based on cortex-M7 Vladimir Murzin
2018-02-28 13:42 ` Alexandre Torgue
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=1519823458-27734-4-git-send-email-alexandre.torgue@st.com \
--to=alexandre.torgue@st.com \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=patrice.chotard@st.com \
--cc=robh+dt@kernel.org \
--cc=vladimir.murzin@arm.com \
/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