OrgACRN
/
sof
mirror of https://github.com/thesofproject/sof.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
sof/app/prj.conf

43 lines
1.3 KiB
Plaintext
Raw Normal View History

zephyr: app: move main SOF app from zephyr samples Make the main SOF app part of SOF, where it belongs. No need for any overlays (which just duplicated the sample .conf anyways) and one place to build everything. This now does not depend on zephyr samples, which have a different purpose completely. Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2022-07-13 10:22:07 +08:00
CONFIG_SOF=y
CONFIG_BUILD_OUTPUT_BIN=n
CONFIG_HAVE_AGENT=n
zephyr: app: explicitly use DEFERRED log mode Calls to log messages are done in many places in SOF code, including latency sensitive low-latency code paths. To minimize the cost to low-latency path, use CONFIG_LOG_MODE_DEFERRED=y by default for all SOF Zephyr builds. This will offload log processing and output to a separate low priority thread. Signed-off-by: Kai Vehmanen <kai.vehmanen@linux.intel.com>
2022-10-05 16:44:32 +08:00
CONFIG_LOG=y
CONFIG_LOG_PRINTK=y
# Log processing is offloaded to a low-priority thread.
CONFIG_LOG_MODE_DEFERRED=y
zephyr: app: tune logging thread sleep and trigger threshold values Logging output of SOF is sporadic in nature (unless debug configuration is used) and it cannot be assumed that a steady flow of log messages is output at all times. During stable state, there are either no or very few messages output. When the DSP pipeline state is modified, there is a flurry of event. Similarly upon errors, a burst of log messages is output. For better balance between delay in writing logs, and limiting overhead of the logging thread, set new defaults to: CONFIG_LOG_PROCESS_TRIGGER_THRESHOLD=5 CONFIG_LOG_PROCESS_THREAD_SLEEP_MS=100 The SLEEP_MS sets an upper bound how long a single log message can stay in the log frontend buffer. Signed-off-by: Kai Vehmanen <kai.vehmanen@linux.intel.com>
2022-10-05 16:49:43 +08:00
# Wake the low-priority log thread every 100ms and/or
# if more than 5 messages are queued by the frontend.
CONFIG_LOG_PROCESS_TRIGGER_THRESHOLD=5
CONFIG_LOG_PROCESS_THREAD_SLEEP_MS=100
zephyr: app: increase log size to 4096 bytes Set CONFIG_LOG_BUFFER_SIZE=4096 for all SOF builds. As SOF uses DEFERRED mode for logging, the frontend buffer for logs must be large enough to cover all typical burts of messages. Tests using CONFIG_LOG_MEM_UTILIZATION debugging infrastructure, show that maximum buffer usage is over 2048 bytes in typical sof-test run on a SOF nocodec topology, tested on Intel TGL hardware. Signed-off-by: Kai Vehmanen <kai.vehmanen@linux.intel.com>
2022-10-05 17:12:34 +08:00
# Frontend buffer must be large enough to cover all
# typical bursts of log messages.
CONFIG_LOG_BUFFER_SIZE=4096
zephyr: app: increase log thread stack size to 4096 Set the logging thread stack size explicitly for SOF builds and use a safe default of 4096 bytes. Individual board overlays can override this default to save stack space. Signed-off-by: Kai Vehmanen <kai.vehmanen@linux.intel.com>
2022-10-05 17:19:27 +08:00
# Use stack that is sufficient for SOF backends
CONFIG_LOG_PROCESS_THREAD_STACK_SIZE=4096
zephyr: app: explicitly use DEFERRED log mode Calls to log messages are done in many places in SOF code, including latency sensitive low-latency code paths. To minimize the cost to low-latency path, use CONFIG_LOG_MODE_DEFERRED=y by default for all SOF Zephyr builds. This will offload log processing and output to a separate low priority thread. Signed-off-by: Kai Vehmanen <kai.vehmanen@linux.intel.com>
2022-10-05 16:44:32 +08:00
zephyr: app: move main SOF app from zephyr samples Make the main SOF app part of SOF, where it belongs. No need for any overlays (which just duplicated the sample .conf anyways) and one place to build everything. This now does not depend on zephyr samples, which have a different purpose completely. Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2022-07-13 10:22:07 +08:00
# Requires heap_info() be implemented, but no Zephyr wrapper
CONFIG_DEBUG_MEMORY_USAGE_SCAN=n
# Ensure -O2 (or similar) is used for optimization
CONFIG_SPEED_OPTIMIZATIONS=y
# Zephyr top-level default of -fno-strict-overflow is
# not a good fit for audio DSP code
CONFIG_COMPILER_OPT="-fstrict-overflow"
CONFIG_SCHED_DEADLINE=y
CONFIG_SCHED_CPU_MASK=y
CONFIG_SMP_BOOT_DELAY=y
app: set CONFIG_SCHED_CPU_MASK_PIN_ONLY=y for all SOF builds In many places of SOF code, assumption is that code is only run on a specific core. This allows to reduce overhead of cache coherency management. For example this is used in the IPC stack. In Zephyr, we can force threads to be pinned by default using the CONFIG_SCHED_CPU_MASK_PIN_ONLY setting. Enable this setting for all SOF builds. Signed-off-by: Kai Vehmanen <kai.vehmanen@linux.intel.com>
2022-09-08 20:06:36 +08:00
# SOF code assumes system work queue and other system
# wide threads are pinned to a single core.
# CPU_MASK_PIN_ONLY must be set for all SOF builds.
CONFIG_SCHED_CPU_MASK_PIN_ONLY=y
zephyr: app: move main SOF app from zephyr samples Make the main SOF app part of SOF, where it belongs. No need for any overlays (which just duplicated the sample .conf anyways) and one place to build everything. This now does not depend on zephyr samples, which have a different purpose completely. Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2022-07-13 10:22:07 +08:00
# Fix the sys ticks value until following bugs are solved:
# - https://github.com/zephyrproject-rtos/zephyr/issues/46378
CONFIG_SYS_CLOCK_TICKS_PER_SEC=15000
CONFIG_DAI=y
CONFIG_HEAP_MEM_POOL_SIZE=2048