-
Notifications
You must be signed in to change notification settings - Fork 8
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
Add support for DMA-based reading from USART #261
Conversation
This makes the transfer code more generic and prepares it for the addition of peripheral-to-memory transfers.
Only buffers can provide a transfer count, but the trait should also be implementable by peripherals.
This is required to support buffers as transfer destinations.
We expose it in type signatures, which means our users may need to depend on it. I believe it is best practive to re-export it in this case, as that relieves the user from having to manage their own dependency on it (while keeping the version in sync at all times).
This is required to support buffers as destinations.
It hasn't served a purpose since I made `Channel::start_transfer` private.
Rebased, ready for review. @david-sawatzke: To address your comment on #260, I've pushed a commit that panics, if the buffer is too long. Is that what you had in mind? I don't think a |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The documentation looks good now!
Based on #260. I recommend reviewing/merging that one first.
Close #124.