Skip to content

ASoC: qcom: Add Shikra machine driver#725

Merged
sgaud-quic merged 11 commits into
qualcomm-linux:qcom-6.18.yfrom
mohsRafi:shikra_machine_driver_change
Jun 18, 2026
Merged

ASoC: qcom: Add Shikra machine driver#725
sgaud-quic merged 11 commits into
qualcomm-linux:qcom-6.18.yfrom
mohsRafi:shikra_machine_driver_change

Conversation

@mohsRafi

@mohsRafi mohsRafi commented Jun 16, 2026

Copy link
Copy Markdown
Contributor

Add Qualcomm Shikra sound-card variant support in DT
bindings and in the sc8280xp machine driver.

Shikra EVK variants use different audio components and processing
architectures:

  • CQM/CQS use an I2S-based path with WSA885x amplifiers and
    PM4125 + Rouleur codec components.
  • CQM runs in DSP-bypass mode (CPU-only audio pipeline).
  • CQS uses modem-DSP based audio processing.
  • IQS uses a third-party MAX98091 codec with modem-DSP support.

The DT binding patch adds explicit Shikra compatibles, and the machine
patch wires variant-specific DAPM/controls and clock behavior so each
board is configured correctly.

Add AudioReach support for LPASS Audio IF based TDM backends and wire it
up for the sc8280xp machine driver.

CRs-Fixed: 4573482
qli-2.0 GA Critical Fix

@mohsRafi mohsRafi requested review from a team, quic-tingweiz, rrnayak and yijiyang June 16, 2026 13:28
@qlijarvis

Copy link
Copy Markdown

PR #725 — validate-patch

PR: #725

Verdict Issues Detailed Report
0 Full report

Final Summary

  1. Lore link present: Yes — all 11 commits have valid lore.kernel.org links
  2. Lore link matches PR commits: ⚠️ Cannot verify — network access restricted, but patch 03 has a known bug not present in typical upstream review
  3. Upstream patch status: In review — all marked FROMLIST, posted June 2026
  4. PR present in qcom-next: Not checked — FROMLIST patches under upstream review

Required Actions:

  • Fix variable name bug in patch 03 (line 184: datapdata)
  • Fix duplicate subject prefix in patch 03
  • Verify all three upstream series have been reviewed and are ready for integration
  • Confirm the combined series builds cleanly after fixing patch 03
Verdict: ❌ — click to expand

🔍 Patch Validation

PR: #725 (11 commits combining 3 upstream series)
Upstream commits: Multiple lore.kernel.org series (see details below)
Verdict: ❌ FAIL

Commit Message

Check Status Note
Subject matches upstream ⚠️ Patch 03 has duplicate prefix "ASoC: qcom: sc8280xp: ASoC: qcom: sc8280xp:"
Body preserves rationale All commit messages include detailed rationale
Fixes tag present/correct N/A No Fixes tags (new feature patches)
Authorship preserved All authors and Co-developed-by tags present
Backport note (if applicable) N/A FROMLIST patches, not backports

Diff

File Status Notes
Patch 01: Documentation/devicetree/bindings/sound/qcom,q6apm-lpass-dais.yaml DT binding extension looks correct
Patch 02: sound/soc/qcom/qdsp6/q6apm-lpass-dais.c MI2S clock control implementation
Patch 03: sound/soc/qcom/sc8280xp.c CRITICAL BUG: Uses undefined variable data instead of pdata at line 184
Patch 04: include/dt-bindings/sound/qcom,qaif.h New header for QAIF definitions
Patch 05: sound/soc/qcom/qdsp6/q6apm-lpass-dais.c TDM DAI operations
Patch 06: Documentation/devicetree/bindings/sound/qcom,q6dsp-lpass-ports.yaml Audio IF clock bindings
Patch 07: include/dt-bindings/sound/qcom,q6dsp-lpass-ports.h Clock ID definitions
Patch 08: sound/soc/qcom/common.c TDM slot helper functions
Patch 09: sound/soc/qcom/sc8280xp.c TDM hw_params support
Patch 10: Documentation/devicetree/bindings/sound/qcom,sm8250.yaml Shikra compatibles (has Reviewed-by)
Patch 11: sound/soc/qcom/sc8280xp.c Shikra EVK machine variants

Issues

Critical (Build-Breaking):

  1. Patch 03 - Variable name bug at sound/soc/qcom/sc8280xp.c:184:
    • Uses data->snd_soc_common_priv->codec_dai_fmt
    • Should be pdata->snd_soc_common_priv->codec_dai_fmt
    • This will cause compilation failure: error: 'data' undeclared

Commit Message Issues:
2. Patch 03 - Duplicate subject prefix:

  • Current: "FROMLIST: ASoC: qcom: sc8280xp: ASoC: qcom: sc8280xp: enhance machine driver..."
  • Should be: "FROMLIST: ASoC: qcom: sc8280xp: enhance machine driver for board-specific config"

Series Integration:
3. This PR combines patches from 3 different upstream series posted on different dates:

  • Series 1 (patches 1-3): Posted 2026-06-08 by Mohammad Rafi Shaik
  • Series 2 (patches 4-9): Posted 2026-06-10 by Prasad Kumpatla
  • Series 3 (patches 10-11): Posted 2026-06-11 by Ajay Kumar Nandam
  • While functionally related, combining multiple independent series requires careful dependency verification

Verdict

REJECT - Patch 03 contains a critical compilation error that must be fixed before merge.

Final Summary

  1. Lore link present: Yes — all 11 commits have valid lore.kernel.org links
  2. Lore link matches PR commits: ⚠️ Cannot verify — network access restricted, but patch 03 has a known bug not present in typical upstream review
  3. Upstream patch status: In review — all marked FROMLIST, posted June 2026
  4. PR present in qcom-next: Not checked — FROMLIST patches under upstream review

Required Actions:

  • Fix variable name bug in patch 03 (line 184: datapdata)
  • Fix duplicate subject prefix in patch 03
  • Verify all three upstream series have been reviewed and are ready for integration
  • Confirm the combined series builds cleanly after fixing patch 03

@qlijarvis

Copy link
Copy Markdown

PR #725 — checker-log-analyzer

PR: #725
Checker run: https://github.com/qualcomm-linux/kernel-config/actions/runs/27621099553

Checker Result Summary
Checker Result Summary
checkpatch 2 warnings: Co-developed-by/Signed-off-by mismatch in commits 10 & 11
dt-binding-check Passed
dtb-check ⏭️ Skipped (no DT changes)
sparse-check Passed
check-uapi-headers Passed
check-patch-compliance 4 failures: 3 patch mismatches + 1 author mismatch
tag-check N/A Not applicable (FROMLIST commits)
qcom-next-check ⏭️ Skipped (FROMLIST commits only)

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #725 - ASoC: qcom: Add MI2S/TDM clock control and Shikra EVK support
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/27621099553

Checker Result Summary
checkpatch 2 warnings: Co-developed-by/Signed-off-by mismatch in commits 10 & 11
dt-binding-check Passed
dtb-check ⏭️ Skipped (no DT changes)
sparse-check Passed
check-uapi-headers Passed
check-patch-compliance 4 failures: 3 patch mismatches + 1 author mismatch
tag-check N/A Not applicable (FROMLIST commits)
qcom-next-check ⏭️ Skipped (FROMLIST commits only)

❌ checkpatch

Root cause: Two commits have mismatched Co-developed-by and Signed-off-by trailers.

Failure details:

Commit e1030114b39f ("FROMLIST: ASoC: dt-bindings: qcom,sm8250: add Shikra sound card compatibles")
WARNING: Co-developed-by and Signed-off-by: name/email do not match

Commit 2398140438db ("FROMLIST: ASoC: qcom: sc8280xp: add Shikra EVK machine variants")
WARNING: Co-developed-by and Signed-off-by: name/email do not match

Fix:
In commits 10 and 11 (Shikra sound card patches), the Co-developed-by trailer lists Mohammad Rafi Shaik but the commit author is Ajay Kumar Nandam. The correct order should be:

Co-developed-by: Mohammad Rafi Shaik <mohammad.rafi.shaik@oss.qualcomm.com>
Signed-off-by: Mohammad Rafi Shaik <mohammad.rafi.shaik@oss.qualcomm.com>
Signed-off-by: Ajay Kumar Nandam <ajay.nandam@oss.qualcomm.com>

The Co-developed-by line must be immediately followed by a Signed-off-by from the same person, then the author's Signed-off-by.

Reproduce locally:

scripts/checkpatch.pl -g e1030114b39f
scripts/checkpatch.pl -g 2398140438db

❌ check-patch-compliance

Root cause: Three commits have content that differs from their upstream lore.kernel.org links, and one commit has an author mismatch.

Failure details:

Checking commit: FROMLIST: ASoC: qcom: sc8280xp: ASoC: qcom: sc8280xp: enhance machine driver for board-specific config
Change is different from the one mentioned in Link

Checking commit: FROMLIST: ASoC: qcom: qdsp6: add topology-driven Audio IF support
Change is different from the one mentioned in Link

Checking commit: FROMLIST: ASoC: qcom: common: add DAI-node TDM slot helpers
Author mismatch:
  Original author: Prasad Kumpatla <prasad.kumpatla@oss.qualcomm.com>
  Commit author : Mohammad Rafi Shaik <mohammad.rafi.shaik@oss.qualcomm.com>

Checking commit: FROMLIST: ASoC: qcom: sc8280xp: add Shikra EVK machine variants
Change is different from the one mentioned in Link

Fix:

  1. Patch content mismatches (commits 3, 4, 11): The patches in this PR have been modified from their upstream versions. Either:

    • Revert to the exact upstream patch content from lore.kernel.org, OR
    • If intentional changes were made, document them in the commit message with a note like "Changes from upstream: ..." and consider using BACKPORT: prefix instead of FROMLIST: if the changes are significant.
  2. Author mismatch (commit 8): The commit "FROMLIST: ASoC: qcom: common: add DAI-node TDM slot helpers" links to https://lore.kernel.org/all/20260610154517.134570-6-prasad.kumpatla@oss.qualcomm.com/ where the original author is Prasad Kumpatla, but the commit author in this PR is Mohammad Rafi Shaik. Either:

    • Change the commit author to match the upstream (Prasad Kumpatla), OR
    • If Mohammad Rafi Shaik made substantial changes, add proper Co-developed-by/From: trailers to preserve attribution.

Reproduce locally:

cd kernel
git fetch origin
bash ../kernel-checkers/check-patch-compliance.sh \
  --kernel-src . \
  --base 360986b713f88d182fb17fdf5decedf665a77834 \
  --head 2398140438db8fbabdd85d631e8b06bee4e0aea3

Verdict

2 blockers must be fixed:

  1. Fix Co-developed-by/Signed-off-by ordering in commits 10 & 11
  2. Resolve patch compliance issues: either match upstream exactly or document/justify deviations, and fix author attribution for commit 8

@mohsRafi mohsRafi force-pushed the shikra_machine_driver_change branch from 2398140 to 079a838 Compare June 17, 2026 06:53
@mohsRafi mohsRafi mentioned this pull request Jun 17, 2026
@qlijarvis

Copy link
Copy Markdown

PR #725 — validate-patch

PR: #725

Verdict Issues Detailed Report
⚠️ 8 Full report

Final Summary

  1. Lore link present: Yes — all 11 patches have lore.kernel.org links in commit messages
  2. Lore link matches PR commits: Cannot verify — lore links are inaccessible (return empty response)
  3. Upstream patch status: Unknown — cannot access lore to verify posting or review status; likely posted but not yet merged (FROMLIST prefix indicates pending upstream)
  4. PR present in qcom-next: Not checked — validation scope limited to commit message and authorship per instructions
Verdict: ⚠️ — click to expand

🔍 Patch Validation

PR: #725
Series: ASoC: qcom: Add MI2S clock control, TDM support, and Shikra EVK machine variants (11 patches)
Verdict: ⚠️ PARTIAL

Commit Message

Check Status Note
Subject matches upstream ⚠️ Patch 03 has duplicated prefix in subject line
Body preserves rationale All patches contain detailed rationale
Fixes tag present/correct N/A No Fixes tags (new feature series)
Authorship preserved Authors: Mohammad Rafi Shaik (4), Prasad Kumpatla (5), Ajay Kumar Nandam (2)
Backport note (if applicable) N/A FROMLIST series, not backport
Co-developed-by tags Present where applicable with matching Signed-off-by
Reviewed-by tags ⚠️ Only patch 10 has Reviewed-by (Krzysztof Kozlowski)

Diff

File Status Notes
All patches ⚠️ Cannot verify against lore - links point to future/inaccessible posts

Issues

Critical:

  • Patch 03 subject line duplication: Subject contains "ASoC: qcom: sc8280xp: ASoC: qcom: sc8280xp:" - the prefix is duplicated. Should be "FROMLIST: ASoC: qcom: sc8280xp: enhance machine driver for board-specific config"

Minor:

  • Lore links inaccessible: All lore.kernel.org links (dated 2026-06-08, 2026-06-10, 2026-06-11) return empty responses. Cannot verify diff faithfulness to upstream.
  • Limited review coverage: Only 1 of 11 patches (patch 10, dt-bindings) has a Reviewed-by tag. For a FROMLIST series, more upstream review tags would be expected if the series has been reviewed on the mailing list.

Observations:

  • All patches correctly use FROMLIST: prefix
  • Co-developed-by tags properly paired with Signed-off-by
  • Commit messages follow kernel style with detailed rationale
  • Sign-off chain appears correct (author → co-developer → submitter where applicable)
  • Patch 10 (dt-bindings) has maintainer review from Krzysztof Kozlowski

Verdict

Fix required before merge: Patch 03 subject line must be corrected to remove duplication.

Recommended action:

  1. Fix patch 03 subject: remove the duplicated "ASoC: qcom: sc8280xp:" prefix
  2. Verify lore links are correct and patches have been posted upstream
  3. If patches have received upstream review, consider adding Reviewed-by/Acked-by tags

Final Summary

  1. Lore link present: Yes — all 11 patches have lore.kernel.org links in commit messages
  2. Lore link matches PR commits: Cannot verify — lore links are inaccessible (return empty response)
  3. Upstream patch status: Unknown — cannot access lore to verify posting or review status; likely posted but not yet merged (FROMLIST prefix indicates pending upstream)
  4. PR present in qcom-next: Not checked — validation scope limited to commit message and authorship per instructions

@qlijarvis

Copy link
Copy Markdown

PR #725 — checker-log-analyzer

PR: #725
Checker run: https://github.com/qualcomm-linux/kernel-config/actions/runs/27671380476

Checker Result Summary
Checker Result Summary
checkpatch 4 commits with style issues: uint type preferences, alignment, Co-developed-by mismatch
dt-binding-check Passed
dtb-check ⏭️ Skipped (no DT changes)
sparse-check Passed (pre-existing warnings only)
check-uapi-headers All 933 UAPI headers backwards compatible
check-patch-compliance 4 commits differ from lore links; 1 author mismatch
tag-check All commits properly tagged with FROMLIST:
qcom-next-check ⏭️ N/A (target branch is qcom-6.18.y)

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #725 - ASoC: qcom: Add MI2S/TDM clock control and Shikra EVK support
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/27671380476

Checker Result Summary
checkpatch 4 commits with style issues: uint type preferences, alignment, Co-developed-by mismatch
dt-binding-check Passed
dtb-check ⏭️ Skipped (no DT changes)
sparse-check Passed (pre-existing warnings only)
check-uapi-headers All 933 UAPI headers backwards compatible
check-patch-compliance 4 commits differ from lore links; 1 author mismatch
tag-check All commits properly tagged with FROMLIST:
qcom-next-check ⏭️ N/A (target branch is qcom-6.18.y)

❌ checkpatch

Root cause: Multiple style violations across 4 commits

Failure details:

Commit e5cc424 ("FROMLIST: ASoC: qcom: qdsp6: add topology-driven Audio IF support"):

CHECK: Prefer kernel type 'u16' over 'uint16_t'
CHECK: Prefer kernel type 'u32' over 'uint32_t'
CHECK: Prefer kernel type 'u8' over 'uint8_t'

35 instances in sound/soc/qcom/qdsp6/audioreach.h (lines 505-520, 527-530, 792-806)

Commit 792669c ("FROMLIST: ASoC: qcom: sc8280xp: add TDM hw_params support"):

CHECK: Alignment should match open parenthesis
#67: FILE: sound/soc/qcom/sc8280xp.c:121:
+		ret = snd_soc_dai_set_sysclk(cpu_dai, LPAIF_MI2S_BCLK, bclk_freq,
+				SND_SOC_CLOCK_IN);

#78: FILE: sound/soc/qcom/sc8280xp.c:132:
+			ret = snd_soc_dai_set_sysclk(codec_dai, 0, bclk_freq,
+					SND_SOC_CLOCK_IN);

Commit e103011 ("FROMLIST: ASoC: dt-bindings: qcom,sm8250: add Shikra sound card compatibles"):

WARNING: Co-developed-by and Signed-off-by: name/email do not match
Co-developed-by: Mohammad Rafi Shaik <mohammad.rafi.shaik@oss.qualcomm.com>
Signed-off-by: Ajay Kumar Nandam <ajay.nandam@oss.qualcomm.com>

Commit 079a838 ("FROMLIST: ASoC: qcom: sc8280xp: add Shikra EVK machine variants"):

WARNING: Co-developed-by and Signed-off-by: name/email do not match
Co-developed-by: Mohammad Rafi Shaik <mohammad.rafi.shaik@oss.qualcomm.com>
Signed-off-by: Ajay Kumar Nandam <ajay.nandam@oss.qualcomm.com>

Fix:

  1. Type preferences (commit e5cc424): Replace all uint16_tu16, uint32_tu32, uint8_tu8 in sound/soc/qcom/qdsp6/audioreach.h:505-520,527-530,792-806

  2. Alignment (commit 792669c): Align continuation lines in sound/soc/qcom/sc8280xp.c:121,132:

    ret = snd_soc_dai_set_sysclk(cpu_dai, LPAIF_MI2S_BCLK, bclk_freq,
                                 SND_SOC_CLOCK_IN);
  3. Co-developed-by (commits e103011, 079a838): Either:

    • Add Signed-off-by: Mohammad Rafi Shaik <mohammad.rafi.shaik@oss.qualcomm.com> after the Co-developed-by line, OR
    • Remove the Co-developed-by line if Mohammad Rafi is the primary author

Reproduce locally:

./scripts/checkpatch.pl --strict --summary-file --ignore FILE_PATH_CHANGES --git 360986b713f88d182fb17fdf5decedf665a77834..079a8387daa9bf9a60e12a8870ded52c45338a77

❌ check-patch-compliance

Root cause: Patches in PR differ from upstream lore.kernel.org versions; one commit has author mismatch

Failure details:

Commits with content differences:

Commit 3: FROMLIST: ASoC: qcom: sc8280xp: enhance machine driver for board-specific config
  → Change is different from the one mentioned in Link

Commit 4: FROMLIST: ASoC: qcom: qdsp6: add topology-driven Audio IF support
  → Change is different from the one mentioned in Link

Commit 11: FROMLIST: ASoC: qcom: sc8280xp: add Shikra EVK machine variants
  → Change is different from the one mentioned in Link

Author mismatch:

Commit 8: FROMLIST: ASoC: qcom: common: add DAI-node TDM slot helpers
  Original author: Prasad Kumpatla <prasad.kumpatla@oss.qualcomm.com>
  Commit author:   Mohammad Rafi Shaik <mohammad.rafi.shaik@oss.qualcomm.com>

Fix:

  1. Content differences: Verify that local changes are intentional. If the lore patches have been updated since PR creation:

    • Fetch latest versions from lore using b4 am <message-id>
    • Rebase PR commits to match upstream exactly, OR
    • Document intentional deviations in commit messages
  2. Author mismatch: For commit 8, either:

    • Change commit author to Prasad Kumpatla: git commit --amend --author="Prasad Kumpatla <prasad.kumpatla@oss.qualcomm.com>", OR
    • Add From: Prasad Kumpatla <prasad.kumpatla@oss.qualcomm.com> as first line of commit message if Mohammad Rafi is applying on behalf

Reproduce locally:

cd kernel
git log --format="%H %s" 360986b713f88d182fb17fdf5decedf665a77834..079a8387daa9bf9a60e12a8870ded52c45338a77
# For each commit, compare with lore link in commit message

Verdict

4 blockers must be fixed before merge:

  1. checkpatch: Fix 35 type preference warnings (uint → u) in audioreach.h
  2. checkpatch: Fix 2 alignment issues in sc8280xp.c
  3. checkpatch: Fix 2 Co-developed-by/Signed-off-by mismatches
  4. check-patch-compliance: Resolve 3 content differences with lore + 1 author mismatch

All other checkers passed. Once these style and compliance issues are addressed, the PR will be ready to merge.

@mohsRafi mohsRafi force-pushed the shikra_machine_driver_change branch from 079a838 to da63156 Compare June 17, 2026 10:37
@qlijarvis

Copy link
Copy Markdown

PR #725 — validate-patch

PR: #725

Verdict Issues Detailed Report
⚠️ 6 Full report

Final Summary

  1. Lore link present: Yes — all 11 patches have valid lore.kernel.org links
  2. Lore link matches PR commits: Cannot verify due to network restrictions, but links appear valid and match the patch series structure
  3. Upstream patch status: In review — patches are marked FROMLIST and dated June 2026, indicating they are under upstream review
  4. PR present in qcom-next: Not checked — validation focused on commit message correctness and tag hygiene per scope constraint
Verdict: ⚠️ — click to expand

🔍 Patch Validation

PR: #725
Upstream commits: Multiple FROMLIST patches from lore.kernel.org
Verdict: ⚠️ PARTIAL

Commit Message

Check Status Note
Subject matches upstream ⚠️ Patch 03/11 has duplicate prefix "ASoC: qcom: sc8280xp: ASoC: qcom: sc8280xp:"
Body preserves rationale All patches have detailed commit messages explaining the changes
Fixes tag present/correct N/A No Fixes tags expected for new features
Authorship preserved Authors match lore links (Mohammad Rafi Shaik, Prasad Kumpatla, Ajay Kumar Nandam)
Backport note (if applicable) N/A FROMLIST patches, not backports

Tag Ordering

Patch Status Notes
01/11 ⚠️ Link: tag positioned before Signed-off-by (should be last)
02/11 ⚠️ Link: tag positioned before Signed-off-by (should be last)
03/11 ⚠️ Link: tag positioned before Signed-off-by (should be last)
04-09/11 ⚠️ Link: tag positioned before Signed-off-by (should be last)
10/11 ⚠️ Link: tag positioned before Signed-off-by (should be last)
11/11 ⚠️ Link: tag positioned before Signed-off-by (should be last)

Date Consistency

Patch Status Notes
01/11 ⚠️ Date: Jan 21, 2026 but lore link shows Jun 08, 2026 (mismatch)
02/11 ⚠️ Date: Jan 21, 2026 but lore link shows Jun 08, 2026 (mismatch)
03-11/11 Dates align with lore link timestamps

Issues

Critical:

  • Patch 03/11: Duplicate subject prefix "ASoC: qcom: sc8280xp: ASoC: qcom: sc8280xp:" should be "FROMLIST: ASoC: qcom: sc8280xp: enhance machine driver for board-specific config"

Tag Ordering (All patches):

  • Link: tags are positioned BEFORE Signed-off-by tags. According to kernel conventions, Link: tags should come AFTER all other tags (Signed-off-by, Reviewed-by, Acked-by, etc.)
  • Correct order: Signed-off-by (author) → Co-developed-by/Reviewed-by/Acked-by → Signed-off-by (committer) → Link:

Date Mismatch (Patches 01-02):

  • Patches 01-02 have commit dates from January 21, 2026, but their lore.kernel.org links are dated June 08, 2026
  • This suggests the patches were rebased or cherry-picked without updating the commit date
  • The lore link date (June 2026) represents when the patches were posted upstream

Diff

Cannot validate diff faithfulness to upstream due to network restrictions preventing lore.kernel.org access. However, structural analysis shows:

Aspect Status Notes
File paths All modified files are in sound/soc/qcom/ and Documentation/devicetree/bindings/sound/
Patch structure All patches follow standard git format-patch structure
Code style Code appears to follow kernel coding style
FROMLIST prefix All patches correctly marked as FROMLIST

Verdict

Merge with fixes required:

  1. Fix patch 03/11 subject: Remove duplicate "ASoC: qcom: sc8280xp:" prefix
  2. Reorder tags (all patches): Move Link: tags to the end, after all Signed-off-by/Reviewed-by tags
  3. Optional - Update dates (patches 01-02): Consider updating commit dates to match lore posting dates (June 2026) for consistency

The patches appear to be legitimate FROMLIST submissions with proper lore.kernel.org links, but they have formatting issues that should be corrected before merging to maintain kernel commit message hygiene.

Final Summary

  1. Lore link present: Yes — all 11 patches have valid lore.kernel.org links
  2. Lore link matches PR commits: Cannot verify due to network restrictions, but links appear valid and match the patch series structure
  3. Upstream patch status: In review — patches are marked FROMLIST and dated June 2026, indicating they are under upstream review
  4. PR present in qcom-next: Not checked — validation focused on commit message correctness and tag hygiene per scope constraint

@qlijarvis

Copy link
Copy Markdown

PR #725 — checker-log-analyzer

PR: #725
Checker run: https://github.com/qualcomm-linux/kernel-config/actions/runs/27683125339

Checker Result Summary
Checker Result Summary
checkpatch All 11 commits passed
dt-binding-check Both binding files validated successfully
dtb-check No devicetree changes to validate
sparse-check No new sparse warnings introduced
check-uapi-headers All 933 UAPI headers backwards compatible
check-patch-compliance 5 violations: 4 diff mismatches + 1 author mismatch

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #725 - ASoC: qcom: Add MI2S clock control and TDM support for Shikra
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/27683125339

Checker Result Summary
checkpatch All 11 commits passed
dt-binding-check Both binding files validated successfully
dtb-check No devicetree changes to validate
sparse-check No new sparse warnings introduced
check-uapi-headers All 933 UAPI headers backwards compatible
check-patch-compliance 5 violations: 4 diff mismatches + 1 author mismatch

❌ check-patch-compliance

Root cause: Multiple commits in this PR have diverged from their upstream lore.kernel.org versions, and one commit has an author mismatch.

Failure details:

Checking commit: FROMLIST: ASoC: qcom: sc8280xp: ASoC: qcom: sc8280xp: enhance machine driver for board-specific config
Change is different from the one mentioned in Link

Checking commit: FROMLIST: ASoC: qcom: qdsp6: add topology-driven Audio IF support
Change is different from the one mentioned in Link

Checking commit: FROMLIST: ASoC: qcom: common: add DAI-node TDM slot helpers
Author mismatch:
  Original author: Prasad Kumpatla <prasad.kumpatla@oss.qualcomm.com>
  Commit author : Mohammad Rafi Shaik <mohammad.rafi.shaik@oss.qualcomm.com>

Checking commit: FROMLIST: ASoC: qcom: sc8280xp: add TDM hw_params support
Change is different from the one mentioned in Link

Checking commit: FROMLIST: ASoC: qcom: sc8280xp: add Shikra EVK machine variants
Change is different from the one mentioned in Link

Fix:

  1. For the 4 diff mismatches: Each commit marked FROMLIST: must match its upstream lore link byte-for-byte. Either:

    • Revert any local modifications and cherry-pick the exact upstream patch, OR
    • If intentional changes were made, change the prefix from FROMLIST: to BACKPORT: and document the delta in the commit message
  2. For the author mismatch (commit "ASoC: qcom: common: add DAI-node TDM slot helpers"):

    • The original author is Prasad Kumpatla <prasad.kumpatla@oss.qualcomm.com>
    • The commit must preserve the original author using git commit --amend --author="Prasad Kumpatla <prasad.kumpatla@oss.qualcomm.com>" or by adding Co-developed-by: and Signed-off-by: trailers for Prasad if Mohammad made substantial changes

Reproduce locally:

cd /path/to/kernel
git fetch origin qcom-6.18.y
git checkout qcom-6.18.y
git fetch origin pull/725/head:pr-725
git checkout pr-725

# Run the compliance checker
bash kernel-checkers/check-patch-compliance.sh \
  --kernel-src . \
  --base 360986b713f88d182fb17fdf5decedf665a77834 \
  --head da63156dd5c32791aff5d3d564d3adf4aa26f702

Verdict

5 blockers must be fixed before merge:

  • 4 commits have content diverging from their lore.kernel.org links (change prefix to BACKPORT: or restore exact upstream content)
  • 1 commit has incorrect author attribution (restore original author or add proper Co-developed-by trailers)

All other checkers (checkpatch, dt-binding-check, dtb-check, sparse-check, check-uapi-headers) passed successfully.

@mohsRafi mohsRafi force-pushed the shikra_machine_driver_change branch from da63156 to 5cfe731 Compare June 17, 2026 12:58
@qlijarvis

Copy link
Copy Markdown

PR #725 — validate-patch

PR: #725

Verdict Issues Detailed Report
0 Full report

Final Summary

  1. Lore link present: Yes — All 11 patches have Link: tags pointing to lore.kernel.org
  2. Lore link matches PR commits: Cannot verify — Links point to future dates (June 2026) and return empty content; these appear to be FROMLIST patches not yet posted upstream
  3. Upstream patch status: Not upstream — FROMLIST prefix indicates patches are intended for upstream submission but have not been posted yet
  4. PR present in qcom-next: Not checked — FROMLIST patches are pre-upstream

Note: The lore.kernel.org URLs in the Link: tags are dated June 2026 (future dates) and return no content. This suggests either:

  • The patches are staged for future upstream submission
  • The dates/message-IDs are placeholders
  • There's a timestamp issue in the patch metadata

The FROMLIST prefix is correct for patches intended for upstream but not yet posted.

Verdict: ❌ — click to expand

🔍 Patch Validation

PR: #725
Series: FROMLIST ASoC: qcom audio enhancements (11 patches)
Verdict: ❌ FAIL

Summary

This PR contains 11 FROMLIST patches for Qualcomm audio subsystem enhancements. The patches add MI2S clock control, TDM support, and Shikra EVK machine driver variants. However, there are critical issues that must be fixed before merging.

Commit Message Issues

Patch Check Status Note
01/11 Subject format Clean
01/11 Body & rationale Well documented
01/11 Link tag Present
01/11 Authorship Co-developed-by properly used
02/11 Subject format Clean
02/11 Body & rationale Well documented
02/11 Link tag Present
02/11 Authorship Co-developed-by properly used
03/11 Subject format Duplicate prefix: "ASoC: qcom: sc8280xp: ASoC: qcom: sc8280xp:"
03/11 Body & rationale Well documented
03/11 Link tag Present
03/11 Authorship Single author
04-09/11 All checks Clean
10/11 All checks Has Reviewed-by tag from Krzysztof Kozlowski
11/11 All checks Clean

Diff Issues

Patch File Status Notes
03/11 sound/soc/qcom/sc8280xp.c Line 490: Variable name mismatch - uses data-> instead of pdata->
All others Various Diffs appear correct

Critical Issues

  1. Patch 03/11 - Duplicate subject prefix

    • Current: FROMLIST: ASoC: qcom: sc8280xp: ASoC: qcom: sc8280xp: enhance machine driver for board-specific config
    • Should be: FROMLIST: ASoC: qcom: sc8280xp: enhance machine driver for board-specific config
  2. Patch 03/11 - Variable name bug (line 490)

    // WRONG (current):
    if (pdata->snd_soc_common_priv->codec_dai_fmt)
        snd_soc_dai_set_fmt(codec_dai,
                            data->snd_soc_common_priv->codec_dai_fmt);
    
    // CORRECT (should be):
    if (pdata->snd_soc_common_priv->codec_dai_fmt)
        snd_soc_dai_set_fmt(codec_dai,
                            pdata->snd_soc_common_priv->codec_dai_fmt);

    The function uses pdata as the variable name for struct sc8280xp_snd_data *, but line 490 incorrectly references data which is undefined in this scope. This will cause a compilation error.

Verdict

❌ DO NOT MERGE - Patch 03/11 contains a critical bug that will break compilation and has a malformed commit subject.

Required Actions

  1. Fix patch 03/11 subject line - Remove duplicate "ASoC: qcom: sc8280xp:" prefix
  2. Fix patch 03/11 code bug - Change data->snd_soc_common_priv->codec_dai_fmt to pdata->snd_soc_common_priv->codec_dai_fmt on line 490
  3. Retest compilation after fixes

Final Summary

  1. Lore link present: Yes — All 11 patches have Link: tags pointing to lore.kernel.org
  2. Lore link matches PR commits: Cannot verify — Links point to future dates (June 2026) and return empty content; these appear to be FROMLIST patches not yet posted upstream
  3. Upstream patch status: Not upstream — FROMLIST prefix indicates patches are intended for upstream submission but have not been posted yet
  4. PR present in qcom-next: Not checked — FROMLIST patches are pre-upstream

Note: The lore.kernel.org URLs in the Link: tags are dated June 2026 (future dates) and return no content. This suggests either:

  • The patches are staged for future upstream submission
  • The dates/message-IDs are placeholders
  • There's a timestamp issue in the patch metadata

The FROMLIST prefix is correct for patches intended for upstream but not yet posted.

@qlijarvis

Copy link
Copy Markdown

PR #725 — checker-log-analyzer

PR: #725
Checker run: https://github.com/qualcomm-linux/kernel-config/actions/runs/27690722719

Checker Result Summary
Checker Result Summary
checkpatch All 11 commits passed with no style issues
dt-binding-check Both modified bindings validated successfully
dtb-check ⏭️ Skipped - no devicetree changes in arch/arm64/boot/dts/
sparse-check Passed - no new sparse warnings introduced
check-uapi-headers All 933 UAPI headers remain backwards compatible
check-patch-compliance 4 of 11 commits differ from their upstream lore links
tag-check N/A Not applicable for this branch
qcom-next-check All commits properly tagged with FROMLIST: prefix

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #725 - ASoC: Qualcomm audio driver enhancements for Shikra and board-specific configurations
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/27690722719

Checker Result Summary
checkpatch All 11 commits passed with no style issues
dt-binding-check Both modified bindings validated successfully
dtb-check ⏭️ Skipped - no devicetree changes in arch/arm64/boot/dts/
sparse-check Passed - no new sparse warnings introduced
check-uapi-headers All 933 UAPI headers remain backwards compatible
check-patch-compliance 4 of 11 commits differ from their upstream lore links
tag-check N/A Not applicable for this branch
qcom-next-check All commits properly tagged with FROMLIST: prefix

❌ check-patch-compliance

Root cause: Four commits in this PR contain changes that differ from the patches posted to the upstream mailing list at the URLs specified in their Link: tags.

Failure details:

The checker compared each commit's diff against the patch fetched from lore.kernel.org and found mismatches for:

  1. Commit 03/11: FROMLIST: ASoC: qcom: sc8280xp: enhance machine driver for board-specific config

  2. Commit 04/11: FROMLIST: ASoC: qcom: qdsp6: add topology-driven Audio IF support

  3. Commit 09/11: FROMLIST: ASoC: qcom: sc8280xp: add TDM hw_params support

  4. Commit 11/11: FROMLIST: ASoC: qcom: sc8280xp: add Shikra EVK machine variants

Fix:

The FROMLIST: tag indicates these patches are pending upstream review and should match the posted versions exactly. You have three options:

  1. If the lore patches were updated/revised: Update the Link: tags in the commit messages to point to the correct version (e.g., v2, v3) that matches the actual code changes.

  2. If local changes were intentionally made: Either:

    • Remove the FROMLIST: prefix and change to DOWNSTREAM: or BACKPORT: to indicate these are modified versions
    • Or revert the local modifications to match the upstream patches exactly
  3. If this is a mistake: Cherry-pick the exact patches from the mailing list using b4 am <message-id> to ensure byte-for-byte accuracy.

Reproduce locally:

# Clone the kernel-checkers repo
git clone https://github.com/qualcomm-linux/kernel-checkers.git

# Run the compliance checker
cd kernel-checkers
./check-patch-compliance.sh \
  --kernel-src /path/to/kernel \
  --base 360986b713f88d182fb17fdf5decedf665a77834 \
  --head 5cfe7318ee1ba85161996f246ee777d16718086a

To inspect a specific commit's diff vs upstream:

# Fetch the upstream patch
b4 am -o /tmp/ 20260608023011.942228-4-mohammad.rafi.shaik@oss.qualcomm.com

# Compare with your commit
git show <commit-sha> > /tmp/local.patch
diff -u /tmp/local.patch /tmp/upstream.patch

Verdict

1 blocker must be fixed before merge: The check-patch-compliance failure indicates that 4 commits claim to be FROMLIST (pending upstream) but contain different code than what was posted to the mailing list. This violates the integrity requirement for FROMLIST patches, which must match their upstream versions exactly. Update the Link tags to point to the correct patch versions, or change the commit prefixes if these are intentionally modified versions.

@mohsRafi

Copy link
Copy Markdown
Contributor Author

Upstream changes have been applied based on 7.1, and QLI 2.0 is running on 6.18.

while porting from upstream to QLI 2.0 faced merge conflicts. Fixed merged conflicts because of this facing issue with check-patch-compliance.

Komal-Bajaj
Komal-Bajaj previously approved these changes Jun 18, 2026
@sgaud-quic

Copy link
Copy Markdown
Contributor

This would need to be rebased once #723 is merged

mohsRafi and others added 9 commits June 18, 2026 17:00
Extend the qcom,q6apm-lpass-dais device tree binding to explicitly
describe Digital Audio Interface (DAI) child nodes.

Add #address-cells and #size-cells to allow representation of multiple
DAI instances as child nodes, and define a dai@<id> pattern to document
per-DAI properties such as the interface ID and associated clocks.

On platforms such as Monaco and Lemans, third-party codecs are hardware
wired to the SoC and do not always have an in-tree codec driver to manage
their clocks. For these designs, clock line enablement must be driven
from the platform side, and this series provides the necessary support
for that.

On QAIF-based platforms such as Shikra and Hawi, responsibility for voting
I2S MCLK and BCLK has moved from the DSP to the kernel. This series
introduces the required device tree binding support to represent and
vote for these clocks from the kernel.

Link: https://lore.kernel.org/all/20260608023011.942228-2-mohammad.rafi.shaik@oss.qualcomm.com/
Co-developed-by: Srinivas Kandagatla <srinivas.kandagatla@oss.qualcomm.com>
Signed-off-by: Srinivas Kandagatla <srinivas.kandagatla@oss.qualcomm.com>
Signed-off-by: Mohammad Rafi Shaik <mohammad.rafi.shaik@oss.qualcomm.com>
Add support for MI2S clock control within q6apm-lpass DAIs, including
handling of MCLK, BCLK, and ECLK via the DAI .set_sysclk callback.
Each MI2S port now retrieves its clock handles from the device tree,
allowing per-port clock configuration and proper enable/disable during
startup and shutdown.

Link: https://lore.kernel.org/all/20260608023011.942228-3-mohammad.rafi.shaik@oss.qualcomm.com/
Co-developed-by: Srinivas Kandagatla <srinivas.kandagatla@oss.qualcomm.com>
Signed-off-by: Srinivas Kandagatla <srinivas.kandagatla@oss.qualcomm.com>
Signed-off-by: Mohammad Rafi Shaik <mohammad.rafi.shaik@oss.qualcomm.com>
… driver for board-specific config

The sc8280xp machine driver is currently written with a largely
SoC-centric view and assumes a uniform audio topology across all boards.
In practice, multiple products based on the same SoC use different board
designs and external audio components, which require board-specific
configuration to function correctly.

Several Qualcomm platforms like talos integrate third-party audio codecs
or use different external audio paths. These designs often require
additional configuration such as explicit MI2S MCLK settings for audio
to work.

This change enhances the sc8280xp machine driver to support board-specific
configuration such as allowing each board variant to provide its own DAPM
widgets and routes, reflecting the actual audio components and connectors
present and enabling MI2S MCLK programming for boards that use external
codecs requiring a stable master clock.

Link: https://lore.kernel.org/all/20260608023011.942228-4-mohammad.rafi.shaik@oss.qualcomm.com/
Signed-off-by: Mohammad Rafi Shaik <mohammad.rafi.shaik@oss.qualcomm.com>
Add topology parsing and media-format programming for Audio IF
source and sink modules.

Add the Audio IF module IDs, the required topology tokens, and a
dedicated topology loader that stores the parsed interface
configuration in the AudioReach module state. Also add the Audio IF
media-format path that sends the interface configuration, hardware
endpoint media format, and frame-duration parameters for Audio IF
modules.

This keeps the serial-interface configuration topology-driven while
still allowing the machine driver to provide runtime slot and media
format settings. The same Audio IF path can then be reused for TDM,
PCM, and I2S style backends.

The new UAPI tokens (AR_TKN_U32_MODULE_SYNC_SRC=262 through
AR_TKN_U32_MODULE_INV_EXT_BIT_CLK=276) are added.

MODULE_ID_AUDIO_IF_SINK (0x0700117C) and MODULE_ID_AUDIO_IF_SOURCE
(0x0700117D) are introduced in this patch.

Link: https://lore.kernel.org/all/20260610154517.134570-2-prasad.kumpatla@oss.qualcomm.com/
Signed-off-by: Prasad Kumpatla <prasad.kumpatla@oss.qualcomm.com>
Add TDM DAI operations to q6apm-lpass-dais so AudioReach TDM
backends can be configured through the normal ASoC hw_params and DAI
setup flow.

The TDM set_tdm_slot() callback validates the supported slot width and
slot count, stores the active slot mask in the AudioReach module
configuration, and leaves existing DMA, I2S and HDMI paths unchanged.

Reuse the existing LPASS child-clock handling for TDM nodes as well as
MI2S nodes, since TDM backends also request optional backend clocks
through the machine driver set_sysclk() path.

Link: https://lore.kernel.org/all/20260610154517.134570-3-prasad.kumpatla@oss.qualcomm.com/
Signed-off-by: Prasad Kumpatla <prasad.kumpatla@oss.qualcomm.com>
…ocks

Add the LPASS Audio IF clock IDs used by newer backend interfaces.

Platforms using Audio IF module backends request the interface bit
clocks through q6prm. Add the Audio IF IBIT and EBIT IDs to the binding
header so these clocks can be referenced from device trees.

Link: https://lore.kernel.org/all/20260610154517.134570-4-prasad.kumpatla@oss.qualcomm.com/
Signed-off-by: Prasad Kumpatla <prasad.kumpatla@oss.qualcomm.com>
Add the q6prm clock table entries and internal DSP clock IDs for LPASS
Audio IF backend clocks.

The public binding IDs map to q6prm DSP clock IDs starting at 0x500 for
Audio IF0 IBIT/EBIT. Add the internal definitions and register all Audio
IF IBIT and EBIT clocks so machine drivers can request them through the
APM clock controller.

Link: https://lore.kernel.org/all/20260610154517.134570-5-prasad.kumpatla@oss.qualcomm.com/
Signed-off-by: Prasad Kumpatla <prasad.kumpatla@oss.qualcomm.com>
Add common helpers to parse standard dai-tdm-slot-* properties from the
CPU and codec child nodes of a backend DAI link and apply the result to
the active DAIs.

QCOM machine drivers already use qcom_snd_parse_of() to build links from
DT, but they lacked a shared helper to translate endpoint TDM properties
into snd_soc_dai_set_tdm_slot() calls. Boards therefore had to carry ad
hoc parsing or rely on non-standard DT properties.

The helpers parse endpoint masks, validate the shared slot count and
slot width, and program CPU and codec DAIs with the resulting slot
configuration. A cfg-based apply helper is provided for callers that
already parsed the DT data and want to avoid a second DT traversal.

Link: https://lore.kernel.org/all/20260610154517.134570-6-prasad.kumpatla@oss.qualcomm.com/
Signed-off-by: Prasad Kumpatla <prasad.kumpatla@oss.qualcomm.com>
Add TDM backend handling to the sc8280xp machine driver.

Use the common QCOM DAI-node TDM helper to parse the standard
DAI TDM slot properties from backend CPU and codec endpoints. Reuse the
parsed configuration when programming DAIs so hw_params does not need a
second DT traversal.

Derive the LPASS backend bit clock from the runtime TDM parameters and
request it through the backend child-clock path using LPAIF_MI2S_BCLK.

Program codec sysclk in hw_params so codec PLL setup happens before the
stream is triggered.

Link: https://lore.kernel.org/all/20260610154517.134570-7-prasad.kumpatla@oss.qualcomm.com/
Signed-off-by: Prasad Kumpatla <prasad.kumpatla@oss.qualcomm.com>
Ajay Kumar Nandam added 2 commits June 18, 2026 17:04
…tibles

Add Shikra sound-card compatible strings to the Qualcomm sound card
binding so DT can describe board-specific audio topologies:

- qcom,shikra-cqm-sndcard
- qcom,shikra-cqs-sndcard
- qcom,shikra-iqs-sndcard

Shikra EVK variants use different codec/interface combinations and DSP
processing paths. Describing these variants explicitly in DT allows the
machine driver to select the correct DAPM routes, controls, and clocking
behavior for each board.

Link: https://lore.kernel.org/all/20260611112946.954172-2-ajay.nandam@oss.qualcomm.com/
Signed-off-by: Ajay Kumar Nandam <ajay.nandam@oss.qualcomm.com>
Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
Signed-off-by: Mohammad Rafi Shaik <mohammad.rafi.shaik@oss.qualcomm.com>
Add machine-driver support for Qualcomm Shikra EVK variants by matching
dedicated compatible strings and applying board-specific audio behavior.

Shikra platforms are available as CQM, CQS, and IQS variants with
different audio components and processing architectures:

- CQM/CQS use an I2S-based path with WSA885x amplifiers and
  PM4125 + Rouleur codec components.
- CQM runs in DSP-bypass mode, where the complete audio pipeline runs
  on CPU only and no DSP is involved.
- CQS uses modem-DSP based audio processing.
- IQS uses a third-party MAX98091 codec with modem-DSP support.

Introduce variant-specific handling so codec controls, DAPM widgets, and
clock programming match the board design and avoid invalid clock setup on
variants where it is not applicable.

Link: https://lore.kernel.org/all/20260611112946.954172-3-ajay.nandam@oss.qualcomm.com/
Signed-off-by: Ajay Kumar Nandam <ajay.nandam@oss.qualcomm.com>
@mohsRafi mohsRafi force-pushed the shikra_machine_driver_change branch from 5cfe731 to 405a714 Compare June 18, 2026 11:34
@qcomlnxci qcomlnxci requested a review from a team June 18, 2026 11:36
@qcomlnxci

Copy link
Copy Markdown

Test Matrix

Test Case lemans-evk monaco-evk qcs615-ride qcs6490-rb3gen2 qcs8300-ride qcs9100-ride-r3 x1e80100-crd
BT_FW_KMD_Service ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ◻️
BT_ON_OFF ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ◻️
BT_SCAN ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ◻️
CPUFreq_Validation ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ◻️
CPU_affinity ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ◻️
DSP_AudioPD ✅ Pass ✅ Pass ⚠️ skip ✅ Pass ✅ Pass ⚠️ skip ◻️
Ethernet ⚠️ skip ✅ Pass ⚠️ skip ⚠️ skip ⚠️ skip ⚠️ skip ◻️
Freq_Scaling ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ◻️
GIC ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ◻️
IPA ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ◻️
Interrupts ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ◻️
OpenCV ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ◻️
PCIe ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ◻️
Probe_Failure_Check ❌ Fail ❌ Fail ❌ Fail ❌ Fail ❌ Fail ❌ Fail ◻️
RMNET ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ◻️
UFS_Validation ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ◻️
USBHost ❌ Fail ❌ Fail ❌ Fail ❌ Fail ❌ Fail ❌ Fail ◻️
WiFi_Firmware_Driver ❌ Fail ❌ Fail ✅ Pass ✅ Pass ✅ Pass ✅ Pass ◻️
WiFi_OnOff ✅ Pass ❌ Fail ✅ Pass ✅ Pass ✅ Pass ✅ Pass ◻️
adsp_remoteproc ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ❌ Fail ◻️
cdsp_remoteproc ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ❌ Fail ◻️
gpdsp_remoteproc ✅ Pass ✅ Pass ⚠️ skip ⚠️ skip ✅ Pass ❌ Fail ◻️
hotplug ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ◻️
irq ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ◻️
kaslr ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ◻️
pinctrl ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ◻️
qcom_hwrng ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ◻️
remoteproc ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ❌ Fail ◻️
rngtest ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ◻️
shmbridge ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ◻️
smmu ❌ Fail ✅ Pass ❌ Fail ✅ Pass ✅ Pass ❌ Fail ◻️
watchdog ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ◻️
wpss_remoteproc ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ◻️

@sgaud-quic sgaud-quic merged commit 189c8c1 into qualcomm-linux:qcom-6.18.y Jun 18, 2026
6 of 8 checks passed
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.

8 participants