aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorMurali Karicheri2015-01-21 13:54:02 -0600
committerMurali Karicheri2015-01-22 09:43:56 -0600
commit6e06c6e6c72581cbeeb4dadfd38096db83435c00 (patch)
tree6a19306d42b823b24b9357383980e8a737f2b3c7
parent90507d089c2ac53041fb8e2d4db78e013902bc6c (diff)
downloadlinux-6e06c6e6c72581cbeeb4dadfd38096db83435c00.tar.gz
linux-6e06c6e6c72581cbeeb4dadfd38096db83435c00.tar.xz
linux-6e06c6e6c72581cbeeb4dadfd38096db83435c00.zip
ARM: keystone: allow FORCE_MAX_ZONEORDER to be configurable on Keystone
Currently adding CONFIG_FORCE_MAX_ZONEORDER option in defconfig doesn't change the MAX_ZONEORDER used in defconfig. User require tuning of this on a target board. So fix this. Signed-off-by: Murali Karicheri <m-karicheri2@ti.com>
-rw-r--r--arch/arm/Kconfig2
1 files changed, 1 insertions, 1 deletions
diff --git a/arch/arm/Kconfig b/arch/arm/Kconfig
index 74304ff17d6..5a6c3e71ea8 100644
--- a/arch/arm/Kconfig
+++ b/arch/arm/Kconfig
@@ -1766,7 +1766,7 @@ config HW_PERF_EVENTS
1766source "mm/Kconfig" 1766source "mm/Kconfig"
1767 1767
1768config FORCE_MAX_ZONEORDER 1768config FORCE_MAX_ZONEORDER
1769 int "Maximum zone order" if ARCH_SHMOBILE 1769 int "Maximum zone order" if ARCH_SHMOBILE || ARCH_KEYSTONE
1770 range 11 64 if ARCH_SHMOBILE 1770 range 11 64 if ARCH_SHMOBILE
1771 default "12" if SOC_AM33XX 1771 default "12" if SOC_AM33XX
1772 default "9" if SA1111 1772 default "9" if SA1111