FIFOs
|
Type
|
Level
|
UID
|
STATUS
|
TYPE
|
COMPONENT
|
REFS
|
Title
|
Statement
|
USER_STORY
|
|---|---|---|---|---|---|---|---|---|---|
|
REQUIREMENT
|
1 |
|
|
|
|
Parents:
|
|
The Zephyr RTOS shall provide a mechanism to define and initialize a FIFO at compile time. |
|
|
REQUIREMENT
|
2 |
|
|
|
|
Parents:
|
|
The Zephyr RTOS shall provide a mechanism for the first thread waiting to get and dequeue a data item to return as if the timeout had expired. |
|
|
REQUIREMENT
|
3 |
|
|
|
|
Parents:
|
|
The Zephyr RTOS shall provide a mechanism to enqueue a data item to the back of a FIFO (i.e. append). |
|
|
REQUIREMENT
|
4 |
|
|
|
|
Parents:
|
|
The Zephyr RTOS shall provide a mechanism to allocate memory from a thread when enqueuing data items to a FIFO. |
|
|
REQUIREMENT
|
5 |
|
|
|
|
Parents:
|
|
The Zephyr RTOS shall provide a mechanism to append a list of data items to the back of a FIFO. |
|
|
REQUIREMENT
|
6 |
|
|
|
|
Parents:
|
|
The Zephyr RTOS shall provide a mechanism to append a list of data items to the back of a FIFO and then empty the list. |
|
|
REQUIREMENT
|
7 |
|
|
|
|
Parents:
|
|
The Zephyr RTOS shall provide a mechanism to get and dequeue a data item from the front of a FIFO, within a timeout. |
|
|
REQUIREMENT
|
8 |
|
|
|
|
Parents:
|
|
The Zephyr RTOS shall provide a mechanism to check if a FIFO is empty. |
|
|
REQUIREMENT
|
9 |
|
|
|
|
Parents:
|
|
The Zephyr RTOS shall provide a mechanism to peek at the data data item at the front of a FIFO. |
|
|
REQUIREMENT
|
10 |
|
|
|
|
Parents:
|
|
The Zephyr RTOS shall provide a mechanism to peek at the data item at the back of a FIFO. |
|