mirror of https://github.com/thesofproject/sof.git
kconfig: move XTOS build specific debug options to a separate file
Some of the DEBUG options are only used in the XTOS implementation and do not impact e.g. Zephyr builds. Make the split explicit by moving these options to a separate file. Signed-off-by: Kai Vehmanen <kai.vehmanen@linux.intel.com>
This commit is contained in:
parent
ffe22f2831
commit
3541b37d46
19
Kconfig
19
Kconfig
|
@ -133,12 +133,6 @@ config GDB_DEBUG
|
|||
help
|
||||
Select for GDB debugging
|
||||
|
||||
config DEBUG_HEAP
|
||||
bool "Heap debug"
|
||||
default n
|
||||
help
|
||||
Select for enable heap alloc debugging
|
||||
|
||||
config DEBUG_MEMORY_USAGE_SCAN
|
||||
bool "Memory usage scan"
|
||||
default y
|
||||
|
@ -147,15 +141,6 @@ config DEBUG_MEMORY_USAGE_SCAN
|
|||
This feature does not affect standard memory operations,
|
||||
especially allocation and deallocation.
|
||||
|
||||
config DEBUG_BLOCK_FREE
|
||||
bool "Blocks freeing debug"
|
||||
default n
|
||||
help
|
||||
It enables checking if free was called multiple times on
|
||||
already freed block of memory. Enabling this feature increases
|
||||
number of memory writes and reads, due to checks for memory patterns
|
||||
that may be performed on allocation and deallocation.
|
||||
|
||||
config DEBUG_LOCKS
|
||||
bool "Spinlock debug"
|
||||
default n
|
||||
|
@ -206,4 +191,8 @@ config DSP_RESIDENCY_COUNTERS
|
|||
R0, R1, R2 are abstract states which can be used differently
|
||||
based on platform implementation.
|
||||
|
||||
if !ZEPHYR_SOF_MODULE
|
||||
rsource "Kconfig.xtos-dbg"
|
||||
endif
|
||||
|
||||
endmenu
|
||||
|
|
|
@ -0,0 +1,14 @@
|
|||
config DEBUG_HEAP
|
||||
bool "Heap debug"
|
||||
default n
|
||||
help
|
||||
Select for enable heap alloc debugging
|
||||
|
||||
config DEBUG_BLOCK_FREE
|
||||
bool "Blocks freeing debug"
|
||||
default n
|
||||
help
|
||||
It enables checking if free was called multiple times on
|
||||
already freed block of memory. Enabling this feature increases
|
||||
number of memory writes and reads, due to checks for memory patterns
|
||||
that may be performed on allocation and deallocation.
|
Loading…
Reference in New Issue