qcom-rtss-mailbox: add KMD and UMD recipes for RTSS mailbox IPC#2528
Open
snegi-qti wants to merge 2 commits into
Open
qcom-rtss-mailbox: add KMD and UMD recipes for RTSS mailbox IPC#2528snegi-qti wants to merge 2 commits into
snegi-qti wants to merge 2 commits into
Conversation
Contributor
|
Repo is not even public: https://github.com/qualcomm-linux/rtss-mailbox-kmd |
snegi-qti
force-pushed
the
rtss_kmd
branch
2 times, most recently
from
be5f40d to
90ca377
Compare
Author
|
Sure, we are very close on making the repo public - awaiting some approvals, meanwhile, we can keep this as draft. |
Test Results 105 files + 79 634 suites +608 5h 16m 59s ⏱️ + 4h 21m 49s Results for commit ebfa959. ± Comparison against base commit f3eeb8b. This pull request removes 2 and adds 114 tests. Note that renamed tests count towards both.♻️ This comment has been updated with latest results. |
This was referenced Jun 22, 2026
Author
|
qli-2.0 GA Critical Fix |
Contributor
It's not a Fix. It's a new features, submitted past the cut-off date. |
Ricardo Salveti (ricardosalveti)
requested changes
Jun 22, 2026
Ricardo Salveti (ricardosalveti)
left a comment
Ricardo Salveti (ricardosalveti)
left a comment
Contributor
There was a problem hiding this comment.
Please improve your commit message, explain why this module is needed in first place, how it is going to be used, by which components, etc.
snegi-qti
changed the title
snegi-qti
changed the title
The RTSS subsystem requires a kernel-side IPC driver to establish the mailbox communication channel between RTSS and the application processor. Without this driver, no IPC path exists between the two subsystems. Add a DLKM recipe that builds and installs the rtss_mailbox kernel module. Configure the module to autoload on boot with a soft dependency on qcom_ipcc to guarantee correct initialization order. Export rtss_mailbox_uapi.h to sysroot so the userspace middleware recipe can consume it at build time. Signed-off-by: Sankalp Negi <snegi@qti.qualcomm.com>
Userspace applications need a stable, versioned API to communicate with the RTSS subsystem over the mailbox IPC channel. Providing a dedicated middleware recipe isolates the kernel UAPI from application code and enables independent versioning of the mailbox and OTA SDK components. Add a CMake-based recipe that builds and packages: - librtss_mailbox and librtss_safemlib (shared and static) as the core mailbox middleware - librtss_ota (shared and static) as the OTA SDK library - rtssdbg, rtss_console, and rtss_ota debug/utility binaries Split the output into runtime, dev, staticdev, and utils subpackages to give consumers fine-grained install control. Depend on qcom-rtss-mailbox-kmd to consume the exported rtss_mailbox_uapi.h header during the build. Signed-off-by: Sankalp Negi <snegi@qti.qualcomm.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The RTSS (Real Time Subsystem) currently has no IPC path to the application processor, and userspace applications have no stable API to communicate with it. These two recipes together establish the full mailbox IPC stack.