automated: linux: add remoteproc smoke test - #634
Merged
Conversation
Contributor
Author
mwasilew
approved these changes
Aug 10, 2026
bhcopeland
reviewed
Aug 11, 2026
bhcopeland
reviewed
Aug 11, 2026
bhcopeland
reviewed
Aug 11, 2026
bhcopeland
reviewed
Aug 11, 2026
Member
|
@lool any progress on this PR? |
Contributor
Author
Addressed the 4 review comments per your suggestions; sorry for the delay, I sent this before going on leave, and replies were buried in a million other things when I came back! |
Contributor
Author
|
Test runs below, first on UNOQ: On a RPi: |
roxell
reviewed
Sep 10, 2026
Contributor
Author
|
@bhcopeland @roxell sorry, I picked up this PR from another system, and fumbled my git commit forgetting to add the changes addressing the review comments – fixed now, sorry :-/ (@roxell: FYI Qualcomm now has a policy to default to year-less copyright statements, I believe it's just to avoid churn, but I know this isn't a common practice. I've added the year, but I personally think the years are indeed a bit of noise, so I thought I'd mention it to you too :) |
bhcopeland
approved these changes
Sep 10, 2026
Member
roxell
approved these changes
Sep 11, 2026
Some remoteprocs silently fail to come up, e.g. when their firmware can't be loaded after an initramfs update. Add a smoke test which enumerates every remoteproc and checks that it reached the running or attached state. Auto-detect all remoteprocs by default; set DEVICE to target specific ones. Some remoteprocs are not booted by the kernel at all, either because no firmware is shipped for them or because another subsystem owns their lifecycle, e.g. ath11k for wpss. Skip modem and wpss by default rather than failing them, and make the list a parameter since it varies per SoC. Their state is still logged to help triage. Boards without any remoteproc report remoteproc-device-exists as skip instead of failing. Colliding remoteproc names are disambiguated by a stable device id. Signed-off-by: Loïc Minier <loic.minier@oss.qualcomm.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Some remoteprocs silently fail to come up, e.g. when their firmware
can't be loaded after an initramfs update.
Add a smoke test which enumerates every remoteproc and checks that it
reached the running or attached state. Auto-detect all remoteprocs by
default; set DEVICE to target specific ones.
Some remoteprocs are not booted by the kernel at all, either because no
firmware is shipped for them or because another subsystem owns their
lifecycle, e.g. ath11k for wpss. Skip modem and wpss by default
rather than failing them, and make the list a parameter since it
varies per SoC. Their state is still logged to help triage. Boards
without any remoteproc report remoteproc-device-exists as skip
instead of failing.