Use the term task instead of thread

Author: adel-mamin

libs/ao/README.rst

@@ -7,7 +7,7 @@ Overview
 
 The Active Object (AO) module provides a framework for implementing the Active
 Object design pattern in embedded systems and other concurrent environments. It
-facilitates the encapsulation of threads, event-driven state machines, and
+facilitates the encapsulation of tasks, event-driven state machines, and
 message queues to enable asynchronous communication and cooperative
 multitasking.
 

libs/ao/ao.h

@@ -580,8 +580,8 @@ void am_ao_log_last_events(void (*log)(const char *name, int event));
  * Prevents using active objects before they are ready to
  * process events.
  *
- * To be run once at the start of regular (non-AO) user threads created with
- * am_pal_task_create() API. These regular user thread are typically
+ * To be run once at the start of regular (non-AO) user tasks created with
+ * am_pal_task_create() API. These regular user tasks are typically
  * used to execute blocking calls and post/publish events to active objects.
  */
 void am_ao_wait_start_all(void);

libs/event/README.rst

@@ -167,7 +167,7 @@ Please note that the following pseudocode is incorrect:
     am_ao_post_fifo(ao2, event);
 
 This is because event could become invalid after posting it to `ao`.
-Consider the case when `ao1` preempts the execution thread executing the code above
+Consider the case when `ao1` preempts the execution task executing the code above
 (let's call it `ao0`) once the event is posted to `ao1`.
 Then `ao1` consumes the event, decrements the event's reference counter and frees the event.
 After that `ao0` resumes the execution and tries to post the already freed event

libs/pal/freertos/pal.c

@@ -33,12 +33,8 @@
 #include "pal/pal.h"
 
 struct am_pal_task {
-    /* pthread data */
+    /* task data */
     static StaticTask_t task;
-    /* mutex to protect condition variable */
-    pthread_mutex_t mutex;
-    /* condition variable for signaling */
-    pthread_cond_t cond;
     /* flag to track notification state */
     bool notified;
     /* the task is valid */

libs/pal/pal.h

@@ -49,7 +49,7 @@
 #define AM_PAL_TICK_DOMAIN_DEFAULT 0
 
 #ifndef AM_PAL_TICK_DOMAIN_MAX
-#define AM_PAL_TICK_DOMAIN_MAX 1 /**< total number of tick domains */
+#define AM_PAL_TICK_DOMAIN_MAX 1 /**< Total number of tick domains. */
 #endif
 
 #ifdef __cplusplus
@@ -92,10 +92,10 @@ int am_pal_mutex_create(void);
 /**
  * Lock mutex.
  *
- * If the mutex is locked by another thread,
- * the calling thread waits until the mutex becomes available.
+ * If the mutex is locked by another task,
+ * the calling task waits until the mutex becomes available.
  *
- * A thread is not permitted to lock a mutex it has already locked.
+ * A task is not permitted to lock a mutex it has already locked.
  *
  * May not be called from ISRs.
  *
@@ -107,10 +107,10 @@ void am_pal_mutex_lock(int mutex);
  * Unlock mutex.
  *
  * The mutex must already be locked with am_pal_mutex_lock()
- * by the calling thread.
+ * by the calling task.
  *
- * The mutex cannot be claimed by another thread until it has been
- * unlocked by the calling thread.
+ * The mutex cannot be claimed by another task until it has been
+ * unlocked by the calling task.
  *
  * Mutexes may not be unlocked in ISRs.
  *

libs/timer/README.rst

@@ -28,7 +28,7 @@ Key Features
 3. **Thread Safety**:
 
    - Critical sections managed using user-defined enter/exit callbacks.
-   - Safe timer operations across concurrent threads.
+   - Safe timer operations across concurrent tasks.
 
 4. **Dynamic and Static Timer Allocation**:
 

libs/timer/timer.c

@@ -56,7 +56,7 @@ struct am_timer_state {
      *
      * This is done to limit struct am_timer::domains[] list operations
      * exclusively to am_timer_tick() call to avoid race conditions
-     * between timer owners the ticker thread/ISR.
+     * between timer owners the ticker task/ISR.
      */
     struct am_slist domains_pend[AM_PAL_TICK_DOMAIN_MAX];
     /** timer library configuration */