Skip to content

QLI2.0 | Shikra SoC boot enablement: LLCC, EDAC, and TLMM GPIO reserved ranges#740

Merged
sgaud-quic merged 3 commits into
qualcomm-linux:qcom-6.18.yfrom
apateriy-qcom:qcom-6.18.y-boot
Jun 19, 2026
Merged

QLI2.0 | Shikra SoC boot enablement: LLCC, EDAC, and TLMM GPIO reserved ranges#740
sgaud-quic merged 3 commits into
qualcomm-linux:qcom-6.18.yfrom
apateriy-qcom:qcom-6.18.y-boot

Conversation

@apateriy-qcom

@apateriy-qcom apateriy-qcom commented Jun 18, 2026 •
edited by Komal-Bajaj
Loading

Copy link
Copy Markdown

Summary

This series adds boot-related enablement for the Shikra SoC on the 6.18.y branch, covering Last Level Cache (LLCC)
configuration, optional EDAC IRQ setup, and TLMM GPIO reservations across the Shikra EVK variants.

CRs-Fixed: 4576473
QLI JIRA Exception: https://jira-dc.qualcomm.com/jira/browse/QLIJIRA-138

@qswat-orbit-external

qswat-orbit-external Bot commented Jun 18, 2026

Copy link
Copy Markdown

Merge Check Failed: CR Not Eligible for Merge

CR 4576473 is not eligible for merge.

The parent software image for kernel.qli.2.0 is not development complete.

Entity: kernel.qli.2.0
CR: 4576473
Reason: CR_CANNOT_MERGE

Please ensure the CR passes both CCT (ComponentChangeTasks) and ICT (Integration Change Tasks) validations.

@qlijarvis

qlijarvis commented Jun 18, 2026

Copy link
Copy Markdown

PR #740 — validate-patch

PR: #740

Verdict Issues Detailed Report
⚠️ 1 Full report

Final Summary

Commit 1/3 (FROMLIST):

  1. Lore link present: Yes — https://lore.kernel.org/all/20260531-shikra_llcc_conf-v1-1-fa405f5a2404@oss.qualcomm.com/
  2. Lore link matches PR commits: Cannot verify — network access restricted; lore.kernel.org unreachable
  3. Upstream patch status: In review — FROMLIST prefix indicates posted to mailing list but not yet merged
  4. PR present in qcom-next: Not checked — no kernel tree access per constraints

Commit 2/3 (PENDING):

  1. Lore link present: No — PENDING prefix; no lore link expected or required
  2. Lore link matches PR commits: N/A — no lore link to compare against
  3. Upstream patch status: N/A — vendor-only change, not posted upstream
  4. PR present in qcom-next: Not checked — PENDING vendor-only commit

Commit 3/3 (PENDING):

  1. Lore link present: No — PENDING prefix; no lore link expected or required
  2. Lore link matches PR commits: N/A — no lore link to compare against
  3. Upstream patch status: N/A — vendor-only change, not posted upstream
  4. PR present in qcom-next: Not checked — PENDING vendor-only commit
Verdict: ⚠️ — click to expand

🔍 Patch Validation

PR: #740
Commits: 3 patches (1 FROMLIST, 2 PENDING)
Verdict: ⚠️ PARTIAL

Commit 1/3: FROMLIST: soc: qcom: llcc: Add configuration data for Shikra SoC

Upstream commit: https://lore.kernel.org/all/20260531-shikra_llcc_conf-v1-1-fa405f5a2404@oss.qualcomm.com/

Commit Message

Check Status Note
Subject format ✅ Proper FROMLIST prefix; descriptive subject
Body preserves rationale ✅ Concise description of change
Fixes tag present/correct N/A Not a fix; new feature addition
Authorship preserved ✅ Original author: Komal Bajaj
Link tag present ✅ Lore link included in commit message
Signed-off-by chain ⚠️ Two SoBs: original author + integrator; second SoB should have context

Diff

File Status Notes
drivers/soc/qcom/llcc-qcom.c ✅ Adds shikra_data[], shikra_cfg[], shikra_cfgs, and of_device_id entry

Issues

  • Dual Signed-off-by without context: The commit has two Signed-off-by tags (Komal Bajaj and Anurag Pateriya). The second SoB suggests Anurag integrated/modified the patch, but there's no explanation in the commit message about what changes were made during integration. If this is a verbatim backport, only the original author's SoB should be present unless Anurag made modifications.

Verdict

Merge with caution — verify that the second Signed-off-by is justified (i.e., Anurag made substantive changes) or remove it if this is a clean cherry-pick from the mailing list.

Commit 2/3: PENDING: arm64: dts: qcom: shikra: Add gpio-reserved-ranges to tlmm

Upstream commit: N/A (PENDING — not yet posted upstream)

Commit Message

Check Status Note
Subject format ✅ Proper PENDING prefix; clear subject
Body preserves rationale ✅ Explains purpose: mark GPIOs used internally by SoC
Fixes tag present/correct N/A Not a fix; new feature/configuration
Authorship ✅ Anurag Pateriya
Backport note N/A Not a backport; original work

Diff

File Status Notes
arch/arm64/boot/dts/qcom/shikra-cqm-evk.dts ✅ Adds gpio-reserved-ranges property
arch/arm64/boot/dts/qcom/shikra-cqs-evk.dts ✅ Adds gpio-reserved-ranges property
arch/arm64/boot/dts/qcom/shikra-iqs-evk.dts ✅ Adds gpio-reserved-ranges property

Issues

None — clean PENDING commit with proper rationale.

Verdict

Merge as-is — well-formed PENDING commit ready for internal integration.

Commit 3/3: PENDING: EDAC/qcom: Skip ECC interrupt setup on Shikra, pre-configured by DSF

Upstream commit: N/A (PENDING — not yet posted upstream)

Commit Message

Check Status Note
Subject format ✅ Proper PENDING prefix; descriptive subject
Body preserves rationale ✅ Detailed explanation of DSF pre-configuration and why driver should skip setup
Fixes tag present/correct N/A Not a fix; platform-specific configuration
Authorship ✅ Faiyaz Mohammed
Backport note N/A Not a backport; original work

Diff

File Status Notes
drivers/soc/qcom/llcc-qcom.c ✅ Sets irq_configured = true in shikra_cfg

Issues

None — clean PENDING commit with excellent technical rationale explaining firmware/driver interaction.

Verdict

Merge as-is — well-documented PENDING commit with clear justification for platform-specific behavior.

Final Summary

Commit 1/3 (FROMLIST):

  1. Lore link present: Yes — https://lore.kernel.org/all/20260531-shikra_llcc_conf-v1-1-fa405f5a2404@oss.qualcomm.com/
  2. Lore link matches PR commits: Cannot verify — network access restricted; lore.kernel.org unreachable
  3. Upstream patch status: In review — FROMLIST prefix indicates posted to mailing list but not yet merged
  4. PR present in qcom-next: Not checked — no kernel tree access per constraints

Commit 2/3 (PENDING):

  1. Lore link present: No — PENDING prefix; no lore link expected or required
  2. Lore link matches PR commits: N/A — no lore link to compare against
  3. Upstream patch status: N/A — vendor-only change, not posted upstream
  4. PR present in qcom-next: Not checked — PENDING vendor-only commit

Commit 3/3 (PENDING):

  1. Lore link present: No — PENDING prefix; no lore link expected or required
  2. Lore link matches PR commits: N/A — no lore link to compare against
  3. Upstream patch status: N/A — vendor-only change, not posted upstream
  4. PR present in qcom-next: Not checked — PENDING vendor-only commit

Overall Assessment

Strengths:

  • All three commits follow proper prefix conventions (FROMLIST, PENDING)
  • Commit messages are clear and provide adequate technical rationale
  • Diffs are focused and surgical — no unrelated changes
  • PENDING commits (2/3, 3/3) are well-documented with excellent justification

Concerns:

  • Commit 1/3: Dual Signed-off-by without explanation. If Anurag Pateriya made modifications during integration, those should be documented in the commit message. If this is a verbatim backport, only the original author's SoB should be present.

Recommendation:

  • Commit 1/3: Request clarification on the second Signed-off-by. If no modifications were made, remove it. If modifications were made, document them.
  • Commits 2/3 and 3/3: Approve as-is.

@qlijarvis

qlijarvis commented Jun 18, 2026

Copy link
Copy Markdown

PR #740 — checker-log-analyzer

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

Checker Result Summary
Checker Result Summary
checkpatch ✅ All 3 commits passed with no style issues
dt-binding-check ⏭️ Skipped - no changes in Documentation/devicetree/bindings
dtb-check ✅ All Shikra DTBs validated successfully
sparse-check ✅ Passed - no new sparse warnings
check-uapi-headers ⏭️ Skipped - no UAPI header changes
check-patch-compliance ❌ FAILED - 2 commits missing subsystem prefix
tag-check N/A Not applicable for qcom-6.18.y branch
qcom-next-check N/A Not applicable for qcom-6.18.y branch

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #740 - Shikra SoC LLCC configuration and device tree updates
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/27757250587

Checker Result Summary
checkpatch ✅ All 3 commits passed with no style issues
dt-binding-check ⏭️ Skipped - no changes in Documentation/devicetree/bindings
dtb-check ✅ All Shikra DTBs validated successfully
sparse-check ✅ Passed - no new sparse warnings
check-uapi-headers ⏭️ Skipped - no UAPI header changes
check-patch-compliance ❌ FAILED - 2 commits missing subsystem prefix
tag-check N/A Not applicable for qcom-6.18.y branch
qcom-next-check N/A Not applicable for qcom-6.18.y branch

❌ check-patch-compliance

Root cause: Two commits with PENDING: prefix do not include the required subsystem prefix after the tag.

Failure details:

Checking commit: PENDING: arm64: dts: qcom: shikra: Add gpio-reserved-ranges to tlmm
Commit summary does not start with a required prefix

Checking commit: PENDING: EDAC/qcom: Skip ECC interrupt setup on Shikra, pre-configured by DSF
Commit summary does not start with a required prefix

The checker expects commit subjects to follow the pattern:

[PREFIX:] subsystem: description

Where PREFIX can be FROMLIST, UPSTREAM, BACKPORT, or PENDING, and must be followed by a subsystem prefix like arm64: dts: or EDAC:.

Current commit subjects:

  • ❌ PENDING: arm64: dts: qcom: shikra: Add gpio-reserved-ranges to tlmm
  • ❌ PENDING: EDAC/qcom: Skip ECC interrupt setup on Shikra, pre-configured by DSF

Expected format:

  • ✅ arm64: dts: qcom: shikra: Add gpio-reserved-ranges to tlmm (remove PENDING: prefix)
  • ✅ EDAC/qcom: Skip ECC interrupt setup on Shikra, pre-configured by DSF (remove PENDING: prefix)

Fix: Remove the PENDING: prefix from both commit subjects. The PENDING: tag is not a valid prefix for the qcom-6.18.y branch. Use the subsystem prefix directly:

  1. For commit 898daecba8ca:

    git rebase -i HEAD~2
# Mark the commit for reword
# Change subject to: arm64: dts: qcom: shikra: Add gpio-reserved-ranges to tlmm

  2. For commit e90b9a923c33:

    # In the same rebase session
# Change subject to: EDAC/qcom: Skip ECC interrupt setup on Shikra, pre-configured by DSF

Reproduce locally:

cd /path/to/kernel
git log --oneline -3 HEAD
# Run the compliance checker
bash kernel-checkers/check-patch-compliance.sh --kernel-src . --base HEAD~3 --head HEAD

Verdict

1 blocker to fix: Remove PENDING: prefix from 2 commits. All other checkers passed successfully. Once the commit subjects are corrected, the PR will be ready to merge.

@qlijarvis

qlijarvis commented Jun 18, 2026

Copy link
Copy Markdown

PR #740 — validate-patch

PR: #740

Verdict Issues Detailed Report
⚠️ 3 Full report

Final Summary

Commit 1/3 (FROMLIST):

  1. Lore link present: Yes — https://lore.kernel.org/all/20260531-shikra_llcc_conf-v1-1-fa405f5a2404@oss.qualcomm.com/
  2. Lore link matches PR commits: Cannot verify — link dated May 31, 2026 is inaccessible (future date)
  3. Upstream patch status: In review — FROMLIST prefix indicates posted to mailing list but not yet merged
  4. PR present in qcom-next: Not checked — cannot verify without kernel tree access

Commit 2/3 (PENDING):

  1. Lore link present: No — PENDING prefix; patch not yet posted upstream
  2. Lore link matches PR commits: N/A — no lore link to compare against
  3. Upstream patch status: Not upstream — PENDING indicates work-in-progress, not yet submitted
  4. PR present in qcom-next: Not checked — PENDING commits typically not in qcom-next until posted

Commit 3/3 (PENDING):

  1. Lore link present: No — PENDING prefix; patch not yet posted upstream
  2. Lore link matches PR commits: N/A — no lore link to compare against
  3. Upstream patch status: Not upstream — PENDING indicates work-in-progress, not yet submitted
  4. PR present in qcom-next: Not checked — PENDING commits typically not in qcom-next until posted
Verdict: ⚠️ — click to expand

🔍 Patch Validation

PR: #740 - Shikra LLCC configuration and device tree updates
Upstream commit: Multiple commits (see per-commit analysis below)
Verdict: ⚠️ PARTIAL

Commit 1/3: FROMLIST: soc: qcom: llcc: Add configuration data for Shikra SoC

Upstream link: https://lore.kernel.org/all/20260531-shikra_llcc_conf-v1-1-fa405f5a2404@oss.qualcomm.com/
Status: FROMLIST (posted to mailing list, not yet merged)

Commit Message

Check Status Note
Subject matches upstream ⚠️ Cannot verify - lore link dated May 31, 2026 (future date, not accessible)
Body preserves rationale ✅ Clear, concise description of adding LLCC config for Shikra
Fixes tag present/correct N/A New feature, no Fixes tag needed
Authorship preserved ✅ Original author Komal Bajaj preserved, co-signed by Anurag Pateriya
Backport note (if applicable) N/A FROMLIST prefix indicates upstream submission in progress

Diff

File Status Notes
drivers/soc/qcom/llcc-qcom.c ✅ Adds shikra_data, shikra_cfg, shikra_cfgs, and of_device_id entry; follows existing pattern

Issues

  • Lore link points to future date (May 31, 2026) which is inaccessible for verification
  • Cannot confirm if PR diff matches upstream submission exactly
  • FROMLIST prefix is appropriate for patches posted but not yet merged

Verdict for Commit 1

Structurally correct but unverifiable due to future-dated lore link.

Commit 2/3: PENDING: arm64: dts: qcom: shikra: Add gpio-reserved-ranges to tlmm

Upstream link: None provided
Status: PENDING (not yet posted upstream)

Commit Message

Check Status Note
Subject matches upstream N/A PENDING - not posted upstream yet
Body preserves rationale ✅ Clear explanation of why gpio-reserved-ranges is needed
Fixes tag present/correct N/A New feature addition
Authorship preserved ✅ Authored by Anurag Pateriya
Backport note (if applicable) N/A PENDING prefix indicates work-in-progress

Diff

File Status Notes
arch/arm64/boot/dts/qcom/shikra-cqm-evk.dts ✅ Adds gpio-reserved-ranges property
arch/arm64/boot/dts/qcom/shikra-cqs-evk.dts ✅ Adds gpio-reserved-ranges property
arch/arm64/boot/dts/qcom/shikra-iqs-evk.dts ✅ Adds gpio-reserved-ranges property

Issues

  • No lore link provided (expected for PENDING commits)
  • Identical gpio-reserved-ranges across all three EVK variants - should be verified this is correct for all board variants
  • PENDING prefix is appropriate for patches not yet submitted upstream

Verdict for Commit 2

Acceptable for internal integration; should be posted upstream when ready.

Commit 3/3: PENDING: soc: qcom: llcc: Skip ECC interrupt setup on Shikra, pre-configured by DSF

Upstream link: None provided
Status: PENDING (not yet posted upstream)

Commit Message

Check Status Note
Subject matches upstream N/A PENDING - not posted upstream yet
Body preserves rationale ✅ Excellent explanation of DSF pre-configuration and why driver should skip setup
Fixes tag present/correct N/A New platform-specific configuration
Authorship preserved ✅ Original author Faiyaz Mohammed preserved, co-signed by Anurag Pateriya
Backport note (if applicable) N/A PENDING prefix indicates work-in-progress

Diff

File Status Notes
drivers/soc/qcom/llcc-qcom.c ✅ Adds irq_configured flag to shikra_cfg; minimal, targeted change

Issues

  • No lore link provided (expected for PENDING commits)
  • Depends on commit 1/3 (shikra_cfg structure must exist first)
  • PENDING prefix is appropriate for patches not yet submitted upstream
  • Commit message uses em dash (—) which may cause issues in some email clients; consider using standard dash (-)

Verdict for Commit 3

Well-documented platform-specific quirk; acceptable for internal integration.

Overall Assessment

Issues Summary

  1. Commit 1/3: Lore link is future-dated (May 31, 2026) and inaccessible - cannot verify upstream submission matches PR diff
  2. Commit 2/3: No concerns beyond standard PENDING status
  3. Commit 3/3: Minor: em dash in subject line may cause email rendering issues

Verdict

⚠️ PARTIAL PASS - Commits are structurally sound and follow kernel conventions, but commit 1/3 cannot be verified against upstream due to inaccessible lore link.

Recommendation:

  • For commit 1/3: Verify the lore link is correct and accessible, or wait until the upstream patch is actually posted
  • For commits 2/3 and 3/3: Acceptable for internal integration with PENDING prefix; should be posted upstream when ready
  • Consider replacing em dash (—) with standard dash (-) in commit 3/3 subject for better email compatibility

Final Summary

Commit 1/3 (FROMLIST):

  1. Lore link present: Yes — https://lore.kernel.org/all/20260531-shikra_llcc_conf-v1-1-fa405f5a2404@oss.qualcomm.com/
  2. Lore link matches PR commits: Cannot verify — link dated May 31, 2026 is inaccessible (future date)
  3. Upstream patch status: In review — FROMLIST prefix indicates posted to mailing list but not yet merged
  4. PR present in qcom-next: Not checked — cannot verify without kernel tree access

Commit 2/3 (PENDING):

  1. Lore link present: No — PENDING prefix; patch not yet posted upstream
  2. Lore link matches PR commits: N/A — no lore link to compare against
  3. Upstream patch status: Not upstream — PENDING indicates work-in-progress, not yet submitted
  4. PR present in qcom-next: Not checked — PENDING commits typically not in qcom-next until posted

Commit 3/3 (PENDING):

  1. Lore link present: No — PENDING prefix; patch not yet posted upstream
  2. Lore link matches PR commits: N/A — no lore link to compare against
  3. Upstream patch status: Not upstream — PENDING indicates work-in-progress, not yet submitted
  4. PR present in qcom-next: Not checked — PENDING commits typically not in qcom-next until posted

@qlijarvis

qlijarvis commented Jun 18, 2026

Copy link
Copy Markdown

PR #740 — checker-log-analyzer

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

Checker Result Summary
Checker Result Summary
checkpatch ✅ All 3 commits passed with no errors or warnings
dt-binding-check ⏭️ Skipped - no changes in Documentation/devicetree/bindings
dtb-check ✅ All Shikra DTBs validated successfully
sparse-check ✅ Passed - no new sparse warnings introduced
check-uapi-headers ✅ Passed - no UAPI header changes
check-patch-compliance ❌ FAILED - 2 commits missing required subject prefix
tag-check N/A Not applicable for this branch
qcom-next-check ⚠️ 1 FROMLIST commit, 2 PENDING commits (expected for non-qcom-next branches)

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #740 - LLCC and DTS updates for Shikra SoC
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/27768561451

Checker Result Summary
checkpatch ✅ All 3 commits passed with no errors or warnings
dt-binding-check ⏭️ Skipped - no changes in Documentation/devicetree/bindings
dtb-check ✅ All Shikra DTBs validated successfully
sparse-check ✅ Passed - no new sparse warnings introduced
check-uapi-headers ✅ Passed - no UAPI header changes
check-patch-compliance ❌ FAILED - 2 commits missing required subject prefix
tag-check N/A Not applicable for this branch
qcom-next-check ⚠️ 1 FROMLIST commit, 2 PENDING commits (expected for non-qcom-next branches)

❌ check-patch-compliance

Root cause: Two commits with PENDING: prefix do not include the required subsystem prefix after the tag.

Failure details:

Checking commit: PENDING: arm64: dts: qcom: shikra: Add gpio-reserved-ranges to tlmm
Commit summary does not start with a required prefix

Checking commit: PENDING: soc: qcom: llcc: Skip ECC interrupt setup on Shikra, pre-configured by DSF
Commit summary does not start with a required prefix

Fix: The check-patch-compliance checker expects commit subjects to follow the pattern:

TAG: subsystem: description

For the two failing commits, the subsystem prefix appears after the PENDING: tag, but the checker expects it to be part of a recognized pattern. The commits should be reformatted as:

Commit 2 (bf2f6aa):

  • Current: PENDING: arm64: dts: qcom: shikra: Add gpio-reserved-ranges to tlmm
  • Expected: arm64: dts: qcom: shikra: Add gpio-reserved-ranges to tlmm (remove PENDING prefix)
  • Or if PENDING must be kept, ensure it follows the subsystem convention used in the tree

Commit 3 (f82cd8e):

  • Current: PENDING: soc: qcom: llcc: Skip ECC interrupt setup on Shikra, pre-configured by DSF
  • Expected: soc: qcom: llcc: Skip ECC interrupt setup on Shikra, pre-configured by DSF (remove PENDING prefix)
  • Or if PENDING must be kept, ensure it follows the subsystem convention used in the tree

The FROMLIST: prefix in commit 1 is accepted because it's a recognized upstream tag pattern.

Reproduce locally:

cd /path/to/kernel
git fetch origin pull/740/head:pr-740
git checkout pr-740
bash kernel-checkers/check-patch-compliance.sh --kernel-src . \
  --base 9f78b3e53ed930b4720f4691f2433d355ce1a777 \
  --head f82cd8e88cfeea167d0ea52815fd284af76e44a7

Verdict

1 blocker to fix: The check-patch-compliance failure must be resolved before merge. Either remove the PENDING: prefix from commits 2 and 3, or update the commit message format to match the expected pattern for the target branch. All other checkers passed successfully.

Komal-Bajaj and others added 3 commits June 19, 2026 10:12
@Komal-Bajaj @apateriy-qcom
FROMLIST: soc: qcom: llcc: Add configuration data for Shikra SoC
df503ac 
Add Last Level Cache table and configs for the Shikra SoC.

Link: https://lore.kernel.org/all/20260531-shikra_llcc_conf-v1-1-fa405f5a2404@oss.qualcomm.com/

Signed-off-by: Komal Bajaj <komal.bajaj@oss.qualcomm.com>
Signed-off-by: Anurag Pateriya <apateriy@qti.qualcomm.com>
@apateriy-qcom
PENDING: arm64: dts: qcom: shikra: Add gpio-reserved-ranges to tlmm
234030f 
Add gpio-reserved-ranges property to the tlmm node for all three
Shikra EVK variants (CQM, CQS, IQS) to mark GPIOs used by the
SoC internally and not available for general use.

Signed-off-by: Anurag Pateriya <apateriy@qti.qualcomm.com>
@faiyaz-mohammed @apateriy-qcom
PENDING: soc: qcom: llcc: Skip ECC interrupt setup on Shikra, pre-con…
116d8ce 
…figured by DSF

On Shikra, the DDR System Firmware (DSF) configures ECC interrupt
routing before the kernel driver probes — it enables Tag/Data RAM
interrupts and programs error thresholds in the LLCC interrupt-enable
registers.

Set irq_configured in shikra_cfg so that qcom_llcc_edac_probe() skips
calling qcom_llcc_core_setup(), which would otherwise overwrite the
firmware-managed register state with redundant writes.

Signed-off-by: Faiyaz Mohammed <faiyazm@qti.qualcomm.com>
Signed-off-by: Anurag Pateriya <apateriy@qti.qualcomm.com>
@qcomlnxci

qcomlnxci commented Jun 19, 2026

Copy link
Copy Markdown

Test jobs on 116d8ce

@qcomlnxci

qcomlnxci commented Jun 19, 2026

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 ❌ Fail ✅ 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 f03e957 into qualcomm-linux:qcom-6.18.y Jun 19, 2026
6 of 8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@shashim-quic shashim-quic shashim-quic approved these changes

@quicAspratap quicAspratap quicAspratap approved these changes

@ndechesne ndechesne Awaiting requested review from ndechesne ndechesne was automatically assigned from qualcomm-linux/qualcomm-kernel-maint

@sgaud-quic sgaud-quic Awaiting requested review from sgaud-quic sgaud-quic was automatically assigned from qualcomm-linux/qualcomm-kernel-maint

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

qli-2.0 GA pull-request freeze

Development

Successfully merging this pull request may close these issues.

8 participants

@apateriy-qcom @qlijarvis @qcomlnxci @shashim-quic @quicAspratap @sgaud-quic @Komal-Bajaj @faiyaz-mohammed