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

61 lines
1.9 KiB
Plaintext
Raw Normal View History

modules: move module kconfig to main tree Due to in-tree dependencies on Kconfig options defined in modules we end up having warnings and errors when those modules are not part of the manifest. Users should be able to remove unwanted modules from their downstream manifest and still build any board configurations. Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2019-05-24 05:19:41 +08:00
# Copyright (c) 2019 Intel Corporation
# SPDX-License-Identifier: Apache-2.0
modules: introducing MODULE_EXT_ROOT to allow glue code in Zephyr repo This commit introduces MODULE_EXT_ROOT which allows CMake and Kconfig glue code to be placed outside of the Zephyr module repository. This allows for placing glue code in Zephyr, but also allows users to specify custom MODULE_EXT_ROOTs for glue code using either `-DMODULE_EXT_ROOT` or `zephyr/module.yml` with `build:settings:module_ext_root` settings. MODULE_EXT_ROOT' is a list of directories, similar to other roots such as BOARD_ROOT, DTS_ROOT, etc. The Zephyr repo folder ${ZEPHYR_BASE} is always to the MODULE_EXT_ROOT list as lowest priority. For each MODULE_EXT_ROOT, the file `<module_ext_root>/modules/modules.cmake` will be processed. In Zephyr repo, the folder `modules/<module>/` contains CMakeLists.txt and Kconfig glue code for the Zephyr module. A Zephyr module can specify that CMakeLists.txt and Kconfig glue code is placed in an external module root by specifying: ``` build: cmake-ext: True kconfig-ext: True ``` It is still possible to place the CMakeLists.txt and Kconfig files directly in the Zephyr module using the existing: ``` build: cmake: <path> kconfig: <file> ```. Signed-off-by: Torsten Rasmussen <Torsten.Rasmussen@nordicsemi.no>
2020-12-17 18:27:42 +08:00
comment "Available modules."
source "$(KCONFIG_BINARY_DIR)/Kconfig.modules"
modules: move module kconfig to main tree Due to in-tree dependencies on Kconfig options defined in modules we end up having warnings and errors when those modules are not part of the manifest. Users should be able to remove unwanted modules from their downstream manifest and still build any board configurations. Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2019-05-24 05:19:41 +08:00
comment "Optional modules. Make sure they're installed, via the project manifest."
ext: hal: Remove Altera HAL from the tree and use a module Use an external Altera HAL repo instead of keeping a copy in ext/hal. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2020-03-20 02:19:00 +08:00
source "modules/Kconfig.altera"
kconfig: modules: Avoid including Kconfig.tls-generic twice The glob in modules/Kconfig accidentally picked up Kconfig.tls-generic, which is only supposed to be included from modules/Kconfig.mbedtls. Replace the globbing with explicit 'source's to fix it. Best to avoid globbing unless absolutely necessary, because it tends to pick up random non-checked-in files as well. Use 'source' instead of 'osource' since the files are known to exists. Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2020-02-07 10:38:12 +08:00
source "modules/Kconfig.atmel"
source "modules/Kconfig.canopennode"
source "modules/Kconfig.civetweb"
arm: Remove CMSIS from the tree and use a module Use an external CMSIS repo instead of keeping a copy in ext/hal. Closes #23373 Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2020-03-20 00:26:04 +08:00
source "modules/Kconfig.cmsis"
kconfig: modules: Avoid including Kconfig.tls-generic twice The glob in modules/Kconfig accidentally picked up Kconfig.tls-generic, which is only supposed to be included from modules/Kconfig.mbedtls. Replace the globbing with explicit 'source's to fix it. Best to avoid globbing unless absolutely necessary, because it tends to pick up random non-checked-in files as well. Use 'source' instead of 'osource' since the files are known to exists. Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2020-02-07 10:38:12 +08:00
source "modules/Kconfig.cypress"
modules: add Kconfig for QuickLogic EOS S3 module Add proper Kconfig for external QuickLogic module. Signed-off-by: Jan Kowalewski <jkowalewski@antmicro.com>
2020-02-04 18:35:50 +08:00
source "modules/Kconfig.eos_s3"
kconfig: modules: Avoid including Kconfig.tls-generic twice The glob in modules/Kconfig accidentally picked up Kconfig.tls-generic, which is only supposed to be included from modules/Kconfig.mbedtls. Replace the globbing with explicit 'source's to fix it. Best to avoid globbing unless absolutely necessary, because it tends to pick up random non-checked-in files as well. Use 'source' instead of 'osource' since the files are known to exists. Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2020-02-07 10:38:12 +08:00
source "modules/Kconfig.imx"
soc: arm: add infineon_xmc series support Add infineon xmc series with XMC4500 support. XMC series comes with, - CPU operates upto 120MHz - 3 RAM (PSRAM1 - code, DSRAM1 - data and DSRAM2 - communiation) - upto 1MB flash init: clock control & gpio is not done, so SoC initialization directly relies on HAL. Core operating clock is stored in no_init section, which is kept under DSRAM1. Only DSRAM1 is used until clock support. Using PSRAM1 and DSRAM1 needs adaptation in linker script - planned for next revision. Note: SystemInit cannot be consumed directly due to vector table + HAL linker dependency. Signed-off-by: Parthiban Nallathambi <parthiban@linumiz.com>
2020-04-21 17:37:42 +08:00
source "modules/Kconfig.infineon"
kconfig: modules: Avoid including Kconfig.tls-generic twice The glob in modules/Kconfig accidentally picked up Kconfig.tls-generic, which is only supposed to be included from modules/Kconfig.mbedtls. Replace the globbing with explicit 'source's to fix it. Best to avoid globbing unless absolutely necessary, because it tends to pick up random non-checked-in files as well. Use 'source' instead of 'osource' since the files are known to exists. Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2020-02-07 10:38:12 +08:00
source "modules/Kconfig.libmetal"
source "modules/Kconfig.loramac-node"
source "modules/Kconfig.mbedtls"
source "modules/Kconfig.mcux"
source "modules/Kconfig.microchip"
soc: arm: add support for nuvoton numicro m48x series Add initial support for nuvoton numicro m48x SoC series, basic init and uart functionality are covered with gpio and clock directly relies on HAL. Signed-off-by: Saravanan Sekar <saravanan@linumiz.com>
2020-04-15 16:04:50 +08:00
source "modules/Kconfig.nuvoton"
kconfig: modules: Avoid including Kconfig.tls-generic twice The glob in modules/Kconfig accidentally picked up Kconfig.tls-generic, which is only supposed to be included from modules/Kconfig.mbedtls. Replace the globbing with explicit 'source's to fix it. Best to avoid globbing unless absolutely necessary, because it tends to pick up random non-checked-in files as well. Use 'source' instead of 'osource' since the files are known to exists. Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2020-02-07 10:38:12 +08:00
source "modules/Kconfig.open-amp"
source "modules/Kconfig.silabs"
source "modules/Kconfig.simplelink"
modules: Add Sound Open Firmware module Add the Sound Open Firmware project as a Zephyr module under modules/audio/sof. Signed-off-by: Andy Ross <andrew.j.ross@intel.com> Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2020-06-26 08:30:00 +08:00
source "modules/Kconfig.sof"
kconfig: modules: Avoid including Kconfig.tls-generic twice The glob in modules/Kconfig accidentally picked up Kconfig.tls-generic, which is only supposed to be included from modules/Kconfig.mbedtls. Replace the globbing with explicit 'source's to fix it. Best to avoid globbing unless absolutely necessary, because it tends to pick up random non-checked-in files as well. Use 'source' instead of 'osource' since the files are known to exists. Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2020-02-07 10:38:12 +08:00
source "modules/Kconfig.st"
source "modules/Kconfig.stm32"
source "modules/Kconfig.syst"
trusted-firmware-m: Add initial plumbing for TFM This commits adds a config option to build a PSA trusted-firmware-m (TF-M) application image for the secure processing environment, and configures the Zephyr application image for the non-secure processing environment. The secure and non-secure environment images will be linked together via the veneer function table that is produced as an artifact of the TF-M build process. Signed-off-by: Karl Zhang <karl.zhang@linaro.org>
2020-05-08 21:22:52 +08:00
source "modules/Kconfig.tfm"
kconfig: modules: Avoid including Kconfig.tls-generic twice The glob in modules/Kconfig accidentally picked up Kconfig.tls-generic, which is only supposed to be included from modules/Kconfig.mbedtls. Replace the globbing with explicit 'source's to fix it. Best to avoid globbing unless absolutely necessary, because it tends to pick up random non-checked-in files as well. Use 'source' instead of 'osource' since the files are known to exists. Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2020-02-07 10:38:12 +08:00
source "modules/Kconfig.tinycbor"
ext: crypto: Remove TinyCrypt from the tree and use a module Use an external TinyCrypt repo instead of keeping a copy in ext/hal. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2020-03-20 19:11:33 +08:00
source "modules/Kconfig.tinycrypt"
kconfig: modules: Avoid including Kconfig.tls-generic twice The glob in modules/Kconfig accidentally picked up Kconfig.tls-generic, which is only supposed to be included from modules/Kconfig.mbedtls. Replace the globbing with explicit 'source's to fix it. Best to avoid globbing unless absolutely necessary, because it tends to pick up random non-checked-in files as well. Use 'source' instead of 'osource' since the files are known to exists. Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2020-02-07 10:38:12 +08:00
source "modules/Kconfig.vega"
source "modules/Kconfig.xtensa"
modules: introduce MCUBOOT_BOOTUTIL module Some parts of subsys/dfu/boot code are re-implementations of what is implemented in the MCUBoot repository. Mcuboot's repository already provide implementation of function required for application for interact with the MCUboot. This patch introduces new MCUBOOT_BOOTUTIL module which covers common code which is used in the bootloader and the chainnloaded application. dfu/boot: use MCUBoot's source code Module was reworked so it start using MCUBoot's bootutil_public API instead of copied code. Reworked boot_is_img_confirmed() used MCUBoot's API for determine image_ok flag. mcuboot_shell switchd to use MCUboot's boot_read_swap_state_by_id() This is MCUBoot function, use it for avoid linking conflict. test/subsys/mcuboot: fix `test_write_confirm` dfu/boot library was reworked so it uses MCUboot's bootutil_public library whenever it can. The library required that image was marked as copy-done before it can be pending. This patch adds such mark which fixes the test. Signed-off-by: Andrzej Puzdrowski <andrzej.puzdrowski@nordicsemi.no>
2020-11-13 00:59:59 +08:00
source "modules/Kconfig.mcuboot_bootutil"
modules: introducing MODULE_EXT_ROOT to allow glue code in Zephyr repo This commit introduces MODULE_EXT_ROOT which allows CMake and Kconfig glue code to be placed outside of the Zephyr module repository. This allows for placing glue code in Zephyr, but also allows users to specify custom MODULE_EXT_ROOTs for glue code using either `-DMODULE_EXT_ROOT` or `zephyr/module.yml` with `build:settings:module_ext_root` settings. MODULE_EXT_ROOT' is a list of directories, similar to other roots such as BOARD_ROOT, DTS_ROOT, etc. The Zephyr repo folder ${ZEPHYR_BASE} is always to the MODULE_EXT_ROOT list as lowest priority. For each MODULE_EXT_ROOT, the file `<module_ext_root>/modules/modules.cmake` will be processed. In Zephyr repo, the folder `modules/<module>/` contains CMakeLists.txt and Kconfig glue code for the Zephyr module. A Zephyr module can specify that CMakeLists.txt and Kconfig glue code is placed in an external module root by specifying: ``` build: cmake-ext: True kconfig-ext: True ``` It is still possible to place the CMakeLists.txt and Kconfig files directly in the Zephyr module using the existing: ``` build: cmake: <path> kconfig: <file> ```. Signed-off-by: Torsten Rasmussen <Torsten.Rasmussen@nordicsemi.no>
2020-12-17 18:27:42 +08:00
comment "Unavailable modules, please install those via the project manifest."
# List of comments to display when Zephyr modules are not available, please
# use the following syntax:
# ---------------------------------------------------
# comment "<module_name> module not available."
# depends on !ZEPHYR_<MODULE_NAME_UPPER>_MODULE
#
# Remember to add the following code inside the `<module>/Kconfig file:
# ---------------------------------------------------
# config ZEPHYR_<MODULE_NAME_UPPER>_MODULE
# bool
modules: Move nrfx glue code to main Zephyr repository Move nrfx glue code (nrfx integration files, related Kconfig entries, and related part of CMakeLists.txt taken from the hal_nordic module) to modules/hal_nordic/nrfx/ directory. CMakeLists.txt located in modules/hal_nordic/ is now the main cmake file for the hal_nordic module. It points back to cmake stuff related to the nRF IEEE 802.15.4 driver that still remains in that module and it adds the extracted nrfx part as a subdirectory. Kconfig.nordic is renamed to Kconfig and moved to modules/hal_nordic/. It sources nrfx related entries from that separate file. Update also the manifest to point to accordingly modified hal_nordic revision. Signed-off-by: Andrzej Głąbek <andrzej.glabek@nordicsemi.no>
2021-01-11 19:53:21 +08:00
comment "hal_nordic module not available."
depends on !ZEPHYR_HAL_NORDIC_MODULE
modules: introducing MODULE_EXT_ROOT to allow glue code in Zephyr repo This commit introduces MODULE_EXT_ROOT which allows CMake and Kconfig glue code to be placed outside of the Zephyr module repository. This allows for placing glue code in Zephyr, but also allows users to specify custom MODULE_EXT_ROOTs for glue code using either `-DMODULE_EXT_ROOT` or `zephyr/module.yml` with `build:settings:module_ext_root` settings. MODULE_EXT_ROOT' is a list of directories, similar to other roots such as BOARD_ROOT, DTS_ROOT, etc. The Zephyr repo folder ${ZEPHYR_BASE} is always to the MODULE_EXT_ROOT list as lowest priority. For each MODULE_EXT_ROOT, the file `<module_ext_root>/modules/modules.cmake` will be processed. In Zephyr repo, the folder `modules/<module>/` contains CMakeLists.txt and Kconfig glue code for the Zephyr module. A Zephyr module can specify that CMakeLists.txt and Kconfig glue code is placed in an external module root by specifying: ``` build: cmake-ext: True kconfig-ext: True ``` It is still possible to place the CMakeLists.txt and Kconfig files directly in the Zephyr module using the existing: ``` build: cmake: <path> kconfig: <file> ```. Signed-off-by: Torsten Rasmussen <Torsten.Rasmussen@nordicsemi.no>
2020-12-17 18:27:42 +08:00
# This ensures that symbols are available in Kconfig for dependency checking
# and referencing, while keeping the settings themselves unavailable when the
# modules are not present in the workspace
if 0
osource "modules/*/Kconfig"
endif