RPMSG Lite multiple channels/endpoints

[hfranco.tx]

Hi @swiss and @ompie,

@ompie

Instead of going the Yocto way, I prefer staying with Torizon-builder and adding a new kernel module for the required shared memory transfer I need. I’ll give it a try in the next days and let you known.

Great, let me know if this worked or not.

@swiss

• The rpmsg git repo you linked is on a branch toradex_5.4-2.3.x-imx. I am building with 5.6 and as I just saw there is a 5.7 now available, but I guess the rpmsg is completely the same?

5.6 and 5.7 uses the same Kernel version, toradex_5.4-2.3.x-imx. When the next release of 6 comes out, we will start using kernel toradex_5.15-2.1.x-imx, which is based on kernel 5.15. I believe there are no modifications to 5.4 and 5.15 related to rpmsg, I need to check.

@swiss

• To customize the kernel module, I should basically copy the rpmsg folder into my tcbworkdir, change the .c file and add the source-dir: to the yaml file?

Yes, this should be enough in your case. Maybe some libraries will have to be imported as well, but probably in the rpmsg case there is no need.

@Edward

In your DT someone decided to split RX TX rings to separate 32k areas. It doesn’t make a lot of sense, since in imx_rpmsg driver rings follow each one without any gap. 64k vdev0 reserved memory could be enough.

The DT overlay that I sent to you in this topic was based on the NXP DT file, that’s why I separated in two vrings. But as @Edward suggested, apparently it’s better to work with only one vring. I’ll have to check that myself as well.

@Edward thanks for your contribution!

Best Regards,
Hiago.