qualcomm/fastrpc

FastRPC is Qualcomm's userspace library that facilitates efficient remote procedure calls between the CPU and DSP for high-performance computing.

Owned by Qualcomm

View on GitHub ↗Jump to charts ↓Open shareable report →

qualcomm/fastrpc has 100+ stars and 70+ forks on GitHub, is written in C, and was last pushed on Oct 12, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 19 minutes ago
Added to GitGenius on October 12th, 2026
Created on May 10th, 2024
Open Issues & Pull Requests: 45 (+0)
GitHub issues: Enabled
Number of forks: 78
Total Stargazers: 119 (+0)
Total Subscribers: 10 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 3.6 hours
Mean response time: 18.6 days
90th percentile: 57.7 days
Tracked items: 99

Maintainer activity

9 people did triage or write work on this repository in the last 12 months.

Counts unlabeled, assigned, unassigned, milestoned, demilestoned, locked, unlocked over the last 12 months. These are issue and pull request events that require triage or write permission. Commits and code review are not counted. labeled and renamed are excluded because GitHub issue forms record the issue author as the actor. Figures from October 18, 2026. This count is not comparable across projects: each project's automation decides which of these events a person emits. How this is counted.

How this project is maintained

About 11% of issues opened in the past year have never received a reply. 100% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. 61% of issues opened in the past year have been closed, leaving a working backlog. Three people close 87% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 24
New in 7 days: 1
Closed in 7 days: 0
Avg open age: 124 days
Stale 30+ days: 9
Stale 90+ days: 4

Recent activity

Opened in 7 days: 1
Closed in 7 days: 0
Comments in 7 days: 4
Events in 7 days: 8

Top labels

  • Stale (33)
  • fastrpc_driver_issue (7)
  • enhancement (5)
  • bug (1)
  • documentation (1)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

FastRPC is a userspace library that enables remote procedure calls between a CPU and DSP for offloading compute-intensive tasks to specialized processors.

The tool solves the problem of efficiently executing algorithms on digital signal processors, which can perform certain workloads more compute- and power-efficiently than CPUs through specialized resources like HVX. FastRPC hides the complexity of cross-processor communication by using an IDL-based interface definition approach. Developers define function interfaces in IDL files, which the QAIC compiler processes to generate marshaling code (stubs on the CPU side and skeletons on the DSP side) along with necessary headers. The framework handles parameter serialization, kernel-level transport via rpmsg, and remote invocation dispatch, allowing applications to call DSP functions as if they were local procedures.

FastRPC is suited for teams developing on Qualcomm platforms who have algorithms benefiting from DSP execution, particularly those leveraging HVX vector processing capabilities. The framework is most appropriate for applications where offloading large processing tasks to the DSP provides meaningful performance or power gains. It requires integration into both CPU and DSP build pipelines, with stubs and headers linked into CPU executables and skeletons and headers linked into DSP libraries. The tool is specific to Qualcomm's heterogeneous processor architecture and is not a general-purpose RPC framework.

The project maintains active engagement with its codebase through regular updates and demonstrates responsiveness to issues and pull requests. Development activity shows consistent attention to bug fixes and feature improvements across the FastRPC stack components. The maintainers provide clear documentation of the architecture and workflow, indicating a commitment to helping developers understand the framework's internals. The project accepts external contributions and maintains organized issue tracking, suggesting an open development model.