michaelh/zephyr
1
0
Fork 0
Code Releases Activity

tracing: kconfig: move RAM_TRACING_BUFFER_SIZE out of choice

Browse source 
This kconfig is not a choice, it is an option needed by one of the
choices, so move it out.

Signed-off-by: Anas Nashif <anas.nashif@intel.com>
This commit is contained in:
Anas Nashif 2022-04-12 09:56:27 -04:00
commit 68670d71b8
1 changed files with 1 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

2
subsys/tracing/Kconfig
View file

@ -160,6 +160,7 @@ config TRACING_BACKEND_RAM
Use a ram buffer to output tracing data which can Use a ram buffer to output tracing data which can
be dumped to a file at runtime with a debugger. be dumped to a file at runtime with a debugger.
See gdb dump binary memory documentation for example. See gdb dump binary memory documentation for example.
endchoice
config RAM_TRACING_BUFFER_SIZE config RAM_TRACING_BUFFER_SIZE
int "Ram Tracing buffer size" int "Ram Tracing buffer size"
@ -169,7 +170,6 @@ config RAM_TRACING_BUFFER_SIZE
Size of the RAM trace buffer. Trace will be discarded if the Size of the RAM trace buffer. Trace will be discarded if the
length is exceeded. length is exceeded.
endchoice
config TRACING_BACKEND_UART_NAME config TRACING_BACKEND_UART_NAME
string "Device Name of UART Device for UART backend" string "Device Name of UART Device for UART backend"