zephyr/modules/segger/Kconfig

88 lines
2.2 KiB
Plaintext
Raw Permalink Normal View History

# Copyright (c) 2016 Nordic Semiconductor ASA
# SPDX-License-Identifier: Apache-2.0
config ZEPHYR_SEGGER_MODULE
bool
config HAS_SEGGER_RTT
bool
help
Indicates that the platform supports SEGGER J-Link RTT.
config USE_SEGGER_RTT
bool "SEGGER RTT libraries."
depends on HAS_SEGGER_RTT
select STM32_ENABLE_DEBUG_SLEEP_STOP if SOC_FAMILY_STM32
help
Enable Segger J-Link RTT libraries for platforms that support it.
Selection of this option enables use of RTT for various subsystems.
Note that by enabling this option, RTT buffers consume more RAM.
if USE_SEGGER_RTT
config SEGGER_RTT_CUSTOM_LOCKING
bool "Custom locking"
help
Enable custom locking using a mutex.
config SEGGER_RTT_MAX_NUM_UP_BUFFERS
int "Maximum number of up-buffers"
default 3
config SEGGER_RTT_MAX_NUM_DOWN_BUFFERS
int "Maximum number of down-buffers"
default 3
config SEGGER_RTT_BUFFER_SIZE_UP
int "Size of the buffer for terminal output of target, up to host"
default 1024
config SEGGER_RTT_BUFFER_SIZE_DOWN
int "Size of the buffer for terminal input of target, from host"
default 32 if SHELL_BACKEND_RTT
default 16
config SEGGER_RTT_PRINTF_BUFFER_SIZE
int "Size of buffer for RTT printf to bulk-send chars via RTT"
default 64
choice SEGGER_RTT_MODE
prompt "Mode for pre-initialized terminal channel (buffer 0)"
default SEGGER_RTT_MODE_NO_BLOCK_SKIP
config SEGGER_RTT_MODE_NO_BLOCK_SKIP
bool "Skip. Do not block, output nothing."
config SEGGER_RTT_MODE_NO_BLOCK_TRIM
bool "Trim: Do not block, output as much as fits."
config SEGGER_RTT_MODE_BLOCK_IF_FIFO_FULL
bool "Block: Wait until there is space in the buffer."
endchoice
config SEGGER_RTT_MODE
int
default 2 if SEGGER_RTT_MODE_BLOCK_IF_FIFO_FULL
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 10:57:47 +02:00
default 1 if SEGGER_RTT_MODE_NO_BLOCK_TRIM
default 0
config SEGGER_RTT_MEMCPY_USE_BYTELOOP
bool "Use a simple byte-loop instead of standard memcpy"
choice SEGGER_RTT_SECTION
prompt "Choose RTT data linker section"
config SEGGER_RTT_SECTION_NONE
bool "Place RTT data in the default linker section"
config SEGGER_RTT_SECTION_DTCM
bool "Place RTT data in the DTCM linker section"
config SEGGER_RTT_SECTION_CCM
bool "Place RTT data in the CCM linker section"
endchoice
endif