kmod-load-unload: search logs for "firmware boot complete"

Stop relying on verify-sof-firmware-load.sh in
check-kmod-load-unload.sh. The former has some serious issues:

- It passes even after unloading the firmware
- It has a misleading name
- It looks for firmware versions instead of "firmware boot complete",
  which is not compatible with IPC4.

Add new sof_firmware_boot_complete() function that can be re-used to fix
verify-sof-firmware-load.sh later.

Fixes #845

Signed-off-by: Marc Herbert <[email protected]>

case-lib/lib.sh

@@ -395,6 +395,13 @@ disable_kernel_check_point()
     KERNEL_CHECKPOINT="disabled"
 }
 
+# "$@" is optional, usually: --since=@"$epoch_checkpoint"
+# shellcheck disable=SC2120
+sof_firmware_boot_complete()
+{
+    journalctl_cmd "$@" --grep 'sof.*firmware[[:blank:]]*boot[[:blank:]]*complete'
+}
+
 is_zephyr()
 {
     local ldcFile

test-case/check-kmod-load-unload.sh

@@ -91,8 +91,11 @@ do
         die "Found error(s) in kernel log after module insertion"
 
     dlogi "checking if firmware is loaded successfully"
-    "$(dirname "${BASH_SOURCE[0]}")"/verify-sof-firmware-load.sh ||
+    if sof_firmware_boot_complete --since=@"$KERNEL_CHECKPOINT"; then
+        grep_firmware_info_in_logs --since=@"$KERNEL_CHECKPOINT"
+    else
          die "Failed to load firmware after module insertion"
+    fi
 
     # successful remove/insert module pass
     dlogi "==== firmware boot complete: $idx of $loop_cnt ===="