diff options
| author | Nikita Shubin <n.shubin@yadro.com> | 2022-09-02 11:47:39 +0300 |
|---|---|---|
| committer | Leo Yu-Chi Liang <ycliang@andestech.com> | 2022-09-26 14:28:43 +0800 |
| commit | c2bdf02c9d40da7154fea46b7d10343fe9f14209 (patch) | |
| tree | 362d3715d67989f0d7208a674422dd9e79681eaf /arch/riscv/Kconfig | |
| parent | 435596d57f8beedf36b5dc858fe7ba9d6c03334b (diff) | |
| download | u-boot-c2bdf02c9d40da7154fea46b7d10343fe9f14209.zip u-boot-c2bdf02c9d40da7154fea46b7d10343fe9f14209.tar.gz u-boot-c2bdf02c9d40da7154fea46b7d10343fe9f14209.tar.bz2 | |
spl: introduce SPL_XIP to config
U-Boot and SPL don't necessary share the same location, so we might end
with U-Boot SPL in read-only memory (XIP) and U-Boot in read-write memory.
In case of non XIP boot mode, we rely on such variables as "hart_lottery"
and "available_harts_lock" which we use as atomics.
The problem is that CONFIG_XIP also propagate to main U-Boot, not only SPL,
so we need CONFIG_SPL_XIP to distinguish SPL XIP from other XIP modes.
This adds an option special for SPL to behave it in XIP manner and we don't
use hart_lottery and available_harts_lock, during start proccess.
Signed-off-by: Nikita Shubin <n.shubin@yadro.com>
Reviewed-by: Rick Chen <rick@andestech.com>
Diffstat (limited to 'arch/riscv/Kconfig')
| -rw-r--r-- | arch/riscv/Kconfig | 7 |
1 files changed, 7 insertions, 0 deletions
diff --git a/arch/riscv/Kconfig b/arch/riscv/Kconfig index 78e964d..c042506 100644 --- a/arch/riscv/Kconfig +++ b/arch/riscv/Kconfig @@ -269,6 +269,13 @@ config XIP from a NOR flash memory without copying the code to ram. Say yes here if U-Boot boots from flash directly. +config SPL_XIP + bool "Enable XIP mode for SPL" + help + If SPL starts in read-only memory (XIP for example) then we shouldn't + rely on lock variables (for example hart_lottery and available_harts_lock), + this affects only SPL, other stages should proceed as non-XIP. + config SHOW_REGS bool "Show registers on unhandled exception" |