logging: Remove hda log backend

The HDA log backend has been buggy for some time, and the fixes are well
understood. The issue with HDA log as it is implemented today means
there are concurrency and ISR issues where it can deadlock.

The fixes are effectively dropping the usage of ipc to communicate
status, using polling on the hda stream, and having a formatter per call
context (cores + isr) when log mode immediate is enabled to fix log
mangling. However it was found this had a lot of unintentional side
effects that made it difficult to make progress on when it came to
changes of the host side python tooling.

Meanwhile the feature has sat unused for nearly a year. Remove it, and
it can always be revisited in the future if something like it happens to
be needed.

Signed-off-by: Tom Burdick <[email protected]>

Author: teburd

subsys/logging/Kconfig.formatting

@@ -166,7 +166,7 @@ config LOG_BACKEND_FORMAT_TIMESTAMP
 	bool "Timestamp formatting in the backend"
 	depends on LOG_BACKEND_UART || LOG_BACKEND_NATIVE_POSIX || LOG_BACKEND_RTT \
 	           || LOG_BACKEND_SWO || LOG_BACKEND_XTENSA_SIM || LOG_BACKEND_FS \
-	           || LOG_BACKEND_ADSP || LOG_BACKEND_ADSP_HDA || LOG_BACKEND_ADSP_MTRACE
+	           || LOG_BACKEND_ADSP || LOG_BACKEND_ADSP_MTRACE
 	default y
 	help
 	  When enabled timestamp is formatted to hh:mm:ss:ms,us.

subsys/logging/backends/CMakeLists.txt

@@ -5,11 +5,6 @@ zephyr_sources_ifdef(
   log_backend_adsp.c
 )
 
-zephyr_sources_ifdef(
-  CONFIG_LOG_BACKEND_ADSP_HDA
-  log_backend_adsp_hda.c
-)
-
 zephyr_sources_ifdef(
   CONFIG_LOG_BACKEND_ADSP_MTRACE
   log_backend_adsp_mtrace.c

subsys/logging/backends/Kconfig

@@ -4,7 +4,6 @@
 menu "Backends"
 
 rsource "Kconfig.adsp"
-rsource "Kconfig.adsp_hda"
 rsource "Kconfig.adsp_mtrace"
 rsource "Kconfig.ble"
 rsource "Kconfig.efi_console"