Skip to content

eva-driver: Add EVA kernel driver recipe - #3086

Draft
sasingh-cv wants to merge 1 commit into
qualcomm-linux:masterfrom
sasingh-cv:meta-qcom-add-eva-recipe
Draft

eva-driver: Add EVA kernel driver recipe#3086
sasingh-cv wants to merge 1 commit into
qualcomm-linux:masterfrom
sasingh-cv:meta-qcom-add-eva-recipe

Conversation

@sasingh-cv

Copy link
Copy Markdown

Add a recipe for the Qualcomm EVA (Engine for Visual Analytics) kernel driver.

The EVA driver provides the kernel-space interface to Qualcomm's vision acceleration hardware. It manages device
initialization, memory handling, firmware interaction, buffer management, and communication between userspace clients and EVA hardware.

The recipe builds and installs the msm-eva kernel module along with the associated UAPI headers required by userspace components to interact with the driver.

The driver forms the foundation of the EVA software stack and is consumed by higher-level vision runtimes such as Snapdragon Vision (SV), enabling applications to access hardware-accelerated vision capabilities on supported Qualcomm platforms.

Note: This PR is for review only and it will be merged only after getting the eva-driver overlay exception.

Add a recipe for the Qualcomm EVA (Engine for Visual Analytics)
kernel driver.

The EVA driver provides the kernel-space interface to Qualcomm's
vision acceleration hardware. It manages device
initialization, memory handling, firmware interaction, buffer
management, and communication between userspace clients and EVA
hardware.

The recipe builds and installs the msm-eva kernel module along
with the associated UAPI headers required by userspace components
to interact with the driver.

The driver forms the foundation of the EVA software stack and is
consumed by higher-level vision runtimes such as Snapdragon Vision
(SV), enabling applications to access hardware-accelerated vision
capabilities on supported Qualcomm platforms.

Signed-off-by: Sandeep Singh <sasingh@qti.qualcomm.com>
@lumag

Copy link
Copy Markdown
Contributor

It doesn't even build.

@lumag

Copy link
Copy Markdown
Contributor

Where is the firmware? Why is it this PR being submitted separately from #2968 ? Also, the question there is unanswered.

@lumag

Copy link
Copy Markdown
Contributor

Also, is firmware loaded on the first use or on the driver load? The latter is a much worse option for the system integration.

@sasingh-cv

Copy link
Copy Markdown
Author

It doesn't even build.

Actually, it has missing dependencies like evacc headers in kernel source. That's why it might not be building.

@sasingh-cv

sasingh-cv commented Sep 8, 2026

Copy link
Copy Markdown
Author

Where is the firmware? Why is it this PR being submitted separately from #2968 ? Also, the question there is unanswered.

For firmware bins , once the FW bins are uploaded and hosted in JFrog QArtifactory , we will raise the FW bb recipe meta-qcom PR for the same.
We chose to keep this PR focused on the EVA driver recipe and submit it separately from the SV recipe to maintain modularity and simplify the review process.

Also, is firmware loaded on the first use or on the driver load? The latter is a much worse option for the system integration.

Firmware loading will happen on first use.

@lumag

Copy link
Copy Markdown
Contributor

It doesn't even build.

Actually, it has missing dependencies like evacc headers in kernel source. That's why it might not be building.

Please don't submit the work which can't be merged.

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