Lines Matching refs:be
18 …registering extra Idle and Tick hooks at run time. Moreover, the hooks can be asymmetric among bot…
28 …be filled manually by the user. For efficiency reasons, **items are always retrieved from the ring…
32 **Allow-Split buffers** will allow an item to be split in two parts when wrapping around the end of…
34 …tes, and any number of bytes can be sent or retrieved each time. Use byte buffers when separate it…
37 …ses. Therefore, when retrieving an item, the item pointer is guaranteed to be 32-bit aligned. This…
40 …be rounded up to a 32-bit aligned size (multiple of 4 bytes), however the true item size is record…
84 //This has to be done with SendAcquire, or the address may be different when we copy
200 …owever, the true size of the item is recorded inside the header which will be returned when the it…
215 …be sent to the buffer by ``SendComplete`` for the data to be accessible by the consumer. Multiple …
223 …em. Hence, if ``SendComplete`` is not called for the 20 bytes, it will not be available, nor will …
225 When the 20 bytes item is finally completed, all the 3 data items can be received now, in the order…
227 …``SendAcquire`` or ``SendComplete`` since acquired buffers are required to be complete (not wrappe…
239 … completely store the item and its header, the free space at the tail will be **marked as dummy da…
258 … into the free space at the tail of buffer**. The remaining data will then be stored in the free s…
260 …tains data in two separate continuous parts, and each continuous part will be treated as a separat…
271 …must be returned** for the occupied space to be freed. Multiple items can be retrieved before retu…
279 …be followed by a return before another retrieval is permitted). When using :cpp:func:`xRingbufferR…
286 …be added to FreeRTOS queue sets using :cpp:func:`xRingbufferAddToQueueSetRead` such that every tim…
327 …be used to create ring buffers with specific memory requirements (such as a ring buffer being allo…
330 - The ring buffer's storage area of size ``xBufferSize``. Note that ``xBufferSize`` must be 32-bit …
336 …the function :cpp:func:`vRingbufferDelete` will not free any of the memory blocks. This must be do…
369 Ideally, ring buffers can be used with multiple tasks in an SMP fashion where the **highest priorit…
371 …ny lower priority tasks from being serviced as the semaphore should always be given to the highest…
373 …g buffer and as a result give the semaphore. Therefore, the semaphore will be given before the hig…
383 …Hooks and Tick Hooks which allow for application specific functionality to be added to the Idle Ta…
390 …eeRTOS. To enable legacy hooks, :ref:`CONFIG_FREERTOS_LEGACY_HOOKS` should be enabled in :doc:`pro…
394 …e core, ``vApplicationIdleHook()`` and ``vApplicationTickHook()`` can only be defined once. Howeve…
399 For some use-cases it may be necessary for the Idle Tasks or Tick Interrupts to execute multiple ho…
403 …Furthermore, due to the dual-core nature of the {IDF_TARGET_NAME}, it may be necessary for some ap…
407 The ESP-IDF tick and idle hooks are registered at run time. Each tick hook and idle hook must be re…
410 … hence ``vApplicationTickHook()`` (legacy case) or ESP-IDF tick hooks must be placed in internal R…
424 …be instances where users may want the freeing of TLSP memory to be automatic. Therefore, ESP-IDF F…
429 …LSP's associated Deletion Callback to `NULL` meaning that no callback will be called for that TLSP…
433 - The callback **must never attempt to block or yield** and critical sections should be kept as sho…
434 …tly before a deleted task's memory is freed. Thus, the callback can either be called from :cpp:fun…