1. Interrupt Management
   1. Deferred Interrupt Process
   2. Binary / Counting Semaphores

Interrupt Management

For the principle of the ISR to be as quick as possible, the trigger of freeRTOS api and the implementation of the ISR functions are always separated.
There are 3 mainstream usages:

Deferred Interrupt Process

The notion is to make the ISR related function higher priority. Its advantage shows when the execution time is unknown, like for reading or storing data from peripheral.

Binary / Counting Semaphores

For the Counting Semaphores, when ISR is triggered, a semaphore is pushed to a queue and the count is added. Then, the frozen task is unblocked and executing until the queue is cleared.

Note that the datatype of the queue can be self-defined.

When the ISR trigger, a semaphore is GIVEN through a ISR api and execute context switch. Then, a handler function is unblocked and TAKE the semaphore or decrease the semaphore before the ISR related process function.
Note that, the above procedure is pretty similar to the notifications management but in ISR.