-
Notifications
You must be signed in to change notification settings - Fork 6.6k
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 eDMA for S32K344 #61311
Add support eDMA for S32K344 #61311
Conversation
a716552
to
203217d
Compare
The following west manifest projects have been modified in this Pull Request:
Note: This message is automatically posted and updated by the Manifest GitHub Action. |
203217d
to
21192d9
Compare
8fb3120
to
59d9f69
Compare
Minor update |
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.
Test PASS on NXP regression for RT series
@Dat-NguyenDuy , thank you for the PR. Overall this looks great. My request would be not leave the current EDMA driver Kconfigs and device tree binding names unchanged to maintain backwards compatibility. |
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.
Request to leave the EDMA Kconfigs and device tree binding names unchanged.
@mmahadevan108 I'm a bit puzzled, I had the impression we agreed naming existing binding v2 and the new one v3 to follow the corresponding DMA versions (#61311 (comment)). We should add this to release notes to make sure the changes are visible to users. |
Add new dt binding for edma v3 that inherits whole dt properties from current version. One more property is added for SoCs that don't have separate error interrupt id, use same id with channel interrupt Signed-off-by: Dat Nguyen Duy <dat.nguyenduy@nxp.com>
On S32K344, the offset in memory map between each channel is 0x4000 for most channels, but there is specific case is between channel 11 and 12 which is 0x1D4000 instead. As a consequence, 32 channels are divided to two parts: one starts from channel 0 -> 11. The other is from channel 128 to 145. The channel gap is from 12 -> 127. For user and data structures in shim driver, the channel's value comes from 0 --> 31. Above constraint will be counted when interact with the mcux sdk Beside that, the DMAMUX register in this platform is very specific, not in identical with DMAMUX channel, so shim driver is updated to cover this case Signed-off-by: Dat Nguyen Duy <dat.nguyenduy@nxp.com>
dc50609
59d9f69
to
dc50609
Compare
I re-pushed to leave current EDMA Kconfig and dts binding |
Please update |
Enable dma support for mr_canhubk3 board Signed-off-by: Dat Nguyen Duy <dat.nguyenduy@nxp.com>
Add devicetree overlay for enabling dma test for mr_canhubk3 board Signed-off-by: Dat Nguyen Duy <dat.nguyenduy@nxp.com>
dc50609
to
69dd303
Compare
|
@manuargue , the general guidance from the Zephyr project is to limit breaking backward compatibility as much as possible. In this case, we are sticking with the SDMA naming convention for the driver folders. |
regression test is done. no issue found in rt platforms with this change |
This extends NXP current eDMA shim driver for supporting eDMA v3 on S32K344