michaelh/zephyr
1
0
Fork 0
Code Releases Activity
zephyr/Kconfig.zephyr

40 lines
730 B
Text
Raw Normal View History

Split main Kconfig to allow application specific Kconfig This will allow adding an application level Kconfig, for example mainmenu "Zephyr Application" config ZEPHYR_BASE string option env="ZEPHYR_BASE" config APPLICATION_BASE string option env="PROJECT_BASE" source "$ZEPHYR_BASE/Kconfig.zephyr" config TESTME bool "Test me" default y config BLAH bool "blah" default y source "$APPLICATION_BASE/src/Kconfig" In the application file, add the following for example: KBUILD_KCONFIG := $(PWD)/Kconfig export KBUILD_KCONFIG Change-Id: I7b7a6daace5f589ddadab0f0de54b5adc1b8dc86 Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2015-08-22 14:43:07 -04:00
# Kconfig - general configuration options
#
# Copyright (c) 2014-2015 Wind River Systems, Inc.
kconfig: untangle ordering and dependencies There are two major issues with the kconfig: () Some of the config options have incorrect dependencies inside help under menuconfig. For example, CONFIG_GPIO depends on BOARD_GALILEO. () Since the SoC and board specific kconfig files are parsed first, the help screen would say, for example, CONFIG_SPI is defined at arch/arm/soc/fsl_frdm_k64f/Kconfig. This is incorrect because the actual config is defined in drivers/spi/Kconfig. These cause great confusion to users of menuconfig/xconfig. To fix these, the SoC and board defaults are now to be parsed last. Note that the position swapping of defaults in this patch is due to the fact the the default parsed last will be used. And, spi_test is broken due to the fact that it requires CONFIG_SPI_INTEL_PORT_1, but never enables it anywhere. This is bypassed for now. Origin: refactored and edited from existing files Change-Id: I2a4b1ae5be4d27e68c960aa47d91ef350f2d500f Signed-off-by: Daniel Leung <daniel.leung@intel.com>
2016-03-25 14:30:50 -07:00
# Copyright (c) 2016 Intel Corporation
Split main Kconfig to allow application specific Kconfig This will allow adding an application level Kconfig, for example mainmenu "Zephyr Application" config ZEPHYR_BASE string option env="ZEPHYR_BASE" config APPLICATION_BASE string option env="PROJECT_BASE" source "$ZEPHYR_BASE/Kconfig.zephyr" config TESTME bool "Test me" default y config BLAH bool "blah" default y source "$APPLICATION_BASE/src/Kconfig" In the application file, add the following for example: KBUILD_KCONFIG := $(PWD)/Kconfig export KBUILD_KCONFIG Change-Id: I7b7a6daace5f589ddadab0f0de54b5adc1b8dc86 Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2015-08-22 14:43:07 -04:00
#
license: Replace Apache boilerplate with SPDX tag Replace the existing Apache 2.0 boilerplate header with an SPDX tag throughout the zephyr code tree. This patch was generated via a script run over the master branch. Also updated doc/porting/application.rst that had a dependency on line numbers in a literal include. Manually updated subsys/logging/sys_log.c that had a malformed header in the original file. Also cleanup several cases that already had a SPDX tag and we either got a duplicate or missed updating. Jira: ZEP-1457 Change-Id: I6131a1d4ee0e58f5b938300c2d2fc77d2e69572c Signed-off-by: David B. Kinder <david.b.kinder@intel.com> Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
2017-01-18 17:01:01 -08:00
# SPDX-License-Identifier: Apache-2.0
Split main Kconfig to allow application specific Kconfig This will allow adding an application level Kconfig, for example mainmenu "Zephyr Application" config ZEPHYR_BASE string option env="ZEPHYR_BASE" config APPLICATION_BASE string option env="PROJECT_BASE" source "$ZEPHYR_BASE/Kconfig.zephyr" config TESTME bool "Test me" default y config BLAH bool "blah" default y source "$APPLICATION_BASE/src/Kconfig" In the application file, add the following for example: KBUILD_KCONFIG := $(PWD)/Kconfig export KBUILD_KCONFIG Change-Id: I7b7a6daace5f589ddadab0f0de54b5adc1b8dc86 Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2015-08-22 14:43:07 -04:00
#
kconfig: define architecture as a kconfig variable Do not depend on environment variables and use a kconfig variable for defining the architecture. In addition, remove the X86_32 variable, it just duplicates X86 for not good reason, at least until start supporting MCUs with 64bit. Change-Id: Ia001db81ed007e6a43f34506fed9be1345b88a4b Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2015-10-09 06:20:52 -04:00
config KERNELVERSION
Cleanup whitespace in Kconfig files Convert leading whitespace into tabs in Kconfig files. Also replaced double spaces between config and <prompt>. Change-Id: I341c718ecf4143529b477c239bbde88e18f37062 Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
2016-05-24 18:17:13 -05:00
string
option env="KERNELVERSION"
Split main Kconfig to allow application specific Kconfig This will allow adding an application level Kconfig, for example mainmenu "Zephyr Application" config ZEPHYR_BASE string option env="ZEPHYR_BASE" config APPLICATION_BASE string option env="PROJECT_BASE" source "$ZEPHYR_BASE/Kconfig.zephyr" config TESTME bool "Test me" default y config BLAH bool "blah" default y source "$APPLICATION_BASE/src/Kconfig" In the application file, add the following for example: KBUILD_KCONFIG := $(PWD)/Kconfig export KBUILD_KCONFIG Change-Id: I7b7a6daace5f589ddadab0f0de54b5adc1b8dc86 Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2015-08-22 14:43:07 -04:00
kconfig: define architecture as a kconfig variable Do not depend on environment variables and use a kconfig variable for defining the architecture. In addition, remove the X86_32 variable, it just duplicates X86 for not good reason, at least until start supporting MCUs with 64bit. Change-Id: Ia001db81ed007e6a43f34506fed9be1345b88a4b Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2015-10-09 06:20:52 -04:00
source "arch/Kconfig"
Split main Kconfig to allow application specific Kconfig This will allow adding an application level Kconfig, for example mainmenu "Zephyr Application" config ZEPHYR_BASE string option env="ZEPHYR_BASE" config APPLICATION_BASE string option env="PROJECT_BASE" source "$ZEPHYR_BASE/Kconfig.zephyr" config TESTME bool "Test me" default y config BLAH bool "blah" default y source "$APPLICATION_BASE/src/Kconfig" In the application file, add the following for example: KBUILD_KCONFIG := $(PWD)/Kconfig export KBUILD_KCONFIG Change-Id: I7b7a6daace5f589ddadab0f0de54b5adc1b8dc86 Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2015-08-22 14:43:07 -04:00
kconfig: define architecture as a kconfig variable Do not depend on environment variables and use a kconfig variable for defining the architecture. In addition, remove the X86_32 variable, it just duplicates X86 for not good reason, at least until start supporting MCUs with 64bit. Change-Id: Ia001db81ed007e6a43f34506fed9be1345b88a4b Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2015-10-09 06:20:52 -04:00
source "kernel/Kconfig"
Split main Kconfig to allow application specific Kconfig This will allow adding an application level Kconfig, for example mainmenu "Zephyr Application" config ZEPHYR_BASE string option env="ZEPHYR_BASE" config APPLICATION_BASE string option env="PROJECT_BASE" source "$ZEPHYR_BASE/Kconfig.zephyr" config TESTME bool "Test me" default y config BLAH bool "blah" default y source "$APPLICATION_BASE/src/Kconfig" In the application file, add the following for example: KBUILD_KCONFIG := $(PWD)/Kconfig export KBUILD_KCONFIG Change-Id: I7b7a6daace5f589ddadab0f0de54b5adc1b8dc86 Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2015-08-22 14:43:07 -04:00
kconfig: define architecture as a kconfig variable Do not depend on environment variables and use a kconfig variable for defining the architecture. In addition, remove the X86_32 variable, it just duplicates X86 for not good reason, at least until start supporting MCUs with 64bit. Change-Id: Ia001db81ed007e6a43f34506fed9be1345b88a4b Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2015-10-09 06:20:52 -04:00
source "drivers/Kconfig"
Split main Kconfig to allow application specific Kconfig This will allow adding an application level Kconfig, for example mainmenu "Zephyr Application" config ZEPHYR_BASE string option env="ZEPHYR_BASE" config APPLICATION_BASE string option env="PROJECT_BASE" source "$ZEPHYR_BASE/Kconfig.zephyr" config TESTME bool "Test me" default y config BLAH bool "blah" default y source "$APPLICATION_BASE/src/Kconfig" In the application file, add the following for example: KBUILD_KCONFIG := $(PWD)/Kconfig export KBUILD_KCONFIG Change-Id: I7b7a6daace5f589ddadab0f0de54b5adc1b8dc86 Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2015-08-22 14:43:07 -04:00
kconfig: define architecture as a kconfig variable Do not depend on environment variables and use a kconfig variable for defining the architecture. In addition, remove the X86_32 variable, it just duplicates X86 for not good reason, at least until start supporting MCUs with 64bit. Change-Id: Ia001db81ed007e6a43f34506fed9be1345b88a4b Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2015-10-09 06:20:52 -04:00
source "net/Kconfig"
source "misc/Kconfig"
Split main Kconfig to allow application specific Kconfig This will allow adding an application level Kconfig, for example mainmenu "Zephyr Application" config ZEPHYR_BASE string option env="ZEPHYR_BASE" config APPLICATION_BASE string option env="PROJECT_BASE" source "$ZEPHYR_BASE/Kconfig.zephyr" config TESTME bool "Test me" default y config BLAH bool "blah" default y source "$APPLICATION_BASE/src/Kconfig" In the application file, add the following for example: KBUILD_KCONFIG := $(PWD)/Kconfig export KBUILD_KCONFIG Change-Id: I7b7a6daace5f589ddadab0f0de54b5adc1b8dc86 Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2015-08-22 14:43:07 -04:00
tinycrypt: move from lib to regular objects tinycrypt was built using the lib- scripts without any real benefit. We also had a wrong placement of the Kconfig files under misc/ and a Kconfig file for Crypto that was never used before. Change-Id: I82d5902d92e7c06e10a95f418d9ead3cbcabcce4 Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2016-05-14 23:10:51 -04:00
source "lib/Kconfig"
fs: Move file system code to subsys/ Subsystems code will reside in subsys/ folder. This patch creates the folder and moves FS code there. Jira: ZEP-1120 Change-Id: If3b1bcb996c5fbd4056cd5d1920d41d29810d6b2 Signed-off-by: Ramesh Thomas <ramesh.thomas@intel.com>
2016-10-29 04:10:36 -07:00
source "subsys/Kconfig"
fs: Adds diskio interface Adds the diskio interface for the FAT file system. This revision uses RAM to emulate disk storage. Origin: Original Jira: ZEP-285 Change-Id: I7a30c8761d5ed9b564f1d1e08482c5ef199d7372 Signed-off-by: Ramesh Thomas <ramesh.thomas@intel.com>
2016-07-25 16:20:54 -07:00
ext: plumb out Kconfig support for external source code Add missing Kconfig files and connections to expose Kconfig options in ext/ directories. Fixup QMSI to only be exposed on platforms that utilize it. Change-Id: I6c6c5011b2bf2966f65aa8279dc594a244821956 Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
2016-05-24 14:23:26 -05:00
source "ext/Kconfig"
tests: Add a generic testing framework This framework makes testing in most parts a lot easier, since it gives an unified base to work with, removing a lot of unnecessary code from tests. This framework currently features simple assertions and basic mocking support. The framework works both with and without Zephyr running, so it can be used for real unit testing. Origin: Original Change-Id: I8c5bf2e6b8d6656b6197ee91699b61e730c1cfe3 Signed-off-by: Jaakko Hannikainen <jaakko.hannikainen@intel.com> Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2016-08-22 14:51:46 +03:00
source "tests/Kconfig"
kconfig: untangle ordering and dependencies There are two major issues with the kconfig: () Some of the config options have incorrect dependencies inside help under menuconfig. For example, CONFIG_GPIO depends on BOARD_GALILEO. () Since the SoC and board specific kconfig files are parsed first, the help screen would say, for example, CONFIG_SPI is defined at arch/arm/soc/fsl_frdm_k64f/Kconfig. This is incorrect because the actual config is defined in drivers/spi/Kconfig. These cause great confusion to users of menuconfig/xconfig. To fix these, the SoC and board defaults are now to be parsed last. Note that the position swapping of defaults in this patch is due to the fact the the default parsed last will be used. And, spi_test is broken due to the fact that it requires CONFIG_SPI_INTEL_PORT_1, but never enables it anywhere. This is bypassed for now. Origin: refactored and edited from existing files Change-Id: I2a4b1ae5be4d27e68c960aa47d91ef350f2d500f Signed-off-by: Daniel Leung <daniel.leung@intel.com>
2016-03-25 14:30:50 -07:00
#
# The following are for Kconfig files for default values only.
# These should be parsed at the end.
#
parse board defconfig at the very end The board defconfig is useless if it does not override what the SoC sets. Boards can have different values than those set by the SoC. Change-Id: Iab287c62986b20585b4df3e77bd973dbab50eea4 Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2016-09-10 09:55:55 -04:00
# Board defaults should be parsed after SoC defaults
# because board usually overrides SoC values.
kconfig: untangle ordering and dependencies There are two major issues with the kconfig: () Some of the config options have incorrect dependencies inside help under menuconfig. For example, CONFIG_GPIO depends on BOARD_GALILEO. () Since the SoC and board specific kconfig files are parsed first, the help screen would say, for example, CONFIG_SPI is defined at arch/arm/soc/fsl_frdm_k64f/Kconfig. This is incorrect because the actual config is defined in drivers/spi/Kconfig. These cause great confusion to users of menuconfig/xconfig. To fix these, the SoC and board defaults are now to be parsed last. Note that the position swapping of defaults in this patch is due to the fact the the default parsed last will be used. And, spi_test is broken due to the fact that it requires CONFIG_SPI_INTEL_PORT_1, but never enables it anywhere. This is bypassed for now. Origin: refactored and edited from existing files Change-Id: I2a4b1ae5be4d27e68c960aa47d91ef350f2d500f Signed-off-by: Daniel Leung <daniel.leung@intel.com>
2016-03-25 14:30:50 -07:00
#
source "arch/*/soc/*/Kconfig.defconfig"
board: organize boards based on architecture Introduce an architecture sorting of boards. This is to allow for easier maintenance going forward as the number of boards grows. It will be easier for any scripts to know the board/arch mapping without having to maintain an explicit list of what boards are associated with which arch. We can also do things like have architecture maintainers cover reviews and branches for arch/${ARCH} and boards/${ARCH} going forward. Change-Id: I02e0a30292b31fad58fb5dfab2682ad1c5a7d5a7 Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
2016-10-19 15:13:41 -05:00
source "boards/*/*/Kconfig.defconfig"
Copy permalink