OrgZephyr/zephyr
OrgZephyr
/
zephyr
mirror of https://github.com/zephyrproject-rtos/zephyr.git
1
0
Fork 0
Code Issues Releases Wiki Activity
zephyr/soc/Kconfig

50 lines
1.0 KiB
Plaintext
Raw Normal View History

license: cleanup: add SPDX Apache-2.0 license identifier Update the files which contain no license information with the 'Apache-2.0' SPDX license identifier. Many source files in the tree are missing licensing information, which makes it harder for compliance tools to determine the correct license. By default all files without license information are under the default license of Zephyr, which is Apache version 2. Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2019-04-06 21:08:09 +08:00
# SPDX-License-Identifier: Apache-2.0
kconfig: move soc selection to ZEPHYR_BASE/soc/ Rather than do that for each architecture, source SoC Kconfigs where the code is maintained, under ZEPHYR_BASE/soc. Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2018-09-04 21:32:07 +08:00
choice
prompt "SoC/CPU/Configuration Selection"
cmake: kconfig: support for multiple SOC_ROOT This commit introduces support for multiple SOC_ROOT. This means that additional SOC_ROOTs specified using -DSOC_ROOT as argument to CMake will be forming a list together with ${ZEPHYR_BASE}. This allows for greater flexibility, as developers can now specify multiple out-of-tree SoCs and not worry about the SoC used for the board they compile for. Also it avoid code, such as: if(BOARD STREQUAL my_board_using_out_of_tree_soc) set(SOC_ROOT some/out/of/tree/soc/path) endif() in application CMakeLists.txt. Finally, allowing multiple SOC_ROOTs prepares for specifying SOC_ROOTs in Zephyr modules. Signed-off-by: Torsten Rasmussen <Torsten.Rasmussen@nordicsemi.no>
2020-07-06 18:53:39 +08:00
source "$(KCONFIG_BINARY_DIR)/Kconfig.soc"
kconfig: move soc selection to ZEPHYR_BASE/soc/ Rather than do that for each architecture, source SoC Kconfigs where the code is maintained, under ZEPHYR_BASE/soc. Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2018-09-04 21:32:07 +08:00
endchoice
menu "Hardware Configuration"
cmake: kconfig: support for multiple SOC_ROOT This commit introduces support for multiple SOC_ROOT. This means that additional SOC_ROOTs specified using -DSOC_ROOT as argument to CMake will be forming a list together with ${ZEPHYR_BASE}. This allows for greater flexibility, as developers can now specify multiple out-of-tree SoCs and not worry about the SoC used for the board they compile for. Also it avoid code, such as: if(BOARD STREQUAL my_board_using_out_of_tree_soc) set(SOC_ROOT some/out/of/tree/soc/path) endif() in application CMakeLists.txt. Finally, allowing multiple SOC_ROOTs prepares for specifying SOC_ROOTs in Zephyr modules. Signed-off-by: Torsten Rasmussen <Torsten.Rasmussen@nordicsemi.no>
2020-07-06 18:53:39 +08:00
source "$(KCONFIG_BINARY_DIR)/Kconfig.soc.arch"
kconfig: move soc selection to ZEPHYR_BASE/soc/ Rather than do that for each architecture, source SoC Kconfigs where the code is maintained, under ZEPHYR_BASE/soc. Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2018-09-04 21:32:07 +08:00
soc: logging: move soc tree to new logger Use the new logger framework for soc related code. Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2018-09-17 23:39:56 +08:00
module = SOC
module-str = SOC
source "subsys/logging/Kconfig.template.log_config"
kconfig: move soc selection to ZEPHYR_BASE/soc/ Rather than do that for each architecture, source SoC Kconfigs where the code is maintained, under ZEPHYR_BASE/soc. Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2018-09-04 21:32:07 +08:00
endmenu
soc: Kconfig: Add options for compatible NRF SOCs Simulated NRF boards based on the POSIX ARCH cannot directly use the current SOC_*NRF options as these pull options from the ARM CPU and other peripherals. This commit adds a new set of hidden SOC_COMPATIBLE_* options to be selected both by the real SOCs and the simulated ones. In this manner we can have the common code depend on the SOC_COMPATIBLE* options instead of the current ones where neccessary. Signed-off-by: Alberto Escolar Piedras <alpi@oticon.com> (f) arm kconfig
2018-10-03 21:51:11 +08:00
# The helper symbols below are put here due to an unusual setup: The simulated
# nrf52_bsim board uses the POSIX arch, but is compatible with Nordic ARM
# boards
config SOC_COMPATIBLE_NRF
bool
config SOC_COMPATIBLE_NRF52X
bool
config SOC_COMPATIBLE_NRF52832
bool
linker: allow SoC to insert linker script fragments This allows the SoC to specify some additional linker script fragments into the bss, data and read-only data sections. For example, the Cypress PSOC6 has a few input sections that must be put into bss and data sections. Without specifying these in the linker script, they are consider orphan sections and the placement is based on linker heuristic which is arbitrary. POSIX is not supported as the main linker script is provided by the host system's binutils and we have no control over it. Also, currently Xtensa SoCs have their own linker scripts so there is no need to this feature. Signed-off-by: Daniel Leung <daniel.leung@intel.com>
2018-10-20 01:15:19 +08:00
#
# SOC_*_LD: SoC specific Linker script additions
#
soc: kconfig: Simplify SOC_*_LD deps. with an 'if' 'if FOO' is equivalent to adding 'depends on FOO' to each item within the 'if'. Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2019-03-18 23:08:42 +08:00
soc: kconfig: add SOC_DEPRECATED_RELEASE Adding a Kconfig parameter so that we can indicate an SoC is to be deprecated, similar to what is being done for BOARD_DEPRECATED_RELEASE. Signed-off-by: Vincent Wan <vincent.wan@linaro.org>
2020-01-09 09:10:51 +08:00
config SOC_DEPRECATED_RELEASE
string
help
This hidden option is set in the SoC configuration and indicates
the Zephyr release that the SoC configuration will be removed.
When set, any build for that SoC will generate a clearly visible
deprecation warning.
timing: introduce timing functions as a generic feature Add timing functions and APIs. This is now used with some of the tests we have for performance and metrics and will be used whereever timing informations are needed, for example for tracing, profiling and other operations where timing info is critical. Signed-off-by: Daniel Leung <daniel.leung@intel.com> Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2020-08-06 03:57:00 +08:00
config SOC_HAS_TIMING_FUNCTIONS
bool
help
Should be selected if SoC provides custom method for retrieving
timestamps and cycle count.