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

RMT driver, memory management clarification / documentation (IDFGH-12068) #13129

Closed
3 tasks done
higaski opened this issue Feb 7, 2024 · 0 comments
Closed
3 tasks done
Assignees
Labels
Resolution: NA Issue resolution is unavailable Status: Done Issue is done internally

Comments

@higaski
Copy link
Contributor

higaski commented Feb 7, 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

The new RMT transmission driver introduced with ESP-IDF 5 does require the user to keep data pointed to by the transaction queue alive until this particular transmission gets completed. The documentation mentions multiple times that the internal queue really is just a job queue, but I still think that there should be one paragraph about memory management.

The potential to introduce very subtle bugs here is huge, specially when changing the RMT configuration. Imagine users switching from blocking to non-blocking behavior, or simply change the transaction queue size from 1 to 2.

@espressif-bot espressif-bot added the Status: Opened Issue is new label Feb 7, 2024
@github-actions github-actions bot changed the title RMT driver, memory management clarification / documentation RMT driver, memory management clarification / documentation (IDFGH-12068) Feb 7, 2024
@espressif-bot espressif-bot added Status: In Progress Work is in progress 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: In Progress Work is in progress Status: Reviewing Issue is being reviewed labels Mar 14, 2024
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