Debian Patches

Status for fastrpc/1.0.7-1

Patch Description Author Forwarded Bugs Origin Last update
udev-start-offline-dsp-remoteprocs udev: start DSP remoteprocs left offline When qcom_q6v5_pas is loaded from the initramfs, rproc_add() auto-boots
the core before the root filesystem is mounted. /lib/firmware is not
reachable yet, so request_firmware() fails with -ENOENT, and the
remoteproc core has no retry path: the DSP stays "offline" for the rest
of the boot even though the firmware is present on disk. With no DSP
there is no rpmsg channel, so no /dev/fastrpc-* node appears and none of
the daemons in 60-fastrpc.rules can start.
.
Add a udev rule that writes "start" to the remoteproc state attribute.
The event fires twice: once in the initramfs, where the write still
fails for the same reason the kernel's did, and again from the coldplug
pass that systemd-udev-trigger.service runs after switch_root, where the
firmware is reachable and the boot succeeds. udev logs and ignores the
failed write, so the first pass is harmless.
.
Only cores that qcom_q6v5_pas auto-boots and that FastRPC uses are
matched. modem and wpss have .auto_boot = false: modem is absent by
design on some SoCs, and ath11k owns the wpss lifecycle.
.
The ATTR{state}=="offline" gate is required: rproc_boot() increments
rproc->power unconditionally, so writing to an already-running core
would pin an extra reference and prevent a later shutdown or subsystem
restart from taking effect.
.
This is a userspace stopgap for the kernel bug; it can be dropped once a
kernel-side retry lands.
.
Relates to https://github.com/qualcomm-linux/kernel/issues/923		 Loïc Minier <loic.minier@oss.qualcomm.com> yes upstream upstream, https://github.com/qualcomm/fastrpc/pull/372 2026-08-13

All known versions for source package 'fastrpc'

Links