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

132 lines
4.2 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 CONFIG_BOARD to boards/Kconfig Moving this option to the subdirectory for boards might make it easier to find, and will keep it next to some other board-related Kconfig options set in the same file. Signed-off-by: Martí Bolívar <marti.bolivar@nordicsemi.no>
2022-04-09 00:08:48 +08:00
config BOARD
string
help
This option holds the name of the board and is used to locate the files
related to the board in the source tree (under boards/).
The Board is the first location where we search for a linker.ld file,
if not found we look for the linker file in
soc/<arch>/<family>/<series>
Kconfig: add CONFIG_BOARD_REVISION Propagate the board revision to Kconfig via the environment. This is useful for application code to have access to for similar reasons that CONFIG_BOARD is useful. Signed-off-by: Martí Bolívar <marti.bolivar@nordicsemi.no>
2022-04-08 02:21:18 +08:00
config BOARD_REVISION
def_string "$BOARD_REVISION"
help
If the BOARD has a revision field set, this is the revision.
Otherwise, it is the empty string. For example, if BOARD is
"plank@foo", this option will be "foo". If BOARD is "plank",
this option will be the empty string.
boards: Kconfig: rename BOARD_DEPRECATED to BOARD_DEPRECATED_RELEASE Renaming this Kconfig option given it corresponds to a version string for a particular release. Signed-off-by: Vincent Wan <vincent.wan@linaro.org>
2020-01-10 06:20:44 +08:00
config BOARD_DEPRECATED_RELEASE
build: add Kconfig mechanism for deprecating boards If a deprecated board is built, a warning is presented indicating what future release the board will be removed. Change-Id: Ib166198d8b71303b990a30f79429f51871591a97 Signed-off-by: Andrew Boie <andrew.p.boie@intel.com>
2016-10-20 04:05:35 +08:00
string
help
kconfig: fix help syntax and add spaces Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2017-12-13 23:08:21 +08:00
This hidden option is set in the board configuration and indicates
the Zephyr release that the board configuration will be removed.
When set, any build for that board will generate a clearly visible
deprecation warning.
build: add Kconfig mechanism for deprecating boards If a deprecated board is built, a warning is presented indicating what future release the board will be removed. Change-Id: Ib166198d8b71303b990a30f79429f51871591a97 Signed-off-by: Andrew Boie <andrew.p.boie@intel.com>
2016-10-20 04:05:35 +08:00
boards: mark qemu targets with a unified Kconfig This will allow checking if we are building for QEMU globally, without having to know the exact architecture and board name. Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2017-07-26 20:08:21 +08:00
config QEMU_TARGET
boards: Fix QEMU_TARGET config prompt and default The default boolean setting for QEMU_TARGET was incorrectly placed in the prompt field, so it was showing up as a config option in 'make menuconfig' when it should be hidden. Signed-off-by: Maureen Helm <maureen.helm@nxp.com>
2017-08-01 04:38:03 +08:00
bool
boards: mark qemu targets with a unified Kconfig This will allow checking if we are building for QEMU globally, without having to know the exact architecture and board name. Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2017-07-26 20:08:21 +08:00
help
Mark all QEMU targets with this variable for checking whether we are
running in an emulated environment.
drivers: net: adding NET_DRIVERS menuconfig Fixes: #38403 Adding NET_DRIVERS menuconfig so that network drivers are grouped together in its own menu entry under drivers, similar to most other drivers. This further has the advantages that `CONFIG_NET_DRIVERS` can be used for testing to determine if network drivers has been selected. This changed revealed a dependency loop where both `select` (for SLIP) and `depends` (for PPP) which both depends on NET_DRIVERS` where in use in the dependency tree for Qemu networking, especially NET_SLIP_TAP. This is handled by defaulting `NET_DRIVERS` to `y` when building for a Qemu target. `SLIP` had a dependency to `!QEMU_TARGET || NET_QEMU_SLIP`. This is changed so that SLIP prompt depends on `!QEMU_TARGET` which provides full user control in hardware but makes the symbol promptless on Qemu targets. Signed-off-by: Torsten Rasmussen <Torsten.Rasmussen@nordicsemi.no>
2021-09-10 21:53:31 +08:00
config NET_DRIVERS
bool
default y if QEMU_TARGET && NETWORKING
help
When building for a qemu target then NET_DRIVERS will be default
enabled to allow for easy use of SLIP or PPP
Kconfig: Rename $ENV_VAR_{ARCH,BOARD_DIR} to $ARCH/$BOARD_DIR The prefixes might be a leftover from the old 'option env="..."' symbols (which are no longer needed). Since environment variables can be referenced directly now, there's no point in having a prefix. Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2018-09-05 18:58:05 +08:00
# Note: $BOARD_DIR might be a glob pattern
kconfig: Make 'source' non-globbing and use 'gsource' Until now, Zephyr has used a patched Kconfiglib that turns 'source' into a globbing source (by replacing 'source' with 'gsource' at the token level). There's two problems with this: - The patch needs to be maintained separately - Misspelled filenames are silently ignored, as they look like glob patterns that don't match anything Fix it as follows: 1. Replace all 'source' statements that use wildcards with 'gsource' 2. Remove the custom Kconfiglib patch so that 'source' no longer globs The sed pattern '/source.*[*?]/s/source/gsource/' was run over all Kconfig* files to do the replacement. source's that use environment variables that might contain glob patterns were manually changed to gsource. Building the docs in doc/ is a good test, as doc/Makefile deliberately sets the environment variables to glob up as many Kconfig files as possible. Signed-off-by: Ulf Magnusson <ulfalizer@gmail.com>
2018-05-08 15:31:48 +08:00
kconfig: add board configurations First step for adding the new board layer. Create configurations for the various boards we support on x86 under boards with the new Kconfig variables defining them. The board selection is optional, that means you will be able to run make menuconfig and create your own .config and select any SoC. Change-Id: If08e88e9675d13f0f0501ef6750b9424b15f5dc8 Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2015-12-13 18:54:28 +08:00
choice
kconfig: Global whitespace/consistency cleanup Clean up space errors and use a consistent style throughout the Kconfig files. This makes reading the Kconfig files more distraction-free, helps with grepping, and encourages the same style getting copied around everywhere (meaning another pass hopefully won't be needed). Go for the most common style: - Indent properties with a single tab, including for choices. Properties on choices work exactly the same syntactically as properties on symbols, so not sure how the no-indentation thing happened. - Indent help texts with a tab followed by two spaces - Put a space between 'config' and the symbol name, not a tab. This also helps when grepping for definitions. - Do '# A comment' instead of '#A comment' I tweaked Kconfiglib a bit to find most of the stuff. Some help texts were reflowed to 79 columns with 'gq' in Vim as well, though not all, because I was afraid I'd accidentally mess up formatting. Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2019-11-01 17:24:07 +08:00
prompt "Board Selection"
Kconfig: Use new preprocessor syntax for env. variables With the new Kconfig preprocessor (described in https://github.com/torvalds/linux/blob/master/Documentation/kbuild/ kconfig-macro-language.txt), the syntax for expanding environment variables is $(FOO) rather than $FOO. $(FOO) is a general preprocessor variable expansion, which falls back to environment variables if the variable isn't set (like in Make). It can also be used in prompts, 'comment's, etc. The old syntax will probably be supported forever in Kconfiglib for backwards compatibility, but might as well make it consistent now that people might start using the preprocessor more. Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2018-09-05 19:10:19 +08:00
source "$(BOARD_DIR)/Kconfig.board"
kconfig: Global whitespace/consistency cleanup Clean up space errors and use a consistent style throughout the Kconfig files. This makes reading the Kconfig files more distraction-free, helps with grepping, and encourages the same style getting copied around everywhere (meaning another pass hopefully won't be needed). Go for the most common style: - Indent properties with a single tab, including for choices. Properties on choices work exactly the same syntactically as properties on symbols, so not sure how the no-indentation thing happened. - Indent help texts with a tab followed by two spaces - Put a space between 'config' and the symbol name, not a tab. This also helps when grepping for definitions. - Do '# A comment' instead of '#A comment' I tweaked Kconfiglib a bit to find most of the stuff. Some help texts were reflowed to 79 columns with 'gq' in Vim as well, though not all, because I was afraid I'd accidentally mess up formatting. Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2019-11-01 17:24:07 +08:00
kconfig: add board configurations First step for adding the new board layer. Create configurations for the various boards we support on x86 under boards with the new Kconfig variables defining them. The board selection is optional, that means you will be able to run make menuconfig and create your own .config and select any SoC. Change-Id: If08e88e9675d13f0f0501ef6750b9424b15f5dc8 Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2015-12-13 18:54:28 +08:00
endchoice
boards: Kconfig: Enable use of shield conditional Kconfig files To make use of shields Kconfig.defconfig, parse these files and newly created Kconfig.shield files which will define the SHIELD_XXX Kconfig symbols that will be used for conditional configuration. Signed-off-by: Erwan Gouriou <erwan.gouriou@linaro.org>
2019-11-22 17:37:01 +08:00
# Parse shields references
# Don't do it as a menuconfig, as shield selection is a CMake feature.
kconfig: soc and shield cleanup Always source the Zephyr base soc and shield (board root) Kconfigs directly from Kconfig instead of generated Kconfig files. This has the benefit that it is no longer necessary to generate Kconfig files to source SoC root and shield (board root) when no custom roots are provided. Also this cleans up the doc/CMakeLists.txt and ensures that the doc/CMakeLists.txt is not getting out of sync with the Kconfig.cmake. Signed-off-by: Torsten Rasmussen <Torsten.Rasmussen@nordicsemi.no>
2021-06-02 14:47:21 +08:00
# This loads custom shields Kconfig (from BOARD_ROOT)
osource "$(KCONFIG_BINARY_DIR)/Kconfig.shield"
# This loads Zephyr base shield defconfigs
rsource "shields/*/Kconfig.shield"
kconfig: add board configurations First step for adding the new board layer. Create configurations for the various boards we support on x86 under boards with the new Kconfig variables defining them. The board selection is optional, that means you will be able to run make menuconfig and create your own .config and select any SoC. Change-Id: If08e88e9675d13f0f0501ef6750b9424b15f5dc8 Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2015-12-13 18:54:28 +08:00
boards: add a menu surrounding board Kconfig This adds a menu to enclose all board Kconfig. So the board configs do not appear on the top level out of context in menuconfig. This also reflects the SoC options where these are under menus for each architecture. Change-Id: I76ce2bf1acf7cbd2673ceb2eac71e96cdca2ff35 Signed-off-by: Daniel Leung <daniel.leung@intel.com>
2016-03-16 01:27:39 +08:00
menu "Board Options"
boards: remove the existing qemu icount configuration Remove the existing qemu icount configuration because icount mode will be controlled by Kconfig QEMU_ICOUNT so that none suitable cases(especially networking cases) can exclude icount configuration Signed-off-by: Wentong Wu <wentong.wu@intel.com>
2020-05-12 08:44:51 +08:00
config QEMU_ICOUNT
bool "QEMU icount mode"
depends on QEMU_TARGET
boards: kconfig: Disable QEMU icount when Bluetooth is enabled Bluetooth interacts with real-world hardware and thus requires the QEMU target to follow wall time, and not have a free running timer that is much faster than actual wall time. Diable the QEMU icount mechanism when Bluetooth is enabled. Fixes #26242 Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2020-06-17 23:26:51 +08:00
default y if !NETWORKING && !BT
boards: remove the existing qemu icount configuration Remove the existing qemu icount configuration because icount mode will be controlled by Kconfig QEMU_ICOUNT so that none suitable cases(especially networking cases) can exclude icount configuration Signed-off-by: Wentong Wu <wentong.wu@intel.com>
2020-05-12 08:44:51 +08:00
help
Enable QEMU virtual instruction counter. The virtual cpu will
execute one instruction every 2^N ns of virtual time. This will
give deterministic execution times from the guest point of view.
boards: centralize QEMU icount management Instead of endlessly repeating the same command line args, centralize this and tune the shift value on a per-board basis. Signed-off-by: Andrew Boie <andrew.p.boie@intel.com>
2020-05-20 03:24:25 +08:00
config QEMU_ICOUNT_SHIFT
int "QEMU icount shift value"
depends on QEMU_ICOUNT
help
The virtual CPU will execute one instruction every 2^N nanoseconds
of virtual time, where N is the value provided here.
cmake: boards: make QEMU icount sleep parameter configurable When QEMU is running in icount mode, the behaviour regarding the CPU being in sleep mode is configurable, with the default value being set to 'off'. In this case, instruction counting continues even when the CPU is sleeping or no target time is set in the system timer. If the sleep parameter is set to 'on', instruction counting stops if the CPU is sleeping, and the instruction count will fast-forward directly to the next target time once it is being set. In the Xilinx derivative of QEMU (which simulates ZynqMP and Zynq-7000 SoCs), the default configuration causes QEMU to no longer accept control commands via the console or remotely whenever Zephyr enters and remains in idle mode. Therefore, this commit makes the value of the sleep para- meter of the icount functionality configurable, with the default value remaining 'off'. The value can be changed at board level alongside with the specification of the icount shift value. Signed-off-by: Immo Birnbaum <Immo.Birnbaum@Weidmueller.com>
2021-10-15 17:45:11 +08:00
config QEMU_ICOUNT_SLEEP
bool "QEMU icount sleep mode enable"
depends on QEMU_ICOUNT
help
When the virtual CPU is sleeping, the virtual time will advance
at default speed unless this option is set. With this option set,
the virtual time will jump to the next timer deadline instantly
whenever the virtual CPU goes to sleep mode and will not advance
if no timer is enabled. This behavior gives deterministic execution
times from the guest point of view.
cmake: Adds the necessary flags support for Qemu ivshmem feature Depending whether doorbell or plain versions are enabled, it will set the right flags to qemu. Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
2020-12-11 16:52:09 +08:00
config QEMU_IVSHMEM_PLAIN_MEM_SIZE
int "QEMU ivshmem-plain shared memory size in mega-bytes"
default 1
depends on QEMU_TARGET && IVSHMEM && !IVSHMEM_DOORBELL
help
This sets the size of the shared memory when using ivshmem-plain
device in Qemu. Note that it's in mega-bytes, so 1 means 1M for Qemu
etc..
tests: add a test to verify UEFI boot on x86_64 targets. add a config CONFIG_QEMU_UEFI_BOOT to indicate whether the qemu will use UEFI bootable method; add a new test "sample.basic.helloworld.uefi" to verify UEFT bootable method on qemu_x86_64 platform. Signed-off-by: Chen Peng1 <peng1.chen@intel.com>
2021-07-29 00:15:24 +08:00
config QEMU_UEFI_BOOT
bool "QEMU uses UEFI to boot up"
default n
depends on BUILD_OUTPUT_EFI && QEMU_TARGET && X86_64
help
This option indicates that QEMU will use UEFI bootable method
to boot up.
boards: kconfig: qemu: introduce QEMU_GDBSERVER_LISTEN_DEV Introduce new string option to pass into QEMU invocation so that gdbserver listeners other than `-s` (tcp::1234) can be set. Signed-off-by: Alp Sayin <alpsayin@gmail.com>
2023-01-30 21:09:18 +08:00
config QEMU_GDBSERVER_LISTEN_DEV
string "QEMU gdbserver listen device"
default "tcp::1234"
depends on QEMU_TARGET
help
This options is passed onto QEMU as a parameter to `-gdb` option.
The default value is equivalent to `-s` which is a shorthand for
`-gdb tcp::1234`. An empty value omits the `-gdb` parameter altogether.
This allows the injection of `-gdb` parameter from other sources such
as the `QEMU_EXTRA_FLAGS` environment variable. Refer to application
development doc and/or QEMU invocation doc for more info.
config: qemu: Add QEMU_EXTRA_FLAGS config option Add QEMU_EXTRA_FLAGS as QEMU board config option. This allows Twister tests to provide additional device setup commands to QEMU in prj.conf or testcase.yaml configuration files. Example use case: to setup TCP or UDP network interfaces with non-conflicting port numbers in different test suites to avoid conflicts when Twister run tests in parallel on the same host. Signed-off-by: Dmitrii Golovanov <dmitrii.golovanov@intel.com>
2023-10-09 20:57:39 +08:00
config QEMU_EXTRA_FLAGS
string "QEMU extra flags"
depends on QEMU_TARGET
default ""
help
This option is to pass onto QEMU an extra list of parameters
to setup devices, for example to allocate interface for Zephyr
GDBstub over serial with `-serial tcp:127.0.0.1:5678,server`
Kconfig: Switch to improved globbing statements A design flaw of 'gsource' is that there's no way to require at least one file to match the glob pattern. This could lead to silent errors. Switch to a new design, where a plain 'source' is globbing and requires at least one file to match. A separate 'osource' (optional source) statement is available for cases where it's okay for a pattern (or plain filename) to not match any files. 'orsource' combines 'osource' and 'rsource' (relative source). This commit search-replaces 'gsource' with 'source', but backwards compatibility with 'gsource' is still maintained by making it an alias for 'osource' (and by making 'grsource' an alias for 'orsource'). The three Kconfig files arch/{nios2,posix,xtensa}/Kconfig source arch/{nios2,posix,xtensa}/soc/*/Kconfig, which doesn't match any files. Use 'osource' for those. The soc/*/Kconfig files seem to be for additional SoC-specific symbols, only none exist yet on those ARCHes. Also use 'osource' for the source of $ENV_VAR_BOARD_DIR/Kconfig in boards/Kconfig, which doesn't exist for all boards. Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2018-08-14 13:20:30 +08:00
# There might not be any board options, hence the optional source
Kconfig: Use new preprocessor syntax for env. variables With the new Kconfig preprocessor (described in https://github.com/torvalds/linux/blob/master/Documentation/kbuild/ kconfig-macro-language.txt), the syntax for expanding environment variables is $(FOO) rather than $FOO. $(FOO) is a general preprocessor variable expansion, which falls back to environment variables if the variable isn't set (like in Make). It can also be used in prompts, 'comment's, etc. The old syntax will probably be supported forever in Kconfiglib for backwards compatibility, but might as well make it consistent now that people might start using the preprocessor more. Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2018-09-05 19:10:19 +08:00
osource "$(BOARD_DIR)/Kconfig"
boards: add a menu surrounding board Kconfig This adds a menu to enclose all board Kconfig. So the board configs do not appear on the top level out of context in menuconfig. This also reflects the SoC options where these are under menus for each architecture. Change-Id: I76ce2bf1acf7cbd2673ceb2eac71e96cdca2ff35 Signed-off-by: Daniel Leung <daniel.leung@intel.com>
2016-03-16 01:27:39 +08:00
endmenu
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 BOARD_HAS_TIMING_FUNCTIONS
bool
help
Should be selected if board provides custom method for retrieving
timestamps and cycle count.