smex: logger: Logger should point to smex as ldc generator

rimage will not be responsible for ldc file creation so logger
should points valid tool.

Signed-off-by: Karol Trzcinski <karolx.trzcinski@linux.intel.com>

src/include/sof/trace/trace.h

@@ -199,7 +199,7 @@ static inline struct trace *trace_get(void)
  *
  * All compile-time accessible data (verbosity, class, source file name, line
  * index and string literal) are linked into .static_log_entries section
- * of binary and then extracted by rimage, so they do not contribute to loadable
+ * of binary and then extracted by smex, so they do not contribute to loadable
  * image size. This way more elaborate log messages are possible and encouraged,
  * for better debugging experience, without worrying about runtime performance.
  */

tools/README.md

@@ -15,7 +15,7 @@ make install
 ### sof-logger
 
 sof-logger is used to print logs delivered from FW dma_trace mechanism, by
-searching log entries in *.ldc file generated by rimage.
+searching log entries in *.ldc file generated by smex.
 
 Every entry declared in FW is placed in elf output file (e.g. sof-apl) in
 .static_log_entries section in a form of struct defined in

tools/logger/convert.h

@@ -12,7 +12,7 @@
 
 #include <stdio.h>
 #include <ipc/info.h>
-#include <rimage/file_format.h>
+#include <smex/ldc.h>
 
 #define KNRM	"\x1B[0m"
 #define KRED	"\x1B[31m"

tools/logger/logger.c

@@ -35,8 +35,8 @@ static void usage(void)
 	fprintf(stdout, "%s:\t \t\t\tDisplay mailbox contents\n", APP_NAME);
 	fprintf(stdout, "%s:\t -i infile -o outfile\tDump infile contents "
 		"to outfile\n", APP_NAME);
-	fprintf(stdout, "%s:\t -l *.ldc_file\t\t*.ldc files generated "
-		"by rimage\n", APP_NAME);
+	fprintf(stdout, "%s:\t -l *.ldc_file\t\t*.ldc files generated by smex\n",
+		APP_NAME);
 	fprintf(stdout, "%s:\t -p \t\t\tInput from stdin\n", APP_NAME);
 	fprintf(stdout, "%s:\t -e \t\t\tEnable checking firmware version with "
 		"default verification file\n", APP_NAME);