Skip to content

shikra: Add support for GPU and Adreno_SMMU DT#696

Merged
sgaud-quic merged 3 commits into
qualcomm-linux:qcom-6.18.yfrom
asherawa:dt-shikra-smmu-separate
Jun 18, 2026
Merged

shikra: Add support for GPU and Adreno_SMMU DT#696
sgaud-quic merged 3 commits into
qualcomm-linux:qcom-6.18.yfrom
asherawa:dt-shikra-smmu-separate

Conversation

@asherawa

@asherawa asherawa commented Jun 11, 2026

Copy link
Copy Markdown

Add Shikra device tree support for the Adreno A704 GPU by adding the GPU, GMU wrapper, and Adreno SMMU nodes with required resources such as clocks, interconnects, IOMMU, OPP table, and zap-shader region.

Enable GPU support on CQM-EVK, CQS-EVK, and IQS-EVK boards, and add GPU thermal cooling to throttle GPU frequency at 115°C for thermal protection.

CRs-Fixed: 4569898

qli-2.0 GA Critical Fix
exception - https://jira-dc.qualcomm.com/jira/browse/QLIJIRA-130

@asherawa asherawa requested review from a team, knaveen-qc, quicAspratap and trsoni June 11, 2026 05:07
@quic-ksanadhy

Copy link
Copy Markdown

shikra: Enable GPU (adreno smmu node + thermal + dt support) -> This title doesn't look good.
Make it something like Add support for GPU and Adreno_SMMU DT.

@asherawa asherawa changed the title shikra: Enable GPU (adreno smmu node + thermal + dt support) shikra: Add support for GPU and Adreno_SMMU DT. Jun 11, 2026
@asherawa asherawa force-pushed the dt-shikra-smmu-separate branch from 51cdaa6 to c8e2667 Compare June 11, 2026 11:04
@qlijarvis

Copy link
Copy Markdown

PR #696 — validate-patch

PR: #696

Verdict Issues Detailed Report
⚠️ 3 Full report

Final Summary

  1. Lore link present: No — None of the three commits contain Link: tags to lore.kernel.org
  2. Lore link matches PR commits: N/A — No lore links to compare against
  3. Upstream patch status: Unknown — No upstream submission found via lore.kernel.org search for authors/subjects; likely vendor-only or not yet posted
  4. PR present in qcom-next: Not checked — Would require access to qcom-next branch
Verdict: ⚠️ — click to expand

🔍 Patch Validation

PR: #696 - Add Shikra GPU support (3 commits)
Upstream commit: N/A (not found on lore.kernel.org)
Verdict: ⚠️ PARTIAL


Commit 1/3: arm64: dts: qcom: shikra: Add A704 GPU support

Commit Message

Check Status Note
Subject matches upstream N/A No upstream reference found
Body preserves rationale Clear description of what is added
Fixes tag present/correct N/A Not a fix
Authorship preserved ⚠️ Uses @qti.qualcomm.com (internal) instead of @oss.qualcomm.com
Backport note (if applicable) N/A Not a backport

Diff

File Status Notes
arch/arm64/boot/dts/qcom/shikra-cqm-evk.dts Enables GPU and sets zap-shader firmware
arch/arm64/boot/dts/qcom/shikra-cqs-evk.dts Enables GPU and sets zap-shader firmware
arch/arm64/boot/dts/qcom/shikra-iqs-evk.dts Enables GPU and sets zap-shader firmware
arch/arm64/boot/dts/qcom/shikra.dtsi Adds GPU and GMU wrapper nodes with proper bindings

Issues

  • Author email uses internal domain (@qti.qualcomm.com) instead of upstream-friendly @oss.qualcomm.com
  • No Link: tag to upstream submission
  • Missing Signed-off-by chain if this was co-developed

Commit 2/3: arm64: dts: qcom: shikra: Add GPU cooling

Commit Message

Check Status Note
Subject matches upstream N/A No upstream reference found
Body preserves rationale Clear explanation of why GPU cooling is needed
Fixes tag present/correct N/A Not a fix
Authorship preserved Uses @oss.qualcomm.com
Backport note (if applicable) N/A Not a backport

Diff

File Status Notes
arch/arm64/boot/dts/qcom/shikra.dtsi Adds thermal throttling at 115°C with proper cooling-maps

Issues

  • No Link: tag to upstream submission
  • Depends on commit 1/3 (GPU node must exist first)

Commit 3/3: arm64: dts: qcom: shikra: Add Adreno SMMU node

Commit Message

Check Status Note
Subject matches upstream N/A No upstream reference found
Body preserves rationale ⚠️ Very brief; could explain SMMU purpose
Fixes tag present/correct N/A Not a fix
Authorship preserved Uses @oss.qualcomm.com; proper co-author chain
Backport note (if applicable) N/A Not a backport

Diff

File Status Notes
arch/arm64/boot/dts/qcom/shikra.dtsi Adds adreno_smmu node with proper compatible strings and clocks

Issues

  • No Link: tag to upstream submission
  • Commit message is minimal (one sentence body)
  • Multiple Signed-off-by tags suggest co-development but no explanation in commit message

Overall Issues

  1. Missing Link: tags - None of the three commits contain Link: tags pointing to lore.kernel.org or any upstream submission
  2. Inconsistent email domains - Commit 1/3 uses @qti.qualcomm.com (internal) while 2/3 and 3/3 use @oss.qualcomm.com (upstream-friendly)
  3. No upstream traceability - Cannot verify if these patches were posted upstream or if they match any upstream submission
  4. Commit ordering concern - Commit 3/3 adds the SMMU node that commit 1/3 references (iommus = <&adreno_smmu 0 1>), but commit 3/3 comes after commit 1/3, which could cause bisection issues

Verdict

⚠️ PARTIAL PASS - Patches are technically correct and follow DT binding conventions, but lack upstream traceability and have authorship inconsistencies. The commit ordering may cause bisection issues (SMMU node added after GPU node that references it).

Recommended actions:

  1. Reorder commits: SMMU node (3/3) should come before GPU node (1/3)
  2. Add Link: tags if these were posted upstream
  3. Use consistent email domain (@oss.qualcomm.com) for all authors
  4. Expand commit message for 3/3 to explain SMMU purpose

Final Summary

  1. Lore link present: No — None of the three commits contain Link: tags to lore.kernel.org
  2. Lore link matches PR commits: N/A — No lore links to compare against
  3. Upstream patch status: Unknown — No upstream submission found via lore.kernel.org search for authors/subjects; likely vendor-only or not yet posted
  4. PR present in qcom-next: Not checked — Would require access to qcom-next branch

@qlijarvis

Copy link
Copy Markdown

PR #696 — checker-log-analyzer

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

Checker Result Summary
Checker Result Summary
checkpatch ⚠️ 1 warning: undocumented DT compatible string
dt-binding-check ⏭️ Skipped (no binding changes)
dtb-check GPU interrupt property has wrong cell count
sparse-check ⏭️ Skipped (no C code changes)
check-uapi-headers ⏭️ Skipped (no UAPI changes)
check-patch-compliance All 3 commits missing required subject prefix
tag-check N/A Not applicable for this branch
qcom-next-check N/A Not applicable for this branch

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #696 - arm64: dts: qcom: shikra: Add A704 GPU support (3 commits)
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/27343479315

Checker Result Summary
checkpatch ⚠️ 1 warning: undocumented DT compatible string
dt-binding-check ⏭️ Skipped (no binding changes)
dtb-check GPU interrupt property has wrong cell count
sparse-check ⏭️ Skipped (no C code changes)
check-uapi-headers ⏭️ Skipped (no UAPI changes)
check-patch-compliance All 3 commits missing required subject prefix
tag-check N/A Not applicable for this branch
qcom-next-check N/A Not applicable for this branch

❌ dtb-check

Root cause: GPU node interrupt property uses 3 cells per interrupt instead of required 4 cells

Failure details:

../arch/arm64/boot/dts/qcom/shikra.dtsi:2532.4-27: Warning (interrupts_property): 
/soc@0/gpu@5900000:#interrupt-cells: size is (12), expected multiple of 16

The GPU node at arch/arm64/boot/dts/qcom/shikra.dtsi line ~2236 defines:

interrupts = <GIC_SPI 177 IRQ_TYPE_LEVEL_HIGH>;

This uses only 3 cells (GIC_SPI, IRQ number, trigger type), but the GIC interrupt controller on this platform requires 4 cells per interrupt. The 4th cell is typically used for interrupt affinity/routing and should be set to 0 for default routing.

Fix: Add the 4th cell (set to 0) to the GPU interrupt property:

-			interrupts = <GIC_SPI 177 IRQ_TYPE_LEVEL_HIGH>;
+			interrupts = <GIC_SPI 177 IRQ_TYPE_LEVEL_HIGH 0>;

Reproduce locally:

make ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- dtbs_check DT_SCHEMA_FILES=Documentation/devicetree/bindings/
# Or just build the specific DTB:
make ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- arch/arm64/boot/dts/qcom/shikra-cqm-evk.dtb

❌ check-patch-compliance

Root cause: All 3 commits lack required subject prefix (UPSTREAM:/FROMLIST:/BACKPORT:/etc.)

Failure details:

Checking commit: arm64: dts: qcom: shikra: Add A704 GPU support
Commit summary does not start with a required prefix

Checking commit: arm64: dts: qcom: shikra: Add GPU cooling
Commit summary does not start with a required prefix

Checking commit: arm64: dts: qcom: shikra: Add Adreno SMMU node
Commit summary does not start with a required prefix

The Qualcomm Linux kernel requires commit subjects to be prefixed with tags indicating their origin:

  • UPSTREAM: - Already merged in mainline
  • FROMLIST: - Posted to upstream mailing list, pending acceptance
  • BACKPORT: - Backported from a newer kernel version
  • FROMGIT: - Cherry-picked from an upstream maintainer tree

Fix: Reword all 3 commit subjects to include the appropriate prefix. Since these appear to be new downstream patches for Shikra (not yet upstream), use FROMLIST: if they will be/have been posted upstream, or discuss with maintainers if a different tag is appropriate.

Example:

FROMLIST: arm64: dts: qcom: shikra: Add A704 GPU support
FROMLIST: arm64: dts: qcom: shikra: Add GPU cooling
FROMLIST: arm64: dts: qcom: shikra: Add Adreno SMMU node

Reproduce locally:

cd /path/to/kernel
git clone https://github.com/qualcomm-linux/kernel-checkers.git
bash kernel-checkers/check-patch-compliance.sh --kernel-src . --base <base-sha> --head <head-sha>

⚠️ checkpatch (non-blocking warning)

Root cause: DT compatible string "qcom,adreno-07000400" is not documented in bindings

Failure details:

WARNING: DT compatible string "qcom,adreno-07000400" appears un-documented 
-- check ./Documentation/devicetree/bindings/
#85: FILE: arch/arm64/boot/dts/qcom/shikra.dtsi:2236:
+			compatible = "qcom,adreno-07000400", "qcom,adreno";

Fix: This is typically a non-blocking warning if:

  1. The binding documentation exists but checkpatch didn't find it (false positive), OR
  2. The binding will be added in a separate patch/series

Verify that Documentation/devicetree/bindings/gpu/qcom,adreno.yaml (or similar) documents this compatible string. If not, add it to the binding documentation before or alongside this DTS change.

Reproduce locally:

./scripts/checkpatch.pl --strict --git <base-sha>..<head-sha>

Verdict

2 blockers must be fixed before merge:

  1. dtb-check failure: Add 4th cell (0) to GPU interrupt property
  2. check-patch-compliance failure: Add required subject prefix to all 3 commits (e.g., FROMLIST:)

The checkpatch warning about undocumented compatible string should be verified but is typically non-blocking if the binding exists or will be added separately.

@asherawa asherawa force-pushed the dt-shikra-smmu-separate branch from c8e2667 to e7ce4c2 Compare June 11, 2026 13:30
@qswat-orbit-external

Copy link
Copy Markdown

Merge Check Failed: No CR Numbers Found

Error: No Change Request numbers were found.

Please add Change Request numbers to your pull request description in the format CRs-Fixed: 12345 or link GitHub issues that are associated with Change Requests.

@shashim-quic shashim-quic left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

arm64: dts: qcom: shikra: Add A704 GPU support

add appropriate tag and Link: tag. Downstream patches need exception approval.

@qswat-orbit-external

Copy link
Copy Markdown

Merge Check Failed: CR Not Eligible for Merge

CR 4569898 is not eligible for merge.

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

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

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

@asherawa asherawa changed the title shikra: Add support for GPU and Adreno_SMMU DT. shikra: Add support for GPU and Adreno_SMMU DT Jun 12, 2026
@qswat-orbit-external

Copy link
Copy Markdown

Merge Check Failed: CR Not Eligible for Merge

CR 4569898 is not eligible for merge.

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

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

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

@asherawa asherawa force-pushed the dt-shikra-smmu-separate branch from e7ce4c2 to 369b3ad Compare June 12, 2026 19:15
@qswat-orbit-external

Copy link
Copy Markdown

Merge Check Failed: CR Not Eligible for Merge

CR 4569898 is not eligible for merge.

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

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

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

@qcomlnxci qcomlnxci requested a review from a team June 12, 2026 19:16
@qlijarvis

Copy link
Copy Markdown

PR #696 — validate-patch

PR: #696

Verdict Issues Detailed Report
⚠️ 2 Full report

Final Summary

  1. Lore link present: No — PENDING: prefix indicates patches not yet posted upstream; no lore link expected or required at this stage

  2. Lore link matches PR commits: N/A — no lore link to compare against; these are pre-submission PENDING patches

  3. Upstream patch status: Not upstream — all three patches carry PENDING: prefix indicating work-in-progress not yet submitted to mailing lists

  4. PR present in qcom-next: Not checked — PENDING patches are typically staged in topic branches before qcom-next integration

Recommendation: Fix the patch ordering issue (adreno_smmu definition before use) before merging. Once reordered, the series is suitable for internal integration and subsequent upstream submission.

Verdict: ⚠️ — click to expand

🔍 Patch Validation

PR: #696 - Add Shikra GPU support (3 patches)
Upstream commit: N/A (PENDING patches)
Verdict: ⚠️ PARTIAL

Patch 1/3: PENDING: arm64: dts: qcom: shikra: Add A704 GPU support

Commit Message

Check Status Note
Subject matches upstream N/A PENDING prefix - not yet upstream
Body preserves rationale Clear description of GPU/GMU nodes and board enablement
Fixes tag present/correct N/A New feature, no Fixes tag needed
Authorship preserved Aditya Sherawat asherawa@qti.qualcomm.com
Backport note (if applicable) N/A PENDING patch, not a backport

Diff

File Status Notes
arch/arm64/boot/dts/qcom/shikra-cqm-evk.dts:28 Enables GPU and sets zap-shader firmware
arch/arm64/boot/dts/qcom/shikra-cqs-evk.dts:29 Enables GPU and sets zap-shader firmware
arch/arm64/boot/dts/qcom/shikra-iqs-evk.dts:40 Enables GPU and sets zap-shader firmware
arch/arm64/boot/dts/qcom/shikra.dtsi:2282 Adds complete GPU node with OPP table and GMU wrapper

Issues

  • No Link: tag to upstream submission (expected for PENDING patches)
  • Missing Reviewed-by/Acked-by tags from maintainers

Patch 2/3: PENDING: arm64: dts: qcom: shikra: Add GPU cooling

Commit Message

Check Status Note
Subject matches upstream N/A PENDING prefix - not yet upstream
Body preserves rationale Explains GPU thermal throttling at 115°C
Fixes tag present/correct N/A New feature, no Fixes tag needed
Authorship preserved Aastha Pandey aastha.pandey@oss.qualcomm.com
Backport note (if applicable) N/A PENDING patch, not a backport

Diff

File Status Notes
arch/arm64/boot/dts/qcom/shikra.dtsi:2843 Adds GPU thermal zone with passive cooling

Issues

  • No Link: tag to upstream submission (expected for PENDING patches)
  • Missing Reviewed-by/Acked-by tags from maintainers

Patch 3/3: PENDING: arm64: dts: qcom: shikra: Add Adreno SMMU node

Commit Message

Check Status Note
Subject matches upstream N/A PENDING prefix - not yet upstream
Body preserves rationale ⚠️ Very brief - could explain SMMU purpose/configuration
Fixes tag present/correct N/A New feature, no Fixes tag needed
Authorship preserved Komal Bajaj (author) + 2 co-authors with Signed-off-by
Backport note (if applicable) N/A PENDING patch, not a backport

Diff

File Status Notes
arch/arm64/boot/dts/qcom/shikra.dtsi:2393 Adds Adreno SMMU with clocks and power domains

Issues

  • Commit message is minimal - could benefit from more context about SMMU configuration
  • No Link: tag to upstream submission (expected for PENDING patches)
  • Missing Reviewed-by/Acked-by tags from maintainers

Overall Series Issues

Commit Message Quality:

  • All three patches use PENDING: prefix correctly to indicate work-in-progress
  • Patch 3/3 has minimal commit body (one sentence) - could be more descriptive
  • No Link: tags pointing to lore.kernel.org (expected for PENDING patches)
  • No upstream review tags (Reviewed-by, Acked-by, Tested-by)

Authorship & Tags:

  • All patches have proper Signed-off-by tags
  • Patch 3/3 correctly preserves co-author chain (Bibek → Imran → Komal)
  • Email domains mix @qti.qualcomm.com and @oss.qualcomm.com (acceptable)

Technical Content:

  • Patches form a logical series: GPU node → cooling → SMMU
  • DTS syntax appears correct (compatible strings, reg, clocks, etc.)
  • Patch 1 references &adreno_smmu before Patch 3 defines it (ordering issue)

Critical Ordering Issue:

  • Patch 1/3 uses iommus = <&adreno_smmu 0 1>; at line 2312
  • Patch 3/3 defines adreno_smmu: node
  • ❌ This creates a forward reference that will break bisectability
  • Fix: Patch 3 should come before Patch 1, or Patch 1 should not reference adreno_smmu until it's defined

Verdict

⚠️ PARTIAL PASS with ordering issue

The patches are technically sound but have a critical bisectability problem: Patch 1 references &adreno_smmu before Patch 3 defines it. This will cause DTC (device tree compiler) errors when building after Patch 1 alone.

Required fix: Reorder patches so adreno_smmu is defined before it's referenced, or remove the iommus property from Patch 1 and add it in a follow-up after Patch 3.

Minor improvements:

  • Expand Patch 3/3 commit message with more context
  • Add Link: tags when patches are posted upstream
  • Obtain maintainer review tags before merging

Final Summary

  1. Lore link present: No — PENDING: prefix indicates patches not yet posted upstream; no lore link expected or required at this stage

  2. Lore link matches PR commits: N/A — no lore link to compare against; these are pre-submission PENDING patches

  3. Upstream patch status: Not upstream — all three patches carry PENDING: prefix indicating work-in-progress not yet submitted to mailing lists

  4. PR present in qcom-next: Not checked — PENDING patches are typically staged in topic branches before qcom-next integration

Recommendation: Fix the patch ordering issue (adreno_smmu definition before use) before merging. Once reordered, the series is suitable for internal integration and subsequent upstream submission.

@qlijarvis

Copy link
Copy Markdown

PR #696 — checker-log-analyzer

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

Checker Result Summary
Checker Result Summary
checkpatch ⚠️ 1 warning: undocumented DT compatible string
dt-binding-check ⏭️ Skipped - no binding changes
dtb-check Passed
sparse-check ⏭️ Skipped - no C code changes
check-uapi-headers ⏭️ Skipped - no UAPI changes
check-patch-compliance BLOCKER: All 3 commits use "PENDING:" prefix
tag-check BLOCKER: Subject prefix required (FROMLIST:/UPSTREAM:/BACKPORT:)
qcom-next-check ⚠️ Applies only to qcom-next branches

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #696 - PENDING: arm64: dts: qcom: shikra: Add A704 GPU support (3 commits)
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/27437573961

Checker Result Summary
checkpatch ⚠️ 1 warning: undocumented DT compatible string
dt-binding-check ⏭️ Skipped - no binding changes
dtb-check Passed
sparse-check ⏭️ Skipped - no C code changes
check-uapi-headers ⏭️ Skipped - no UAPI changes
check-patch-compliance BLOCKER: All 3 commits use "PENDING:" prefix
tag-check BLOCKER: Subject prefix required (FROMLIST:/UPSTREAM:/BACKPORT:)
qcom-next-check ⚠️ Applies only to qcom-next branches

❌ check-patch-compliance

Root cause: All three commits use the "PENDING:" prefix which is not a valid upstream-compliant prefix.

Failure details:

Checking commit: PENDING: arm64: dts: qcom: shikra: Add A704 GPU support
Commit summary does not start with a required prefix

Checking commit: PENDING: arm64: dts: qcom: shikra: Add GPU cooling
Commit summary does not start with a required prefix

Checking commit: PENDING: arm64: dts: qcom: shikra: Add Adreno SMMU node
Commit summary does not start with a required prefix

Fix: Replace "PENDING:" with one of the required prefixes:

  • FROMLIST: if the patch has been posted to an upstream mailing list but not yet merged
  • UPSTREAM: if the patch exists in Linus's tree or a maintainer tree
  • BACKPORT: if backporting from a newer kernel version
  • DOWNSTREAM: for Qualcomm-specific changes (use sparingly)

For these GPU devicetree additions, if they haven't been posted upstream yet, you should:

  1. Post them to the linux-arm-msm mailing list first
  2. Then use FROMLIST: prefix with a link to the lore.kernel.org posting

Example fix for commit 1:

FROMLIST: arm64: dts: qcom: shikra: Add A704 GPU support

Reproduce locally:

bash ../kernel-checkers/check-patch-compliance.sh --kernel-src . \
  --base 6ec3dd75be7c4b70733693d6b04a3e94b966f30b --head 369b3ad76136f9206fd49a2e3da1bcda07129240

⚠️ checkpatch

Root cause: The compatible string "qcom,adreno-07000400" is not documented in devicetree bindings.

Failure details:

WARNING: DT compatible string "qcom,adreno-07000400" appears un-documented -- check ./Documentation/devicetree/bindings/
#85: FILE: arch/arm64/boot/dts/qcom/shikra.dtsi:2286:
+			compatible = "qcom,adreno-07000400", "qcom,adreno";

Fix: This is a warning, not a blocker. However, for upstream submission you should:

  1. Add the compatible string to Documentation/devicetree/bindings/display/msm/gpu.yaml (or the appropriate binding file)
  2. Submit the binding update as a separate patch before the DTS changes

Note: This warning can be ignored for internal/downstream branches if the binding documentation will be added later, but it's required for upstream submission.

Reproduce locally:

./scripts/checkpatch.pl --strict --summary-file --ignore FILE_PATH_CHANGES \
  --git 6ec3dd75be7c4b70733693d6b04a3e94b966f30b..369b3ad76136f9206fd49a2e3da1bcda07129240

Verdict

2 blockers must be fixed before merge:

  1. Critical: Remove "PENDING:" prefix from all 3 commits and replace with appropriate upstream-compliant prefix (FROMLIST:/UPSTREAM:/BACKPORT:/DOWNSTREAM:)
  2. Recommended: Document the "qcom,adreno-07000400" compatible string in devicetree bindings (required for upstream, optional for internal branches)

Action items:

  • Reword all commit subjects to use valid prefixes
  • Consider posting patches upstream first, then use FROMLIST: prefix
  • Add DT binding documentation for the new Adreno compatible string

@qswat-orbit-external

Copy link
Copy Markdown

Merge Check Failed: CR Not Eligible for Merge

CR 4569898 is not eligible for merge.

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

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

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

1 similar comment
@qswat-orbit-external

Copy link
Copy Markdown

Merge Check Failed: CR Not Eligible for Merge

CR 4569898 is not eligible for merge.

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

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

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

@asherawa asherawa force-pushed the dt-shikra-smmu-separate branch from 369b3ad to 3d1ad8c Compare June 15, 2026 07:34
@qswat-orbit-external

Copy link
Copy Markdown

Merge Check Failed: CR Not Eligible for Merge

CR 4569898 is not eligible for merge.

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

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

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

@qlijarvis

Copy link
Copy Markdown

PR #696 — validate-patch

PR: #696

Verdict Issues Detailed Report
⚠️ 1 Full report

Final Summary

Patch 1/3:

  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: prefix indicates awaiting upstream submission
  4. PR present in qcom-next: Not checked — PENDING: patches typically merged after upstream posting

Patch 2/3:

  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: prefix indicates awaiting upstream submission
  4. PR present in qcom-next: Not checked — PENDING: patches typically merged after upstream posting

Patch 3/3:

  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: prefix indicates awaiting upstream submission
  4. PR present in qcom-next: Not checked — PENDING: patches typically merged after upstream posting
Verdict: ⚠️ — click to expand

🔍 Patch Validation

PR: #696 - Add GPU support for Shikra SoC
Upstream commit: N/A (PENDING: prefix indicates not yet posted)
Verdict: ⚠️ PARTIAL


Patch 1/3: PENDING: arm64: dts: qcom: shikra: Add A704 GPU support

Upstream commit: N/A
Verdict: ⚠️ PARTIAL

Commit Message

Check Status Note
Subject matches upstream N/A Not yet upstream (PENDING: prefix)
Body preserves rationale Clear description of GPU/GMU nodes and board enablement
Fixes tag present/correct N/A New feature, no Fixes tag needed
Authorship preserved Aditya Sherawat asherawa@qti.qualcomm.com
Backport note (if applicable) N/A Not a backport

Diff

File Status Notes
arch/arm64/boot/dts/qcom/shikra-cqm-evk.dts:28 Enables GPU and zap-shader firmware
arch/arm64/boot/dts/qcom/shikra-cqs-evk.dts:29 Enables GPU and zap-shader firmware
arch/arm64/boot/dts/qcom/shikra-iqs-evk.dts:40 Enables GPU and zap-shader firmware
arch/arm64/boot/dts/qcom/shikra.dtsi:2282 Adds A704 GPU node with OPP table and GMU wrapper

Issues

  • PENDING: prefix indicates patch is not yet posted upstream; should be posted to devicetree/linux-arm-msm mailing lists before merging to product tree

Patch 2/3: PENDING: arm64: dts: qcom: shikra: Add GPU cooling

Upstream commit: N/A
Verdict: ⚠️ PARTIAL

Commit Message

Check Status Note
Subject matches upstream N/A Not yet upstream (PENDING: prefix)
Body preserves rationale Explains GPU thermal throttling at 115°C
Fixes tag present/correct N/A New feature, no Fixes tag needed
Authorship preserved Aastha Pandey aastha.pandey@oss.qualcomm.com
Backport note (if applicable) N/A Not a backport

Diff

File Status Notes
arch/arm64/boot/dts/qcom/shikra.dtsi:2843 Adds GPU thermal throttling trip point and cooling map

Issues

  • PENDING: prefix indicates patch is not yet posted upstream; should be posted to devicetree/linux-arm-msm mailing lists before merging to product tree

Patch 3/3: PENDING: arm64: dts: qcom: shikra: Add Adreno SMMU node

Upstream commit: N/A
Verdict: ⚠️ PARTIAL

Commit Message

Check Status Note
Subject matches upstream N/A Not yet upstream (PENDING: prefix)
Body preserves rationale Clear description of Adreno SMMU node addition
Fixes tag present/correct N/A New feature, no Fixes tag needed
Authorship preserved Multiple authors with proper Signed-off-by chain
Backport note (if applicable) N/A Not a backport

Diff

File Status Notes
arch/arm64/boot/dts/qcom/shikra.dtsi:2393 Adds Adreno SMMU IOMMU node with clocks and power domain

Issues

  • PENDING: prefix indicates patch is not yet posted upstream; should be posted to devicetree/linux-arm-msm mailing lists before merging to product tree
  • Multiple Signed-off-by tags (Bibek Kumar Patro, Imran Shaik, Komal Bajaj) suggest collaborative development; ensure all contributors are properly credited

Overall Verdict

All three patches are well-formed with clear commit messages and proper authorship. However, the PENDING: prefix indicates these patches have not yet been posted upstream. For Qualcomm Linux kernel integration:

Recommendation: These patches should be posted to upstream mailing lists (devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org) for review before merging to the product tree. Once posted, the PENDING: prefix should be replaced with FROMLIST: and the lore link added to the commit message.


Final Summary

Patch 1/3:

  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: prefix indicates awaiting upstream submission
  4. PR present in qcom-next: Not checked — PENDING: patches typically merged after upstream posting

Patch 2/3:

  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: prefix indicates awaiting upstream submission
  4. PR present in qcom-next: Not checked — PENDING: patches typically merged after upstream posting

Patch 3/3:

  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: prefix indicates awaiting upstream submission
  4. PR present in qcom-next: Not checked — PENDING: patches typically merged after upstream posting

@qlijarvis

Copy link
Copy Markdown

PR #696 — checker-log-analyzer

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

Checker Result Summary
Checker Result Summary
checkpatch Undocumented DT compatible string "qcom,adreno-07000400"
dt-binding-check ⏭️ Skipped - no binding changes
dtb-check Passed
sparse-check ⏭️ Skipped - no C code changes
check-uapi-headers ⏭️ Skipped - no UAPI changes
check-patch-compliance All 3 commits use "PENDING:" prefix (not UPSTREAM:/FROMLIST:)
tag-check N/A Not applicable for this branch
qcom-next-check ⚠️ PENDING: prefix used - requires FROMLIST:/UPSTREAM: for qcom-next

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #696 - PENDING: arm64: dts: qcom: shikra: Add A704 GPU support
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/27531208575

Checker Result Summary
checkpatch Undocumented DT compatible string "qcom,adreno-07000400"
dt-binding-check ⏭️ Skipped - no binding changes
dtb-check Passed
sparse-check ⏭️ Skipped - no C code changes
check-uapi-headers ⏭️ Skipped - no UAPI changes
check-patch-compliance All 3 commits use "PENDING:" prefix (not UPSTREAM:/FROMLIST:)
tag-check N/A Not applicable for this branch
qcom-next-check ⚠️ PENDING: prefix used - requires FROMLIST:/UPSTREAM: for qcom-next

❌ checkpatch

Root cause: The compatible string "qcom,adreno-07000400" is used in the GPU node but has no corresponding devicetree binding documentation.

Failure details:

WARNING: DT compatible string "qcom,adreno-07000400" appears un-documented -- check ./Documentation/devicetree/bindings/
#85: FILE: arch/arm64/boot/dts/qcom/shikra.dtsi:2286:
+			compatible = "qcom,adreno-07000400", "qcom,adreno";

b59415b6b72db58a44b910415f12e8366d919a8f total: 0 errors, 1 warnings, 0 checks, 146 lines checked

Fix: Add devicetree binding documentation for the A704 GPU before using this compatible string, or use an existing documented compatible string if this GPU is compatible with an already-documented variant.

Reproduce locally:

./scripts/checkpatch.pl --strict --summary-file --ignore FILE_PATH_CHANGES --git 9740e45b352ca1e5d7f40f5754b977d3533dc8b4..3d1ad8c8d2d01f7c41e1f90a5e40d1a9e849cbb4

❌ check-patch-compliance

Root cause: All three commits use the PENDING: subject prefix, which is not a valid upstream compliance prefix.

Failure details:

Checking commit: PENDING: arm64: dts: qcom: shikra: Add A704 GPU support
Commit summary does not start with a required prefix

Checking commit: PENDING: arm64: dts: qcom: shikra: Add GPU cooling
Commit summary does not start with a required prefix

Checking commit: PENDING: arm64: dts: qcom: shikra: Add Adreno SMMU node
Commit summary does not start with a required prefix

Fix: Replace the PENDING: prefix with one of the following valid prefixes:

  • UPSTREAM: - if the patch has been accepted and merged into mainline Linux
  • FROMLIST: - if the patch has been posted to a mailing list but not yet merged
  • BACKPORT: - if backporting from a newer kernel version
  • Remove the prefix entirely if this is original work for the Qualcomm tree

For example:

FROMLIST: arm64: dts: qcom: shikra: Add A704 GPU support

Reproduce locally:

# Check commit message compliance
git log --oneline 9740e45b352ca1e5d7f40f5754b977d3533dc8b4..3d1ad8c8d2d01f7c41e1f90a5e40d1a9e849cbb4

Verdict

2 blockers must be fixed before merge:

  1. Checkpatch warning: Document the qcom,adreno-07000400 compatible string in Documentation/devicetree/bindings/ or use an existing documented compatible.

  2. Patch compliance: Update all commit subject lines to use valid prefixes (UPSTREAM:, FROMLIST:, BACKPORT:, or no prefix) instead of PENDING:.

@quic-ksanadhy

Copy link
Copy Markdown

GFX Exception Jira has been approved.

@quic-ksanadhy

Copy link
Copy Markdown

@shashim-quic could you please approve this PR?

@qlijarvis

Copy link
Copy Markdown

🔨 Build Failure Analysis — PR #696

PR: #696
Build run: https://github.com/qualcomm-linux/kernel-config/actions/runs/27748096445

# Error File:Line PR-introduced? Root Cause
1 DTS syntax error arch/arm64/boot/dts/qcom/shikra-cqm-evk.dts:119 Yes Missing + prefix on closing brace }; for &gpu_zap_shader node
2 DTS syntax error arch/arm64/boot/dts/qcom/shikra-cqs-evk.dts:120 Yes Missing + prefix on closing brace }; for &gpu_zap_shader node
3 DTS syntax error arch/arm64/boot/dts/qcom/shikra-iqs-evk.dts:217 Yes Missing + prefix on closing brace }; for &gpu_zap_shader node

Verdict

All 3 errors are introduced by this PR due to malformed patch hunks in commit 008d720.

📎 Detailed analysis: Full report

@asherawa asherawa force-pushed the dt-shikra-smmu-separate branch from 8215926 to df48fe3 Compare June 18, 2026 09:28
Comment thread arch/arm64/boot/dts/qcom/shikra-iqs-evk.dts
shashim-quic
shashim-quic previously approved these changes Jun 18, 2026
@sgaud-quic

Copy link
Copy Markdown
Contributor

@asherawa please rebase PR on tip.

@asherawa asherawa force-pushed the dt-shikra-smmu-separate branch from df48fe3 to 06f7236 Compare June 18, 2026 11:20
@qcomlnxci qcomlnxci requested a review from a team June 18, 2026 11:22
@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 ❌ 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 ◻️

1 similar comment
@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 ❌ 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 ◻️

@asherawa asherawa force-pushed the dt-shikra-smmu-separate branch from 06f7236 to a08c22b Compare June 18, 2026 15:51
Komal-Bajaj
Komal-Bajaj previously approved these changes Jun 18, 2026
@qlijarvis

Copy link
Copy Markdown

PR #696 — validate-patch

PR: #696

Verdict Issues Detailed Report
⚠️ 0 Full report

Final Summary

  1. Lore link present: No — all three patches have PENDING: prefix; no lore links present or expected for pre-upstream work

  2. Lore link matches PR commits: N/A — no lore links to compare against

  3. Upstream patch status: Not upstream — PENDING: prefix explicitly marks these as pre-upstream patches; likely internal development or awaiting upstream submission

  4. PR present in qcom-next: Not checked — PENDING: patches are typically staged for future upstream submission

Verdict: ⚠️ — click to expand

🔍 Patch Validation

PR: #696 - shikra GPU support (3 patches)
Upstream commit: N/A (all patches marked PENDING:)
Verdict: ⚠️ PARTIAL


Patch 1/3: PENDING: arm64: dts: qcom: shikra: Add A704 GPU support

Commit Message

Check Status Note
Subject matches upstream N/A PENDING: prefix indicates not yet upstream
Body preserves rationale Clear description of what is added and where
Fixes tag present/correct N/A New feature, no Fixes tag needed
Authorship preserved Author: Aditya Sherawat asherawa@qti.qualcomm.com
Backport note (if applicable) N/A Not a backport

Diff

File Status Notes
arch/arm64/boot/dts/qcom/shikra-cqm-evk.dts Enables GPU and sets zap-shader firmware
arch/arm64/boot/dts/qcom/shikra-cqs-evk.dts Enables GPU and sets zap-shader firmware
arch/arm64/boot/dts/qcom/shikra-iqs-evk.dts Enables GPU and sets zap-shader firmware
arch/arm64/boot/dts/qcom/shikra.dtsi Adds GPU, GMU wrapper, OPP table nodes

Issues

  • None for commit structure; patch is well-formed

Patch 2/3: PENDING: arm64: dts: qcom: shikra: Add GPU cooling

Commit Message

Check Status Note
Subject matches upstream N/A PENDING: prefix indicates not yet upstream
Body preserves rationale Explains why GPU cooling is needed (no auto-throttle)
Fixes tag present/correct N/A New feature, no Fixes tag needed
Authorship preserved Author: Aastha Pandey aastha.pandey@oss.qualcomm.com
Backport note (if applicable) N/A Not a backport

Diff

File Status Notes
arch/arm64/boot/dts/qcom/shikra.dtsi Adds GPU thermal throttling at 115°C

Issues

  • None for commit structure; patch is well-formed

Patch 3/3: PENDING: arm64: dts: qcom: shikra: Add Adreno SMMU node

Commit Message

Check Status Note
Subject matches upstream N/A PENDING: prefix indicates not yet upstream
Body preserves rationale Clear description of what is added
Fixes tag present/correct N/A New feature, no Fixes tag needed
Authorship preserved Multiple authors properly credited with Signed-off-by
Backport note (if applicable) N/A Not a backport

Diff

File Status Notes
arch/arm64/boot/dts/qcom/shikra.dtsi Adds Adreno SMMU IOMMU node with clocks, interrupts

Issues

  • None for commit structure; patch is well-formed

Overall Assessment

Strengths:

  • All three patches follow proper kernel commit message format
  • Authorship is properly preserved with correct Signed-off-by tags
  • Commit bodies provide clear rationale for changes
  • Diffs are clean and focused on single logical changes
  • Patch 3/3 properly credits multiple co-authors

Observations:

  • All patches use "PENDING:" prefix, indicating they are not yet posted upstream
  • No lore.kernel.org links present in any commit message
  • No Link: tags or upstream references
  • Patches appear to be new development work for shikra SoC GPU support

Verdict

Patches are well-formed and follow kernel coding standards for commit messages and authorship. However, they are marked PENDING: and have no upstream references, indicating they are vendor-only or pre-upstream work.


Final Summary

  1. Lore link present: No — all three patches have PENDING: prefix; no lore links present or expected for pre-upstream work

  2. Lore link matches PR commits: N/A — no lore links to compare against

  3. Upstream patch status: Not upstream — PENDING: prefix explicitly marks these as pre-upstream patches; likely internal development or awaiting upstream submission

  4. PR present in qcom-next: Not checked — PENDING: patches are typically staged for future upstream submission

@qlijarvis

Copy link
Copy Markdown

PR #696 — checker-log-analyzer

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

Checker Result Summary
Checker Result Summary
checkpatch All 3 commits pass with no errors or warnings
dt-binding-check ⏭️ Skipped - no changes in Documentation/devicetree/bindings
dtb-check GPU node reg-names schema violation
sparse-check ⏭️ Skipped - no C code changes
check-uapi-headers ⏭️ Skipped - no UAPI header changes
check-patch-compliance All 3 commits use PENDING: prefix (not UPSTREAM:/FROMLIST:)
tag-check N/A Not applicable for this branch
qcom-next-check ⚠️ PENDING: prefix used - commits not ready for upstream

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #696 - PENDING: arm64: dts: qcom: shikra: Add A704 GPU support (3 commits)
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/27771925976

Checker Result Summary
checkpatch All 3 commits pass with no errors or warnings
dt-binding-check ⏭️ Skipped - no changes in Documentation/devicetree/bindings
dtb-check GPU node reg-names schema violation
sparse-check ⏭️ Skipped - no C code changes
check-uapi-headers ⏭️ Skipped - no UAPI header changes
check-patch-compliance All 3 commits use PENDING: prefix (not UPSTREAM:/FROMLIST:)
tag-check N/A Not applicable for this branch
qcom-next-check ⚠️ PENDING: prefix used - commits not ready for upstream

❌ dtb-check

Root cause: The GPU node defines 3 register regions (kgsl_3d0_reg_memory, cx_mem, cx_dbgc) but the schema expects only 2 for this Adreno GPU compatible string.

Failure details:

gpu@5900000 (qcom,adreno-07000400): reg-names:1: 'cx_dbgc' was expected
	from schema $id: http://devicetree.org/schemas/display/msm/gpu.yaml#
gpu@5900000 (qcom,adreno-07000400): reg-names: ['kgsl_3d0_reg_memory', 'cx_mem', 'cx_dbgc'] is too long
	from schema $id: http://devicetree.org/schemas/display/msm/gpu.yaml#

The schema validation indicates that for qcom,adreno-07000400:

  • Position 0: kgsl_3d0_reg_memory ✅ (correct)
  • Position 1: Expected cx_dbgc, but got cx_mem
  • Position 2: cx_dbgc is present but the array is too long ❌

Fix:

Option 1 (if cx_mem is not needed): Remove the cx_mem register region entirely:

 reg = <0x0 0x05900000 0x0 0x40000>,
-      <0x0 0x0599e000 0x0 0x1000>,
       <0x0 0x05961000 0x0 0x800>;
 reg-names = "kgsl_3d0_reg_memory",
-            "cx_mem",
             "cx_dbgc";

Option 2 (if both regions are needed): Update the DT schema in Documentation/devicetree/bindings/display/msm/gpu.yaml to allow 3 register regions for this GPU variant, then resubmit. The schema update must be submitted and accepted upstream first.

Option 3 (if this is vendor-specific): Check if the qcom,adreno-07000400 compatible needs a vendor-specific schema extension or if the register layout differs from upstream expectations.

Reproduce locally:

make ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- dtbs_check DT_SCHEMA_FILES=Documentation/devicetree/bindings/display/msm/gpu.yaml

❌ check-patch-compliance

Root cause: All three commits use the PENDING: subject prefix, which is not a recognized upstream compliance prefix.

Failure details:

Checking commit: PENDING: arm64: dts: qcom: shikra: Add A704 GPU support
Commit summary does not start with a required prefix

Checking commit: PENDING: arm64: dts: qcom: shikra: Add GPU cooling
Commit summary does not start with a required prefix

Checking commit: PENDING: arm64: dts: qcom: shikra: Add Adreno SMMU node
Commit summary does not start with a required prefix

Fix: Replace PENDING: with the appropriate prefix based on upstream status:

  • If patches are already merged upstream: Use UPSTREAM: prefix
  • If patches are posted to mailing list but not yet merged: Use FROMLIST: prefix
  • If patches are not yet posted upstream: Post them to the appropriate mailing list (devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org) first, then use FROMLIST:

Example for FROMLIST:

FROMLIST: arm64: dts: qcom: shikra: Add A704 GPU support

Reproduce locally:

# Check if commits follow required prefix convention
git log --oneline f8275513f58b..a08c22bc0385

Verdict

2 blockers must be fixed before merge:

  1. dtb-check failure - GPU register regions do not match schema expectations. Must either fix the DTS to match the schema or update the schema (requires upstream acceptance).

  2. check-patch-compliance failure - All commits need proper UPSTREAM: or FROMLIST: prefix instead of PENDING:.

The dtb-check issue is the more critical blocker as it indicates a potential hardware description mismatch that could affect driver functionality.

@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 ✅ Pass ❌ 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 ❌ Fail ✅ Pass ✅ Pass ✅ Pass ◻️
WiFi_OnOff ✅ Pass ❌ Fail ⚠️ skip ✅ 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 ⚠️ skip ✅ Pass ✅ Pass ✅ Pass ◻️

asherawa and others added 3 commits June 18, 2026 22:48
Add the A704 GPU and GMU wrapper nodes to shikra.dtsi with register
maps, clocks, interconnects, IOMMU, OPP table and zap-shader region.
Enable the GPU with its zap-shader firmware on the cqm-evk, cqs-evk and
iqs-evk boards.

Signed-off-by: Aditya Sherawat <asherawa@qti.qualcomm.com>
Unlike the CPU, the GPU does not throttle its speed automatically when it
reaches high temperatures.

Set up GPU cooling by throttling the GPU speed
when reaching 115°C.

Signed-off-by: Aastha Pandey <aastha.pandey@oss.qualcomm.com>
Add the Adreno GPU IOMMU (adreno_smmu) node for the Shikra SoC.

Signed-off-by: Bibek Kumar Patro <bibek.patro@oss.qualcomm.com>
Signed-off-by: Imran Shaik <imran.shaik@oss.qualcomm.com>
Signed-off-by: Komal Bajaj <komal.bajaj@oss.qualcomm.com>
@asherawa asherawa force-pushed the dt-shikra-smmu-separate branch from a08c22b to 660290b Compare June 18, 2026 17:19
@qcomlnxci qcomlnxci requested a review from a team June 18, 2026 17:21
@qlijarvis

Copy link
Copy Markdown

PR #696 — validate-patch

PR: #696

Verdict Issues Detailed Report
⚠️ 3 Full report

Final Summary

  1. Lore link present: No — PENDING: prefix; patches 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 prefix indicates work-in-progress for future submission
  4. PR present in qcom-next: Not checked — PENDING patches are vendor-tree development work

Recommendation: Fix commit order (move SMMU node before GPU node) and verify power domain reference before merge. Remove PENDING prefix when ready for upstream submission.

Verdict: ⚠️ — click to expand

🔍 Patch Validation

PR: #696 - Add Shikra GPU support (3 commits)
Upstream commit: N/A (PENDING patches)
Verdict: ⚠️ PARTIAL


Commit 1: PENDING: arm64: dts: qcom: shikra: Add A704 GPU support

Commit Message

Check Status Note
Subject matches upstream N/A PENDING prefix; not yet upstream
Body preserves rationale Clear description of what is added
Fixes tag present/correct N/A New feature, not a fix
Authorship preserved Single author with Signed-off-by
Backport note (if applicable) N/A Not a backport

Diff

File Status Notes
arch/arm64/boot/dts/qcom/shikra-cqm-evk.dts Enables GPU and sets firmware path
arch/arm64/boot/dts/qcom/shikra-cqs-evk.dts Enables GPU and sets firmware path
arch/arm64/boot/dts/qcom/shikra-iqs-evk.dts Enables GPU and sets firmware path
arch/arm64/boot/dts/qcom/shikra.dtsi Adds GPU, GMU wrapper, OPP table nodes

Issues

  • PENDING prefix: Indicates work-in-progress; should be removed before upstream submission
  • No Link tag: Missing lore.kernel.org reference (expected for PENDING status)
  • power-domains reference: Uses QCM2290_VDDCX which may be incorrect for Shikra SoC (appears to be copy-paste from QCM2290 reference)

Commit 2: PENDING: arm64: dts: qcom: shikra: Add GPU cooling

Commit Message

Check Status Note
Subject matches upstream N/A PENDING prefix; not yet upstream
Body preserves rationale Explains why GPU cooling is needed
Fixes tag present/correct N/A New feature, not a fix
Authorship preserved Single author with Signed-off-by
Backport note (if applicable) N/A Not a backport

Diff

File Status Notes
arch/arm64/boot/dts/qcom/shikra.dtsi Adds GPU thermal throttling at 115°C

Issues

  • PENDING prefix: Should be removed before upstream submission
  • No Link tag: Missing lore.kernel.org reference (expected for PENDING status)
  • Dependency: Depends on commit 1 (GPU node must exist first)

Commit 3: PENDING: arm64: dts: qcom: shikra: Add Adreno SMMU node

Commit Message

Check Status Note
Subject matches upstream N/A PENDING prefix; not yet upstream
Body preserves rationale ⚠️ Very brief; could explain SMMU purpose
Fixes tag present/correct N/A New feature, not a fix
Authorship preserved Three authors with proper Signed-off-by chain
Backport note (if applicable) N/A Not a backport

Diff

File Status Notes
arch/arm64/boot/dts/qcom/shikra.dtsi Adds Adreno SMMU with clocks, interrupts, power domain

Issues

  • PENDING prefix: Should be removed before upstream submission
  • No Link tag: Missing lore.kernel.org reference (expected for PENDING status)
  • Commit order: Should come before commit 1, as GPU node references &adreno_smmu which is defined here
  • Multiple authors: Three Signed-off-by tags suggest collaborative work; ensure all contributors are properly credited

Overall Issues

  1. Commit ordering: Logical dependency issue

    • Commit 1 references <&adreno_smmu 0 1> in the GPU node
    • Commit 3 defines the adreno_smmu node
    • Fix: Commit 3 should come before Commit 1
  2. PENDING prefix: All three commits use PENDING prefix

    • This is acceptable for internal/vendor trees during development
    • Must be removed before upstream submission
  3. No upstream references: No lore.kernel.org links or upstream commit references

    • Expected for PENDING status
    • These patches are not yet posted upstream
  4. Potential copy-paste error: Commit 1 uses QCM2290_VDDCX power domain

    • Shikra may need its own power domain constant
    • Verify this is correct for the target SoC
  5. Missing context: No cover letter or PR description explaining the series

    • Would help reviewers understand the feature enablement plan

Verdict

⚠️ PARTIAL PASS — Patches are structurally sound but have commit ordering issue and potential power domain error. Reorder commits (3→1→2) and verify QCM2290_VDDCX is correct for Shikra before merging.


Final Summary

  1. Lore link present: No — PENDING: prefix; patches 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 prefix indicates work-in-progress for future submission
  4. PR present in qcom-next: Not checked — PENDING patches are vendor-tree development work

Recommendation: Fix commit order (move SMMU node before GPU node) and verify power domain reference before merge. Remove PENDING prefix when ready for upstream submission.

@qlijarvis

Copy link
Copy Markdown

PR #696 — checker-log-analyzer

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

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 GPU node reg-names schema violation
sparse-check ⏭️ Skipped - no C code changes
check-uapi-headers ⏭️ Skipped - no UAPI header changes
check-patch-compliance All 3 commits use PENDING: prefix (not UPSTREAM:/FROMLIST:)
tag-check N/A Not applicable for this branch
qcom-next-check ⚠️ PENDING: prefix used - requires FROMLIST:/UPSTREAM: for qcom-next

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #696 - Add A704 GPU support, GPU cooling, and Adreno SMMU node for Shikra
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/27777042022

Checker Result Summary
checkpatch All 3 commits passed with no style issues
dt-binding-check ⏭️ Skipped - no changes in Documentation/devicetree/bindings
dtb-check GPU node reg-names schema violation
sparse-check ⏭️ Skipped - no C code changes
check-uapi-headers ⏭️ Skipped - no UAPI header changes
check-patch-compliance All 3 commits use PENDING: prefix (not UPSTREAM:/FROMLIST:)
tag-check N/A Not applicable for this branch
qcom-next-check ⚠️ PENDING: prefix used - requires FROMLIST:/UPSTREAM: for qcom-next

❌ dtb-check

Root cause: GPU node defines 3 reg-names entries but the Adreno GPU schema expects only 2 for this compatible string.

Failure details:

/opt/actions-runner/_work/kernel-config/kernel-config/kernel/temp-out/arch/arm64/boot/dts/qcom/shikra-cqm-evk.dtb: 
  gpu@5900000 (qcom,adreno-07000400): reg-names:1: 'cx_dbgc' was expected
	from schema $id: http://devicetree.org/schemas/display/msm/gpu.yaml#

/opt/actions-runner/_work/kernel-config/kernel-config/kernel/temp-out/arch/arm64/boot/dts/qcom/shikra-cqm-evk.dtb: 
  gpu@5900000 (qcom,adreno-07000400): reg-names: ['kgsl_3d0_reg_memory', 'cx_mem', 'cx_dbgc'] is too long
	from schema $id: http://devicetree.org/schemas/display/msm/gpu.yaml#

The GPU node in arch/arm64/boot/dts/qcom/shikra.dtsi defines:

reg-names = "kgsl_3d0_reg_memory",
            "cx_mem",
            "cx_dbgc";

But the schema at Documentation/devicetree/bindings/display/msm/gpu.yaml expects only 2 entries for qcom,adreno-07000400, with the second entry being cx_dbgc (not cx_mem). The schema validation indicates:

  • Position 1 should be cx_dbgc but found cx_mem
  • The array is too long (3 entries instead of 2)

Fix:

Option 1 (if cx_mem is not needed): Remove the cx_mem entry:

 reg = <0x0 0x05900000 0x0 0x40000>,
-      <0x0 0x0599e000 0x0 0x1000>,
       <0x0 0x05961000 0x0 0x800>;
 reg-names = "kgsl_3d0_reg_memory",
-            "cx_mem",
             "cx_dbgc";

Option 2 (if cx_mem is required): Update the GPU binding schema to allow 3 reg entries for this compatible, or use a different compatible string that supports 3 regions.

Reproduce locally:

make ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- defconfig
make ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- dtbs_check DT_SCHEMA_FILES=Documentation/devicetree/bindings/display/msm/gpu.yaml

❌ check-patch-compliance

Root cause: All 3 commits use the PENDING: subject prefix, which is not a recognized upstream status tag.

Failure details:

Checking commit: PENDING: arm64: dts: qcom: shikra: Add A704 GPU support
Commit summary does not start with a required prefix

Checking commit: PENDING: arm64: dts: qcom: shikra: Add GPU cooling
Commit summary does not start with a required prefix

Checking commit: PENDING: arm64: dts: qcom: shikra: Add Adreno SMMU node
Commit summary does not start with a required prefix

The checker expects one of the following prefixes:

  • UPSTREAM: - for patches already merged in mainline
  • FROMLIST: - for patches posted to upstream mailing lists
  • BACKPORT: - for backported patches
  • No prefix - for Qualcomm-specific patches not intended for upstream

Fix:

If these patches are intended for upstream submission, update the commit subjects:

If already posted to mailing list:

FROMLIST: arm64: dts: qcom: shikra: Add A704 GPU support
FROMLIST: arm64: dts: qcom: shikra: Add GPU cooling
FROMLIST: arm64: dts: qcom: shikra: Add Adreno SMMU node

If not yet posted but will be:
Remove the PENDING: prefix entirely:

arm64: dts: qcom: shikra: Add A704 GPU support
arm64: dts: qcom: shikra: Add GPU cooling
arm64: dts: qcom: shikra: Add Adreno SMMU node

If already merged upstream:

UPSTREAM: arm64: dts: qcom: shikra: Add A704 GPU support

Reproduce locally:

# From kernel root
git log --oneline 9297c7a62d86..660290b9ae04
# Check each commit subject starts with UPSTREAM:/FROMLIST:/BACKPORT: or has no prefix

Verdict

2 blockers must be fixed before merge:

  1. dtb-check failure - GPU node reg-names schema violation must be resolved by either removing the extra cx_mem region or updating the binding schema
  2. check-patch-compliance failure - Replace PENDING: prefix with appropriate tag (FROMLIST:, UPSTREAM:, or remove prefix)

@sgaud-quic sgaud-quic merged commit afef7d2 into qualcomm-linux:qcom-6.18.y Jun 18, 2026
6 of 8 checks passed
@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 ◻️
BT_ON_OFF ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ◻️
BT_SCAN ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ◻️
CPUFreq_Validation ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ◻️
CPU_affinity ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ◻️
DSP_AudioPD ◻️ ✅ Pass ⚠️ skip ✅ Pass ✅ Pass ⚠️ skip ◻️
Ethernet ◻️ ✅ Pass ⚠️ skip ⚠️ skip ⚠️ skip ⚠️ skip ◻️
Freq_Scaling ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ◻️
GIC ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ◻️
IPA ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ◻️
Interrupts ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ◻️
OpenCV ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ◻️
PCIe ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ◻️
Probe_Failure_Check ◻️ ❌ Fail ❌ Fail ❌ Fail ❌ Fail ❌ Fail ◻️
RMNET ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ◻️
UFS_Validation ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ◻️
USBHost ◻️ ❌ Fail ❌ Fail ❌ Fail ❌ Fail ❌ Fail ◻️
WiFi_Firmware_Driver ◻️ ❌ Fail ✅ Pass ✅ Pass ✅ Pass ✅ Pass ◻️
WiFi_OnOff ◻️ ❌ Fail ✅ Pass ✅ Pass ✅ Pass ✅ Pass ◻️
adsp_remoteproc ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ❌ Fail ◻️
cdsp_remoteproc ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ❌ Fail ◻️
gpdsp_remoteproc ◻️ ✅ Pass ⚠️ skip ⚠️ skip ✅ Pass ❌ Fail ◻️
hotplug ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ◻️
irq ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ◻️
kaslr ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ◻️
pinctrl ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ◻️
qcom_hwrng ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ◻️
remoteproc ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ❌ Fail ◻️
rngtest ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ◻️
shmbridge ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ◻️
smmu ◻️ ✅ Pass ❌ Fail ✅ Pass ✅ Pass ❌ Fail ◻️
watchdog ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ◻️
wpss_remoteproc ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ◻️

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