[docs][utest]:Add comments for smp_spinlock_tc

Add comments for smp_spinlock_tc.

Signed-off-by: Mengchen Teng <teng_mengchen@163.com>

Author: Tm-C-mT

src/utest/smp/smp_interrupt_pri_tc.c

@@ -29,7 +29,7 @@
  *
  * Test Scenarios:
  * - First, two interrupts are registered, namely the low-priority interrupt RT_SPI_1 and the high-priority
- * - interrupt RT_SPI_2. 
+ * - interrupt RT_SPI_2.
  * - Scenario 1 (int_pri1_tc, mode=0): RT_SPI_1 and RT_SPI_2 are triggered sequentially without interrupt masking.
  * - At this point, the interrupt service routine (ISR) of RT_SPI_1 executes first to set ipi_val[0] = SET_VAL;
  * - since the RT_SPI_2 interrupt has not been triggered yet, ipi_val[1] remains at the initial value RES_VAL,

src/utest/smp/smp_spinlock_tc.c

@@ -16,6 +16,27 @@
  * @brief   Spinlock testcase.
  *
  * @note    Create multiple threads and use spinlocks to protect shared memory
+ *
+ * Test Case Name: [smp_spinlock_tc]
+ *
+ * Test Objectives:
+ * - Test the protection effect of spin locks on shared memory under the SMP architecture.
+ *
+ * Test Scenarios:
+ * - This utest creates two threads. Thread 1 acquires the spin lock, performs the number1++ operation,
+ * - then voluntarily enters a sleep state. After being awakened, it executes number2++ and finally
+ * - releases the spin lock. Thread 2, upon acquiring the spin lock, first checks whether number1 is
+ * - equal to number2, then performs number1++ and number2++ operations, and ultimately releases the
+ * - spin lock. Within Thread 2, if the judgment condition number >= 10 is satisfied, finish_flag is set to 1.
+ *
+ * Verification Metrics:
+ * - Output message: [ PASSED ] [ result ] testcase (core.smp_spinlock)
+ *
+ * Dependencies:
+ * - RT_USING_SMP needs to be enabled.
+ *
+ * Expected Results:
+ * - You will see the the PASS message of smp_interrupt_pri_tc.
  */
 
 #define THREAD_PRIORITY   20