Code review suggestions

Signed-off-by: Gaurav Aggarwal <aggarg@amazon.com>
This commit is contained in:
Gaurav Aggarwal 2024-05-13 10:54:41 +00:00
parent b67980cc2c
commit 36f4ffee9e

18
list.c
View file

@ -184,16 +184,14 @@ void vListInsert( List_t * const pxList,
* 4) Using a queue or semaphore before it has been initialised or * 4) Using a queue or semaphore before it has been initialised or
* before the scheduler has been started (are interrupts firing * before the scheduler has been started (are interrupts firing
* before vTaskStartScheduler() has been called?). * before vTaskStartScheduler() has been called?).
* - This includes initializing binary semaphores before taking them. If * 5) Attempting to 'take' binary semaphores created using
* you create one with `xSemaphoreCreateBinary()` or * `xSemaphoreCreateBinary()` or `xSemaphoreCreateBinaryStatic()`
* `xSemaphoreCreateBinaryStatic()`, you must call `xSemaphoreGive()` * APIs, before 'giving' them. Binary semaphores created using
* before calling `xSemaphoreTake(). See: * `xSemaphoreCreateBinary()` or `xSemaphoreCreateBinaryStatic()`,
* https://freertos.org/xSemaphoreCreateBinaryStatic.html: * are created in a state such that the semaphore must first be
* > The semaphore is created in the 'empty' state, meaning the * 'given' using xSemaphoreGive() API before it can be 'taken' using
* > semaphore must first be given using the xSemaphoreGive() API * xSemaphoreTake() API.
* > function before it can subsequently be taken (obtained) using the * 6) If the FreeRTOS port supports interrupt nesting then ensure that
* > xSemaphoreTake() function.
* 5) If the FreeRTOS port supports interrupt nesting then ensure that
* the priority of the tick interrupt is at or below * the priority of the tick interrupt is at or below
* configMAX_SYSCALL_INTERRUPT_PRIORITY. * configMAX_SYSCALL_INTERRUPT_PRIORITY.
**********************************************************************/ **********************************************************************/