2019-06-02 03:37:26 +08:00
|
|
|
# SPDX-License-Identifier: BSD-3-Clause
|
|
|
|
|
2018-12-28 04:18:49 +08:00
|
|
|
mainmenu "SOF $(PROJECTVERSION) Configuration"
|
|
|
|
|
|
|
|
comment "Compiler: $(CC_VERSION_TEXT)"
|
|
|
|
|
2021-05-11 23:41:03 +08:00
|
|
|
config XT_WAITI_DELAY
|
2019-12-03 20:36:24 +08:00
|
|
|
bool
|
|
|
|
default n
|
|
|
|
help
|
|
|
|
LX6 Xtensa platforms may require additional delay to flush loads
|
|
|
|
and stores before entering WAITI.
|
|
|
|
|
2018-12-28 04:18:49 +08:00
|
|
|
config HOST_PTABLE
|
|
|
|
bool
|
|
|
|
default n
|
|
|
|
|
2021-05-11 23:41:03 +08:00
|
|
|
config XT_BOOT_LOADER
|
2018-12-28 04:18:49 +08:00
|
|
|
bool
|
|
|
|
default n
|
|
|
|
|
2021-05-11 23:41:03 +08:00
|
|
|
config XT_HAVE_RESET_VECTOR_ROM
|
2019-05-27 21:01:36 +08:00
|
|
|
bool
|
|
|
|
default n
|
|
|
|
help
|
|
|
|
Select if your platform has the reset vector
|
|
|
|
in ROM.
|
|
|
|
|
2021-05-11 23:41:03 +08:00
|
|
|
config XT_IRQ_MAP
|
2018-12-28 04:18:49 +08:00
|
|
|
bool
|
|
|
|
default n
|
|
|
|
|
|
|
|
config DMA_GW
|
|
|
|
bool
|
|
|
|
default n
|
|
|
|
|
|
|
|
config MEM_WND
|
|
|
|
bool
|
|
|
|
default n
|
|
|
|
|
2019-03-04 20:04:35 +08:00
|
|
|
config INTEL_IOMUX
|
|
|
|
bool
|
|
|
|
default n
|
|
|
|
|
2021-05-17 14:26:54 +08:00
|
|
|
config DMA_HW_LLI
|
2019-04-10 23:48:34 +08:00
|
|
|
bool
|
|
|
|
default n
|
|
|
|
help
|
2021-05-17 14:26:54 +08:00
|
|
|
Hardware linked list is DMA feature, which allows
|
2019-04-10 23:48:34 +08:00
|
|
|
to automatically reload the next programmed linked list
|
|
|
|
item from memory without stopping the transfer. Without
|
|
|
|
it the transfer stops after every lli read and FW needs
|
|
|
|
to manually setup the next transfer.
|
|
|
|
|
|
|
|
Any platforms with hardware linked list support
|
|
|
|
should set this.
|
|
|
|
|
2019-04-16 21:53:53 +08:00
|
|
|
config DMA_SUSPEND_DRAIN
|
|
|
|
bool
|
|
|
|
default n
|
|
|
|
help
|
|
|
|
Some platforms cannot just simple disable DMA
|
|
|
|
channel during the transfer, because it will
|
|
|
|
hang the whole DMA controller. Instead we can
|
|
|
|
suspend the channel and drain the FIFO in order
|
|
|
|
to stop the channel as soon as possible.
|
|
|
|
|
|
|
|
Any platforms without the ability to disable
|
|
|
|
the DMA channel right away should set this.
|
|
|
|
|
2019-04-16 21:59:02 +08:00
|
|
|
config DMA_FIFO_PARTITION
|
|
|
|
bool
|
|
|
|
default n
|
|
|
|
help
|
|
|
|
Some platforms require to manually set DMA
|
|
|
|
FIFO partitions before starting any transfer.
|
|
|
|
|
|
|
|
Any platforms without automatic FIFO partitions
|
|
|
|
should set this.
|
|
|
|
|
2021-05-11 23:41:03 +08:00
|
|
|
config XT_INTERRUPT_LEVEL_1
|
2019-10-01 17:54:54 +08:00
|
|
|
bool
|
2019-10-01 19:02:46 +08:00
|
|
|
default n
|
2019-10-01 17:54:54 +08:00
|
|
|
help
|
|
|
|
Select if the platform supports any interrupts of level 1.
|
|
|
|
Disabling this option allows for less memory consumption.
|
|
|
|
|
2021-05-11 23:41:03 +08:00
|
|
|
config XT_INTERRUPT_LEVEL_2
|
2019-10-01 17:54:54 +08:00
|
|
|
bool
|
2019-10-01 19:02:46 +08:00
|
|
|
default n
|
2019-10-01 17:54:54 +08:00
|
|
|
help
|
|
|
|
Select if the platform supports any interrupts of level 2.
|
|
|
|
Disabling this option allows for less memory consumption.
|
|
|
|
|
2021-05-11 23:41:03 +08:00
|
|
|
config XT_INTERRUPT_LEVEL_3
|
2019-10-01 17:54:54 +08:00
|
|
|
bool
|
2019-10-01 19:02:46 +08:00
|
|
|
default n
|
2019-10-01 17:54:54 +08:00
|
|
|
help
|
|
|
|
Select if the platform supports any interrupts of level 3.
|
|
|
|
Disabling this option allows for less memory consumption.
|
|
|
|
|
2021-05-11 23:41:03 +08:00
|
|
|
config XT_INTERRUPT_LEVEL_4
|
2019-10-01 17:54:54 +08:00
|
|
|
bool
|
2019-10-01 19:02:46 +08:00
|
|
|
default n
|
2019-10-01 17:54:54 +08:00
|
|
|
help
|
|
|
|
Select if the platform supports any interrupts of level 4.
|
|
|
|
Disabling this option allows for less memory consumption.
|
|
|
|
|
2021-05-11 23:41:03 +08:00
|
|
|
config XT_INTERRUPT_LEVEL_5
|
2019-10-01 17:54:54 +08:00
|
|
|
bool
|
2019-10-01 19:02:46 +08:00
|
|
|
default n
|
2019-10-01 17:54:54 +08:00
|
|
|
help
|
|
|
|
Select if the platform supports any interrupts of level 5.
|
|
|
|
Disabling this option allows for less memory consumption.
|
|
|
|
|
2020-05-30 12:14:08 +08:00
|
|
|
rsource "src/Kconfig"
|
2018-12-28 04:18:49 +08:00
|
|
|
|
2021-05-28 04:54:10 +08:00
|
|
|
# See zephyr/modules/Kconfig
|
2021-05-17 20:35:12 +08:00
|
|
|
if !ZEPHYR_SOF_MODULE
|
|
|
|
rsource "Kconfig.xtos-build"
|
|
|
|
endif
|
2019-11-05 18:55:43 +08:00
|
|
|
|
2018-12-28 04:18:49 +08:00
|
|
|
menu "Debug"
|
|
|
|
|
2019-05-24 18:13:41 +08:00
|
|
|
config DEBUG
|
|
|
|
bool "Enable debug build"
|
|
|
|
default n
|
|
|
|
help
|
|
|
|
Select for debug build
|
|
|
|
|
2018-12-28 04:18:49 +08:00
|
|
|
config GDB_DEBUG
|
|
|
|
bool "GDB Stub"
|
|
|
|
default n
|
|
|
|
help
|
|
|
|
Select for GDB debugging
|
|
|
|
|
2020-09-29 20:14:26 +08:00
|
|
|
config DEBUG_MEMORY_USAGE_SCAN
|
|
|
|
bool "Memory usage scan"
|
|
|
|
default y
|
|
|
|
help
|
|
|
|
It enables memory usage scan at demand in runtime.
|
|
|
|
This feature does not affect standard memory operations,
|
|
|
|
especially allocation and deallocation.
|
|
|
|
|
2019-07-17 19:38:39 +08:00
|
|
|
config DEBUG_LOCKS
|
|
|
|
bool "Spinlock debug"
|
|
|
|
default n
|
|
|
|
help
|
|
|
|
It adds additional information to the spinlocks about
|
|
|
|
the current user of the lock. Also executes panic
|
|
|
|
on deadlock.
|
|
|
|
|
|
|
|
config DEBUG_LOCKS_VERBOSE
|
|
|
|
bool "Spinlock verbose debug"
|
|
|
|
depends on DEBUG_LOCKS
|
|
|
|
default n
|
|
|
|
help
|
|
|
|
In addition to DEBUG_LOCKS it also adds spinlock traces
|
|
|
|
every time the lock is acquired.
|
|
|
|
|
2019-05-15 21:32:17 +08:00
|
|
|
config DEBUG_IPC_COUNTERS
|
|
|
|
bool "IPC counters"
|
|
|
|
depends on CAVS
|
|
|
|
depends on DEBUG
|
|
|
|
default n
|
|
|
|
help
|
|
|
|
Select for enabling tracing IPC counter in SRAM_REG mailbox
|
|
|
|
|
2020-01-14 01:18:51 +08:00
|
|
|
config PERFORMANCE_COUNTERS
|
|
|
|
bool "Performance counters"
|
|
|
|
default n
|
|
|
|
help
|
|
|
|
Enables tracing of simple performance measurements.
|
|
|
|
A basic use case is to measure number of platform & cpu clock ticks
|
|
|
|
passed between two checkpoints (init() and stamp()), for example
|
|
|
|
total time spent on running low latency scheduler tasks.
|
|
|
|
Platforms that gate cpu clock in wait-for-interrupt calls may also
|
|
|
|
use the stamp() macro periodically to find out how long the cpu
|
|
|
|
was in active/sleep state between the calls and estimate the cpu load.
|
|
|
|
|
2020-06-10 04:21:55 +08:00
|
|
|
config DSP_RESIDENCY_COUNTERS
|
|
|
|
bool "DSP residency counters"
|
|
|
|
default n
|
|
|
|
help
|
|
|
|
Enables simple DSP residency counters in SRAM_REG mailbox.
|
|
|
|
R0, R1, R2 are abstract states which can be used differently
|
|
|
|
based on platform implementation.
|
|
|
|
|
2021-05-17 21:45:07 +08:00
|
|
|
if !ZEPHYR_SOF_MODULE
|
|
|
|
rsource "Kconfig.xtos-dbg"
|
|
|
|
endif
|
|
|
|
|
2018-12-28 04:18:49 +08:00
|
|
|
endmenu
|