There are two selftest scenarios for ARRAY BIST(Board Integrated System
Test) tests:

1. Perform IFS ARRAY BIST tests once on each CPU.
2. Perform IFS ARRAY BIST tests on a random CPU with 3 rounds.

These are not meant to be exhaustive, but are some minimal tests for
for checking IFS ARRAY BIST.

Reviewed-by: Jithu Joseph <jithu.jos...@intel.com>
Co-developed-by: Ashok Raj <ashok....@intel.com>
Signed-off-by: Ashok Raj <ashok....@intel.com>
Signed-off-by: Pengfei Xu <pengfei...@intel.com>
---
 .../selftests/drivers/platform/x86/intel/ifs/test_ifs.sh  | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/tools/testing/selftests/drivers/platform/x86/intel/ifs/test_ifs.sh 
b/tools/testing/selftests/drivers/platform/x86/intel/ifs/test_ifs.sh
index 63d13400af4f..2ab310c4aaff 100755
--- a/tools/testing/selftests/drivers/platform/x86/intel/ifs/test_ifs.sh
+++ b/tools/testing/selftests/drivers/platform/x86/intel/ifs/test_ifs.sh
@@ -481,6 +481,14 @@ test_ifs()
                test_ifs_scan_available_imgs
                test_ifs_same_cpu_loop "$IFS_SCAN_MODE" "$RANDOM_CPU" 
"$LOOP_TIMES"
        fi
+
+       # SAPPHIRERAPID CPU could not support IFS ARRAY BIST scan
+       if [[ "$MODEL" == "$SAPPHIRERAPIDS_X" ]]; then
+               append_log "[$SKIP] SAPPHIRERAPID CPU, skip IFS ARRAY BIST scan"
+       else
+               ifs_test_cpus "$SIBLINGS" "$IFS_ARRAY_BIST_SCAN_MODE"
+               test_ifs_same_cpu_loop "$IFS_ARRAY_BIST_SCAN_MODE" 
"$RANDOM_CPU" "$LOOP_TIMES"
+       fi
 }
 
 trap ifs_cleanup SIGTERM SIGINT
-- 
2.43.0


Reply via email to