You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
I have searched the issue tracker for a similar issue and not found a similar issue.
General issue report
Hi all,
I was trying to use the FreeRTOS ring buffer for one of our storage library's write buffer. I had a look on the API xRingbufferSendAcquire() and my understanding for this is like a "malloc" but instead of allocates on heap, it "prepares" a contiguous RAM buffer for the consumer to directly modify (e.g. memcpy() from other stuff) on it, and then call xRingbufferSendComplete() to tell the ring buffer my modification on that particular piece of buffer is done.
But the ring buffer documentation below declares dma_item_t item instead of dma_item_t *item. Have I misunderstood anything?
Regards,
Jackson
The text was updated successfully, but these errors were encountered:
github-actionsbot
changed the title
Documentation issue on xRingbufferSendAcquire()
Documentation issue on xRingbufferSendAcquire() (IDFGH-12748)
May 2, 2024
@huming2207 I think you're right. The documentation looks incorrect. Indeed, the code would give a warning when it is compiled. We'll take a look and fix this.
Answers checklist.
General issue report
Hi all,
I was trying to use the FreeRTOS ring buffer for one of our storage library's write buffer. I had a look on the API
xRingbufferSendAcquire()
and my understanding for this is like a "malloc" but instead of allocates on heap, it "prepares" a contiguous RAM buffer for the consumer to directly modify (e.g.memcpy()
from other stuff) on it, and then callxRingbufferSendComplete()
to tell the ring buffer my modification on that particular piece of buffer is done.But the ring buffer documentation below declares
dma_item_t item
instead ofdma_item_t *item
. Have I misunderstood anything?Regards,
Jackson
The text was updated successfully, but these errors were encountered: