qcom-multimedia-proprietary-image: add qcom-rtss-can - #461
q-AnupKulkarni wants to merge 1 commit into
Conversation
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>
|
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 |
That's wrong. There is no need to use VirtIO here, you don't have virtio transport. It must be a normal kernel can driver. |
I agree, will be using CAN network driver in kernel only. |
please make sure it's captured in qualcomm-linux/meta-qcom#3123. On Sepember 1st I expect the qcom-rtss-can recipe to be deleted. |
Done. |
2 participants
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.