summaryrefslogtreecommitdiffstats
path: root/arch/xtensa
diff options
context:
space:
mode:
authorMax Filippov <jcmvbkbc@gmail.com>2016-09-29 10:51:05 -0700
committerMax Filippov <jcmvbkbc@gmail.com>2016-09-29 12:55:00 -0700
commita4c6be5ad1d0c7af0c5421b68a00b6406b28a325 (patch)
tree71f7b6e2746ad5b3f25db3861c942224a4a4e51f /arch/xtensa
parent5b8b3c860ba48f8ac1830cf3a7d02e781de06894 (diff)
downloadlinux-stable-a4c6be5ad1d0c7af0c5421b68a00b6406b28a325.tar.gz
linux-stable-a4c6be5ad1d0c7af0c5421b68a00b6406b28a325.tar.bz2
linux-stable-a4c6be5ad1d0c7af0c5421b68a00b6406b28a325.zip
xtensa: disable MMU initialization option on MMUv2 cores
MMU initialization option is currently ignored on MMUv2 cores, but it is used in Kconfig to select kernel load and start addresses. This choice is not available for MMUv2 cores as they have hardwired TLB entries. Disable MMU initialization option for known MMUv2 cores so that they get correct kernel load/start address by default. This fixes the default allmodconfig build. Signed-off-by: Max Filippov <jcmvbkbc@gmail.com>
Diffstat (limited to 'arch/xtensa')
-rw-r--r--arch/xtensa/Kconfig1
1 files changed, 1 insertions, 0 deletions
diff --git a/arch/xtensa/Kconfig b/arch/xtensa/Kconfig
index 4a866aaed67a..f61058617ada 100644
--- a/arch/xtensa/Kconfig
+++ b/arch/xtensa/Kconfig
@@ -212,6 +212,7 @@ config HOTPLUG_CPU
config INITIALIZE_XTENSA_MMU_INSIDE_VMLINUX
bool "Initialize Xtensa MMU inside the Linux kernel code"
+ depends on !XTENSA_VARIANT_FSF && !XTENSA_VARIANT_DC232B
default y if XTENSA_VARIANT_DC233C || XTENSA_VARIANT_CUSTOM
help
Earlier version initialized the MMU in the exception vector