Merge branch 'master' of git://git.denx.de/u-boot

[u-boot] / arch / arm / cpu / armv8 / Kconfig

diff --git a/arch/arm/cpu/armv8/Kconfig b/arch/arm/cpu/armv8/Kconfig
index 3d19bbfbe24124df6f3a7680f9b0a5d5adc6050b..965a8d129c1d0055a1decde4f38d898c1905452e 100644 (file)
--- a/arch/arm/cpu/armv8/Kconfig
+++ b/arch/arm/cpu/armv8/Kconfig
@@ -1,6 +1,43 @@
 if ARM64
 
 config ARMV8_MULTIENTRY
-        boolean "Enable multiple CPUs to enter into U-Boot"
+        bool "Enable multiple CPUs to enter into U-Boot"
+
+config ARMV8_SPIN_TABLE
+       bool "Support spin-table enable method"
+       depends on ARMV8_MULTIENTRY && OF_LIBFDT
+       help
+         Say Y here to support "spin-table" enable method for booting Linux.
+
+         To use this feature, you must do:
+           - Specify enable-method = "spin-table" in each CPU node in the
+             Device Tree you are using to boot the kernel
+           - Let secondary CPUs in U-Boot (in a board specific manner)
+             before the master CPU jumps to the kernel
+
+         U-Boot automatically does:
+           - Set "cpu-release-addr" property of each CPU node
+             (overwrites it if already exists).
+           - Reserve the code for the spin-table and the release address
+             via a /memreserve/ region in the Device Tree.
+
+config PSCI_RESET
+       bool "Use PSCI for reset and shutdown"
+       default y
+       depends on !ARCH_EXYNOS7 && !ARCH_BCM283X && !TARGET_LS2080A_EMU && \
+                  !TARGET_LS2080A_SIMU && !TARGET_LS2080AQDS && \
+                  !TARGET_LS2080ARDB && !TARGET_LS1012AQDS && \
+                  !TARGET_LS1012ARDB && !TARGET_LS1012AFRDM && \
+                  !TARGET_LS1043ARDB && !TARGET_LS1043AQDS && \
+                  !TARGET_LS1046ARDB && !TARGET_LS1046AQDS && \
+                  !ARCH_UNIPHIER && !ARCH_SNAPDRAGON && !TARGET_S32V234EVB
+       help
+         Most armv8 systems have PSCI support enabled in EL3, either through
+         ARM Trusted Firmware or other firmware.
+
+         On these systems, we do not need to implement system reset manually,
+         but can instead rely on higher level firmware to deal with it.
+
+         Select Y here to make use of PSCI calls for system reset
 
 endif