Rpmsg overlays status

This paragraph describes which is the status of device tree overlays for rpmsg with several Toradex SoMs.
I’m not sure that the picture is up-to-date with the repo https://git.toradex.com/cgit/device-tree-overlays.git/
As an example:
for verdin-imx8mp and verdin-imx8mm SoMs, the branches toradex_5.15-2.1.x-imx and master are listed in the table.
But toradex_5.15-2.1.x-imx is now a stale branch, superseeded by toradex_5.15-2.2.x-imx taht is the active one.
For the verdin-imx8mm SoM, the overlay verdin-imx8mm_hmp_overlay.dts is available both on toradex_5.15-2.1.x-imx (or toradex_5.15-2.2.x-imx) and master branches, but the file is different in the two branches.
Basically, it’s not clear to me what is the purpose of master branch: for other kind of commits, it seems up-to-date with “device-specific” branches, but for hmp/rpmsg commits the situation seems different.
And basically, only toradex_5.15-2.2.x-imx (or the old toradex_5.15-2.1.x-imx) works as expected.

Is a porting to master pending?

Hi, I’m the Toradex AI Assistant. I’m in early beta, and I would appreciate your feedback.
The Toradex Support team will follow up with you shortly!

Did you like my answer?

:+1: :-1:

The status of device tree overlays for RPMsg across various Toradex System on Modules (SoMs), such as the Verdin iMX8MP and Verdin iMX8MM, involves navigating through different branches within the Toradex device tree overlays repository. The branches toradex_5.15-2.1.x-imx and master are indeed mentioned, with the former being superseded by toradex_5.15-2.2.x-imx as the active branch for ongoing development and updates.

The master branch typically serves as a general development line that may not always be synchronized with device-specific branches for every feature, including HMP/RPMsg. This can lead to discrepancies in the availability and versioning of device tree overlays between the master branch and the device-specific branches like toradex_5.15-2.2.x-imx.

For the Verdin iMX8MM SoM, the presence of the verdin-imx8mm_hmp_overlay.dts in both the toradex_5.15-2.1.x-imx (or its successor toradex_5.15-2.2.x-imx) and master branches, with differences in the file across these branches, indicates that updates and specific enhancements tailored to the Verdin iMX8MM may not be fully mirrored in the master branch.

The purpose of the master branch, while generally being to consolidate development efforts and serve as a point of reference, may not fully align with the device-specific branches for certain features like HMP/RPMsg due to the focused nature of these branches on providing optimized support and compatibility for specific SoMs.

Regarding the porting to the master branch, it is plausible that updates or specific enhancements related to HMP/RPMsg for devices like the Verdin iMX8MP and Verdin iMX8MM are pending synchronization with the master branch. This process involves ensuring that any changes or additions made in device-specific branches are compatible and beneficial across the broader range of devices supported by Toradex before they are merged into the master branch.

In summary, while the toradex_5.15-2.2.x-imx branch (or its predecessor) is currently the recommended source for the latest device tree overlays for RPMsg functionality, the master branch’s role and its synchronization with device-specific branches may vary, highlighting

Please, also check if these links can help you solve your problem:

Cortex-M RPMsg Guide | Toradex Developer Center.

Hi @vix,

The overlays on the master branch are compatible with the mainline kernel (meaning we tested them with the upstream Linux kernel), not just vendor kernels. For the HMP functionality on i.MX8MP, the same overlay used on toradex_5.15-2.2.x-imx also works on the master branch, but we haven’t updated the master branch yet. If you plan to use HMP on i.MX8MP, even on the master branch, you’ll also need to consider the module parameter mentioned earlier [1].

[1] Imx8mp clock Linux module parameter

João Paulo