Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Documentation issue on xRingbufferSendAcquire() (IDFGH-12748) #13730

Closed
3 tasks done
huming2207 opened this issue May 2, 2024 · 3 comments
Closed
3 tasks done

Documentation issue on xRingbufferSendAcquire() (IDFGH-12748) #13730

huming2207 opened this issue May 2, 2024 · 3 comments
Assignees
Labels
Resolution: NA Issue resolution is unavailable Status: Done Issue is done internally

Comments

@huming2207
Copy link
Contributor

huming2207 commented May 2, 2024

Answers checklist.

  • I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
  • 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?

image

Regards,
Jackson

@espressif-bot espressif-bot added the Status: Opened Issue is new label May 2, 2024
@github-actions github-actions bot changed the title Documentation issue on xRingbufferSendAcquire() Documentation issue on xRingbufferSendAcquire() (IDFGH-12748) May 2, 2024
@0xjakob
Copy link
Collaborator

0xjakob commented 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.

@espressif-bot espressif-bot added Status: Reviewing Issue is being reviewed Status: Done Issue is done internally Resolution: NA Issue resolution is unavailable and removed Status: Opened Issue is new Status: Reviewing Issue is being reviewed labels May 2, 2024
@0xjakob
Copy link
Collaborator

0xjakob commented May 6, 2024

The fix has been merged to our internal code base. It should appear soon on the master branch here on github.

@huming2207
Copy link
Contributor Author

The fix has been merged to our internal code base. It should appear soon on the master branch here on github.

Nice, thanks for the fix!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Resolution: NA Issue resolution is unavailable Status: Done Issue is done internally
Projects
None yet
Development

No branches or pull requests

3 participants