Skip to content

qcom-multimedia-proprietary-image: add qcom-rtss-can - #461

Open
q-AnupKulkarni wants to merge 1 commit into
qualcomm-linux:mainfrom
q-AnupKulkarni:anupkulk/rtss_can
Open

qcom-multimedia-proprietary-image: add qcom-rtss-can#461
q-AnupKulkarni wants to merge 1 commit into
qualcomm-linux:mainfrom
q-AnupKulkarni:anupkulk/rtss_can

Conversation

@q-AnupKulkarni

@q-AnupKulkarni q-AnupKulkarni commented Sep 9, 2026

Copy link
Copy Markdown

Target milestone: qli-2.1 pull-request freeze

Background

Add support for RTSS CAN user-space deamon

Tracking Issue

qualcomm-linux/meta-qcom#3123

PR dependency

#457

Testing

Default bootup verified on lemans and monaco targets with no regression.

The RTSS (Real-Time Subsystem) is a dedicated real-time processor on
Qualcomm SoCs that manages timing-critical operations such as CAN
(Controller Area Network) communication, commonly used in automotive
and industrial applications.

qcom-rtss-can is a userspace daemon that bridges Linux SocketCAN
virtual interfaces with RTSS mailbox channels, allowing standard
SocketCAN applications to communicate with CAN hardware that is
managed by the RTSS and not directly accessible from the Linux CAN
stack.

Add qcom-rtss-can to the multimedia proprietary image to enable
SocketCAN-based applications on platforms where CAN is handled by
the RTSS.

Signed-off-by: Anup Kulkarni <anup.kulkarni@oss.qualcomm.com>
@lumag

Copy link
Copy Markdown
Contributor

Most of the text in the PR description is redundant and can be removed.

Anyway, when we had a meeting regarding RTSS, what was the decision regarding the CAN being driven by userspace?

@q-AnupKulkarni

Copy link
Copy Markdown
Author

Most of the text in the PR description is redundant and can be removed.

Anyway, when we had a meeting regarding RTSS, what was the decision regarding the CAN being driven by userspace?

Updated the description.

Part of phase-2 and phase-3 timelines

Phase 2 | • RTSS Mailbox transition to upstream solution • Socket CAN migration Start | Q1'27
Phase 3 | • Upstream RTSS Mailbox, or RpMsg if throughput requirements are met. If RPMsg does not satisfy performance needs, both solutions will be maintained. • Evaluation of emerging VirtIO-based CAN efforts from the community to align Qualcomm's upstream direction. • CAN upstream-aligned solution | Q2-Q3'27

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.

2 participants