app: debug_stream_overlay.conf: Add new debug_stream Kconfig options

There is two new options, CONFIG_SOF_DEBUG_STREAM_SLOT_FORCE_MAX_CPUS
and CONFIG_SOF_DEBUG_STREAM_TEXT_MSG_ASSERT_PRINT.

CONFIG_SOF_DEBUG_STREAM_SLOT_FORCE_MAX_CPUS limits the amount of
debug_stream support to a lower number of cores than what is
available. As the number of supported cores shrink, the available
circular buffer size increases. This means increased bandwidth. This
is particularly useful, when debugging a problem on core 0. By defaut
this option is commented out.

CONFIG_SOF_DEBUG_STREAM_TEXT_MSG_ASSERT_PRINT adds optional support to
route assert output through debug stream text messages. This option
obeys CONFIG_EXCEPTION_DUMP_HOOK_ONLY. If it is selected the assert
print is sent only to debug stream. Without it the assert prints are
printed with vprintk too,

Signed-off-by: Jyri Sarha <jyri.sarha@linux.intel.com>

Author: Jyri Sarha

app/debug_stream_overlay.conf

@@ -8,6 +8,17 @@ CONFIG_SOF_DEBUG_STREAM_THREAD_INFO=y
 CONFIG_THREAD_NAME=y
 # For Zephyr to compile with thread names on PTL we need to increase THREAD_BYTES
 CONFIG_MAX_THREAD_BYTES=4
+# Shrink number of CPU sections
+# As the number of supported cores shrink, the available circular
+# buffer size increases. This means increased bandwitdth. This is
+# particularly useful, when debugging a problem on core 0.
+#CONFIG_SOF_DEBUG_STREAM_SLOT_FORCE_MAX_CPUS=1
+
+# Direct the assert prints to debug stream
+# This option obeys CONFIG_EXCEPTION_DUMP_HOOK_ONLY. If it is selected
+# the assert print is sent only to debug stream. Without it the assert
+# prints are printed with vprintk too,
+CONFIG_SOF_DEBUG_STREAM_TEXT_MSG_ASSERT_PRINT=y
 
 # Debug window slot configuration 1
 # The CONFIG_SOF_TELEMETRY uses slot 2, but with performance and IO-performance