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
|
|
|
|
|
|
2019-11-11 00:17:19 +08:00
|
|
|
rsource "core/aarch32/Kconfig"
|
|
|
|
|
rsource "core/aarch64/Kconfig"
|
Kconfig: Use the first default with a satisfied condition
Up until now, Zephyr has patched Kconfig to use the last 'default' with
a satisfied condition, instead of the first one. I'm not sure why the
patch was added (it predates Kconfiglib), but I suspect it's related to
Kconfig.defconfig files.
There are at least three problems with the patch:
1. It's inconsistent with how Kconfig works in other projects, which
might confuse newcomers.
2. Due to oversights, earlier 'range' properties are still preferred,
as well as earlier 'default' properties on choices.
In addition to being inconsistent, this makes it impossible to
override 'range' properties and choice 'default' properties if the
base definition of the symbol/choice already has 'range'/'default'
properties.
I've seen errors caused by the inconsistency, and I suspect there
are more.
3. A fork of Kconfiglib that adds the patch needs to be maintained.
Get rid of the patch and go back to standard Kconfig behavior, as
follows:
1. Include the Kconfig.defconfig files first instead of last in
Kconfig.zephyr.
2. Include boards/Kconfig and arch/<arch>/Kconfig first instead of
last in arch/Kconfig.
3. Include arch/<arch>/soc/*/Kconfig first instead of last in
arch/<arch>/Kconfig.
4. Swap a few other 'source's to preserve behavior for some scattered
symbols with multiple definitions.
Swap 'source's in some no-op cases too, where it might match the
intent.
5. Reverse the defaults on symbol definitions that have more than one
default.
Skip defaults that are mutually exclusive, e.g. where each default
has an 'if <some board>' condition. They are already safe.
6. Remove the prefer-later-defaults patch from Kconfiglib.
Testing was done with a Python script that lists all Kconfig
symbols/choices with multiple defaults, along with a whitelist of fixed
symbols. The script also verifies that there are no "unreachable"
defaults hidden by defaults without conditions
As an additional test, zephyr/.config was generated before and after the
change for several samples and checked to be identical (after sorting).
This commit includes some default-related cleanups as well:
- Simplify some symbol definitions, e.g. where a default has 'if FOO'
when the symbol already has 'depends on FOO'.
- Remove some redundant 'default ""' for string symbols. This is the
implicit default.
Piggyback fixes for swapped ranges on BT_L2CAP_RX_MTU and
BT_L2CAP_TX_MTU (caused by confusing inconsistency).
Piggyback some fixes for style nits too, e.g. unindented help texts.
Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2018-07-30 16:57:47 +08:00
|
|
|
|
2015-10-09 18:20:52 +08:00
|
|
|
config ARCH
|
|
|
|
|
default "arm"
|
2015-05-26 22:38:04 +08:00
|
|
|
|
2019-11-11 00:17:19 +08:00
|
|
|
config ARM64
|
|
|
|
|
bool
|
|
|
|
|
select 64BIT
|
|
|
|
|
|
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).
|
|
|
|
|
|
2016-03-15 10:51:58 +08:00
|
|
|
endmenu
|