2019-11-01 20:45:29 +08:00
|
|
|
# ARM architecture configuration options
|
2015-05-21 00:40:39 +08:00
|
|
|
|
|
|
|
# Copyright (c) 2014-2015 Wind River Systems, Inc.
|
2017-01-19 09:01:01 +08:00
|
|
|
# SPDX-License-Identifier: Apache-2.0
|
2015-05-21 00:40:39 +08:00
|
|
|
|
2016-03-16 01:24:36 +08:00
|
|
|
menu "ARM Options"
|
2015-10-09 18:20:52 +08:00
|
|
|
depends on ARM
|
|
|
|
|
|
|
|
config ARCH
|
|
|
|
default "arm"
|
2015-05-26 22:38:04 +08:00
|
|
|
|
2020-03-31 09:56:32 +08:00
|
|
|
config CPU_CORTEX
|
|
|
|
bool
|
|
|
|
help
|
|
|
|
This option signifies the use of a CPU of the Cortex family.
|
|
|
|
|
2020-02-11 15:21:36 +08:00
|
|
|
config ARM_CUSTOM_INTERRUPT_CONTROLLER
|
|
|
|
bool
|
|
|
|
depends on !CPU_CORTEX_M
|
|
|
|
help
|
|
|
|
This option indicates that the ARM CPU is connected to a custom (i.e.
|
|
|
|
non-GIC) interrupt controller.
|
|
|
|
|
|
|
|
A number of Cortex-A and Cortex-R cores (Cortex-A5, Cortex-R4/5, ...)
|
|
|
|
allow interfacing to a custom external interrupt controller and this
|
|
|
|
option must be selected when such cores are connected to an interrupt
|
|
|
|
controller that is not the ARM Generic Interrupt Controller (GIC).
|
|
|
|
|
|
|
|
When this option is selected, the architecture interrupt control
|
|
|
|
functions are mapped to the SoC interrupt control interface, which is
|
|
|
|
implemented at the SoC level.
|
|
|
|
|
|
|
|
N.B. This option is only applicable to the Cortex-A and Cortex-R
|
|
|
|
family cores. The Cortex-M family cores are always equipped with
|
|
|
|
the ARM Nested Vectored Interrupt Controller (NVIC).
|
|
|
|
|
2021-04-29 06:08:37 +08:00
|
|
|
config CODE_DATA_RELOCATION
|
|
|
|
bool "Relocate code/data sections"
|
|
|
|
depends on CPU_CORTEX_M
|
|
|
|
help
|
|
|
|
When selected this will relocate .text, data and .bss sections from
|
|
|
|
the specified files and places it in the required memory region. The
|
|
|
|
files should be specified in the CMakeList.txt file with
|
|
|
|
a cmake API zephyr_code_relocate().
|
|
|
|
|
|
|
|
config CODE_DATA_RELOCATION_SRAM
|
|
|
|
bool "Relocate code/data sections to SRAM"
|
|
|
|
depends on CPU_CORTEX_M
|
|
|
|
select CODE_DATA_RELOCATION
|
|
|
|
help
|
|
|
|
When selected this will relocate .text, data and .bss sections from
|
|
|
|
the specified files and places it in SRAM. The files should be specified
|
|
|
|
in the CMakeList.txt file with a cmake API zephyr_code_relocate(). This
|
|
|
|
config is used to create an MPU entry for the SRAM space used for code
|
|
|
|
relocation.
|
|
|
|
|
2020-03-31 09:56:32 +08:00
|
|
|
rsource "core/aarch32/Kconfig"
|
|
|
|
|
2016-03-15 10:51:58 +08:00
|
|
|
endmenu
|