Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
fix(PeriphDrivers): Fix UART DMA Transactions and Enable Full Duplex #763
fix(PeriphDrivers): Fix UART DMA Transactions and Enable Full Duplex #763
Changes from 5 commits
b6d919d
b9393ea
34276b4
77ecaef
e2a9134
bd4e60f
fade8a5
1a336ea
2d325eb
07eef60
2d5ec93
a03f22b
2cd7d4f
d9e9441
fe51c36
dc04d78
2ea9524
aba737e
831c893
8086917
ad19c87
34db845
81837cc
c24e810
566f057
b332e72
63fca53
85020c8
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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'd like to avoid part specific code in the _revX.c files. Can this condition be based on MXC_DMA_INSTANCES instead?
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.
These checks could be asserts. They are not really time critical, though, so I'll leave the final decision to you.
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.
Here is another place where ASSERT may be better. I see other places (not just in the code this PR touches) that could be ASSERTs also. IMO, anything that checks to see if a valid UART instance was passed in is better as an ASSERT.
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.
34db845
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.
@lorne-maxim I ended up purging the asserts except for once in the Init functions. The compiler should catch those cases as type-cast mismatch, so I think the checks for a valid UART instance in every function were overkill anyways...
It reduces our kid size pretty significantly, which is nice