-
Notifications
You must be signed in to change notification settings - Fork 325
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
[FEATURE]support for rpmsg #5068
Comments
This is a thing that i'm interested in seeing it done. I think there was no progress on this and I didnt see any patches. My goal would be to have a look at this in 2022. Anyhow, if you have some time I think the support is already in Zephyr so the only thing that might be needed would be a driver in the Linux kernel to implement remoteproc/rpmsg. |
@lenghonglin this slide is quite old and out of data as plans evolved. The CMSIS work morphed into Zephyr, which is now supported upstream. |
Zephyr already support with SOF and OpenAMP(implement with IPM) , but But SOF still uses IPC3/IPC4. I Think if SOF run on Zephyr, SOF shound call zephyr drivers, such dma , ipm, openamp. or will maintain two sets of drivers. |
yes, we already implement RPMSG with Zephyr , If SOF support RPMSG , we don't need rewrite ipc |
I very much hope that zephyr and sof can unify the driver framework so that we don't need to maintain two sets of drivers. Of course it may take time to do it, but I think it’s worth it. |
@hongshui3000 I think that's the intention in the future. We talked about this in this presentation: https://youtu.be/9kPSG5q6gmA?t=518 |
@dbaluta By the way, Zephyr currently has some issues with high-priority interrupts and interrupt nesting on the xtensa architecture. I think nxp may also encounter these issues . Maybe you can give me some suggestions. thanks |
@hongshui3000 - yes, plan is to move all arch/, platform/ and drivers to Zephyr. |
@lgirdwood good news |
@hongshui3000 thanks for logging the issues, fwiw both @dcpleung @andyross are working on them. |
Is there a detailed plan? |
@lenghonglin maybe this is something you want to work alongside @juimonen and discuss. Fwiw, the general work going on now is We have a plan to take the Zephyr i2s.h driver API and extend it as a generic DAI API (to support DMIC, HDA, SDW and other types). Once this is upstream in Zephyr we then plan to add the SOF audio drivers into Zephyr and the DMA drivers. @juimonen pls update any progress you have here. |
good, I wanted to be more involved because we had this problem with sof. |
Probably a good to create a codec interface in Zephyr. It should include the DAI API and it should also create APIs for PM, clocks, jack insert, controls. Please take a look at Linux ASoC codec interface as most concepts can be reused. Feel free to send me an email to discuss. |
I mean maybe we should re-design Zephyr Codec API. we could talk in this channel https://discord.com/channels/720317445772017664/930855494472589362 |
@juimonen can you share your DAI work with @lenghonglin for discussion. Thanks |
I see the ppt say sof already support rpmsg, but in the sof project , i have not find this part code, how's it going?
The text was updated successfully, but these errors were encountered: