-
Notifications
You must be signed in to change notification settings - Fork 211
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
[DMA 5/N]: Clean up duplicate PDMA instance macro #2527
base: main
Are you sure you want to change the base?
Conversation
3af506e
to
e10b28f
Compare
fwiw, the last commit LGTM. (Idk if it's easier to get this in earlier to avoid rebasing it) |
I'm rebasing this PR over and over again so that I can have an overview of what I'm missing. The idea of the macro dedup came a bit too late, I'd rather not pull it up and rebase over it, especially since it doesn't matter that much. |
#[doc = concat!("DMA channel suitable for I2S", $num)] | ||
pub struct [<I2s $num DmaChannel>] {} | ||
#[doc = concat!("DMA channel suitable for ", stringify!([< $peri:upper >]), $num)] | ||
#[non_exhaustive] |
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.
I guess this bug has lived long enough, no more safely constructed I2S DMA channels 🙃
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.
Iirc this is just a marker type anyway
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.
Not anymore, these are the channel "peripherals".
Thank you for your contribution!
We appreciate the time and effort you've put into this pull request.
To help us review it efficiently, please ensure you've gone through the following checklist:
Submission Checklist 📝
cargo xtask fmt-packages
command to ensure that all changed code is formatted correctly.CHANGELOG.md
in the proper section.Extra:
Pull Request Details 📖
Description
Please provide a clear and concise description of your changes, including the motivation behind these changes. The context is crucial for the reviewers.
Testing
Describe how you tested your changes.