Skip to content

Add RTSS mailbox FIT image support for iq-8275-evk and iq-9075-evk#2527

Draft
snegi-qti wants to merge 3 commits into
qualcomm-linux:masterfrom
snegi-qti:rtss_fitimage
Draft

Add RTSS mailbox FIT image support for iq-8275-evk and iq-9075-evk#2527
snegi-qti wants to merge 3 commits into
qualcomm-linux:masterfrom
snegi-qti:rtss_fitimage

Conversation

@snegi-qti

Copy link
Copy Markdown

The RTSS (Real Time Subsystem) mailbox driver uses a dedicated DT overlay (lemans-rtss-mb.dtbo/monaco-rtss-mb.dtbo). These changes wire up the overlay into the FIT image selection flow for platforms with RTSS mailbox IPC support enabled.

  • Add rtssmb FIT DTB compatible entries in fit-dtb-compatible-linux-qcom.inc for both qcs9075 and qcs8275 platforms, extending the base compatible strings with the rtss-mb DTB overlay so the bootloader can select the correct DTB
    bundle at boot
  • Include monaco-rtss-mb.dtbo in LINUX_QCOM_KERNEL_DEVICETREE for the iq-8275-evk machine config
  • Include lemans-rtss-mb.dtbo in LINUX_QCOM_KERNEL_DEVICETREE for the iq-9075-evk machine config
  • EFIVAR "rtssmb" activates the configuration

The RTSS mailbox driver uses a dedicated DT overlay (rtss-mb.dtbo)
that exists only in linux-qcom kernels.

Add rtssmb variants of all existing qcs9075 and qcs8275 FIT DTB
compatible entries, each extending the base compatible string with
the rtss-mb DTB, so the bootloader can select the correct DTB bundle
at boot for platforms with RTSS mailbox enabled.

Signed-off-by: Sankalp Negi <snegi@qti.qualcomm.com>
The monaco-rtss-mb.dtbo overlay enables RTSS mailbox IPC support on
the iq-8275-evk board. Add it to LINUX_QCOM_KERNEL_DEVICETREE to make
it available for FIT image selection on this platform.

Signed-off-by: Sankalp Negi <snegi@qti.qualcomm.com>
The lemans-rtss-mb.dtbo overlay enables RTSS mailbox IPC support on
the iq-9075-evk board. Add it to LINUX_QCOM_KERNEL_DEVICETREE to make
it available for FIT image selection on this platform.

Signed-off-by: Sankalp Negi <snegi@qti.qualcomm.com>
@lumag

lumag commented Jun 18, 2026

Copy link
Copy Markdown
Contributor

Why is it an overlay rather than a part of the main DT?

@lumag lumag left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Describe why, not what. Why is this a separate overlay, why is it enabled via UEFI variable, etc.

@vkraleti

Copy link
Copy Markdown
Contributor

*** No rule to make target 'arch/arm64/boot/dts/qcom/lemans-rtss-mb.dtbo'. Stop.

There is no DT in linux-qcom-6.18

@snegi-qti

Copy link
Copy Markdown
Author

*** No rule to make target 'arch/arm64/boot/dts/qcom/lemans-rtss-mb.dtbo'. Stop.

There is no DT in linux-qcom-6.18

DTs are already merged : QCLINUX: arm64: dts: qcom: lemans: Add RTSS Mailbox device tree overlay · qualcomm-linux/kernel@f9e0…

But the current meta-qcom linux-qcom recipe is pointing to older hash (https://github.com/qualcomm-linux/meta-qcom/blob/master/recipes-kernel/linux/linux-qcom_6.18.bb#L20), once it moves to latest, we will have the required changes.

@snegi-qti

Copy link
Copy Markdown
Author

Why is it an overlay rather than a part of the main DT?

Describe why, not what. Why is this a separate overlay, why is it enabled via UEFI variable, etc.

The RTSS Devicetree change is submitted as an overlay, as it cannot be added to intree kernel devicetree since the RTSS Devicetree and Driver are downstream, as of today. Hence, we have followed the existing precedent for "camx" which follows a similar approach of overlay + efivar activation to bring in this feature. Once this driver can be upstreamed, we shall move to intree approach.

@ricardosalveti ricardosalveti marked this pull request as draft June 19, 2026 11:06
@lumag

lumag commented Jun 19, 2026

Copy link
Copy Markdown
Contributor

@snegi-qti You are still describing that the driver is the out-of-tree module, etc. Describe, why do we want it in this way. What are the benefits. What is the usecase. Why the DTs are specified as an overlay rather than being merged in the base DTs in qcom-next, etc. CamX has an overlay DT, because the upstream kernel uses different bindings to desvribe the camera devices. If there are no conflicting upstream bindings, then the DT should be a part of the default DT.

@snegi-qti

Copy link
Copy Markdown
Author

@snegi-qti You are still describing that the driver is the out-of-tree module, etc. Describe, why do we want it in this way. What are the benefits. What is the usecase. Why the DTs are specified as an overlay rather than being merged in the base DTs in qcom-next, etc. CamX has an overlay DT, because the upstream kernel uses different bindings to desvribe the camera devices. If there are no conflicting upstream bindings, then the DT should be a part of the default DT.

@sargarram7 Could you please help answer the above queries for your RTSS driver ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants