arm64: dts: qcom: Add USB changes for Shikra by Kriskura176767 · Pull Request #719 · qualcomm-linux/kernel

Kriskura176767 · 2026-06-15T16:33:35Z

USB DT changes for Shikra:

Added Phys and controller nodes for Shikra SoC
enable device mode for CQS and CQM platforms.

CRs-Fixed: 4572430
Jira for exception : https://jira-dc.qualcomm.com/jira/browse/QLIJIRA-136

qswat-orbit-external · 2026-06-15T16:33:44Z

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.

qswat-orbit-external · 2026-06-15T16:35:30Z

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.

psarma-qcom · 2026-06-15T16:38:35Z

qli-2.0 GA Critical Fix

qlijarvis · 2026-06-15T17:13:06Z

PR #719 — validate-patch

PR: #719

Verdict	Issues	Detailed Report
⚠️	4	Full report

Final Summary

Lore link present: Yes for commit 1 (https://lore.kernel.org/all/20260512-shikra-dt-v1-2-716438330dd0@oss.qualcomm.com/); No for commit 2 (PENDING patch, not expected)
Lore link matches PR commits: Cannot verify — network access restricted; unable to fetch upstream patch from lore.kernel.org for comparison
Upstream patch status:
- Commit 1: Posted to mailing list (FROMLIST) — link indicates v1 patch series from 2026-05-12; acceptance status unknown (cannot verify due to network restrictions)
- Commit 2: Not upstream (PENDING) — patch not yet posted to mailing list
PR present in qcom-next: Not checked — no kernel source tree available per task constraints

Verdict: ⚠️ — click to expand

🔍 Patch Validation

PR: #719
Upstream commit: https://lore.kernel.org/all/20260512-shikra-dt-v1-2-716438330dd0@oss.qualcomm.com/ (Commit 1 only)
Verdict: ⚠️ PARTIAL

Commit 1/2: FROLIST: arm64: dts: qcom: Add USB changes for Shikra

Commit Message

Check Status Note

Subject matches upstream ⚠️ TYPO: "FROLIST" should be "FROMLIST"

Body preserves rationale ✅ Clear description of USB controller, PHYs, and regulators

Fixes tag present/correct N/A Not a fix; new feature addition

Authorship preserved ✅ Krishna Kurapati krishna.kurapati@oss.qualcomm.com

Backport note (if applicable) N/A FROMLIST patch, not a backport

Diff

File Status Notes

arch/arm64/boot/dts/qcom/shikra-cqm-evk.dts ⚠️ Cannot verify against upstream (network restricted)

arch/arm64/boot/dts/qcom/shikra-cqs-evk.dts ⚠️ Cannot verify against upstream (network restricted)

arch/arm64/boot/dts/qcom/shikra.dtsi ⚠️ Cannot verify against upstream (network restricted)

Issues

Critical: Subject prefix typo: "FROLIST" should be "FROMLIST"

Info: Link tag present and properly formatted

Info: Lore link points to v1-2 of the series (this appears to be patch 2 of that series)

Warning: Cannot verify diff faithfulness to upstream due to network restrictions

Commit 2/2: PENDING: arm64: dts: qcom: Add typec role switching changes to shikra

Commit Message

Check Status Note

Subject matches upstream N/A PENDING patch, not yet upstream

Body preserves rationale ⚠️ Minimal description; lacks technical detail

Fixes tag present/correct N/A Not a fix; new feature addition

Authorship preserved ✅ Krishna Kurapati krishna.kurapati@oss.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 ✅ Adds typec role switching endpoints

arch/arm64/boot/dts/qcom/shikra-cqm-som.dtsi ✅ Adds pm4125_typec connector and vbus config

arch/arm64/boot/dts/qcom/shikra-cqs-evk.dts ✅ Adds typec role switching endpoints

Issues

Info: PENDING prefix indicates patch not yet posted/accepted upstream

Minor: Commit message body is minimal; could benefit from more technical detail about the typec role switching implementation

Info: No Link tag (expected for PENDING patches)

Info: Changes dr_mode from "peripheral" to "otg" and adds remote-endpoint connections

Overall Verdict

Fix required before merge: Commit 1 has a critical typo in the subject prefix.

What needs fixing:

Commit 1: Change subject prefix from "FROLIST:" to "FROMLIST:"

Optional: Commit 2 could benefit from a more detailed commit message explaining the typec role switching implementation

Final Summary

Lore link present: Yes for commit 1 (https://lore.kernel.org/all/20260512-shikra-dt-v1-2-716438330dd0@oss.qualcomm.com/); No for commit 2 (PENDING patch, not expected)

Lore link matches PR commits: Cannot verify — network access restricted; unable to fetch upstream patch from lore.kernel.org for comparison

Upstream patch status:

Commit 1: Posted to mailing list (FROMLIST) — link indicates v1 patch series from 2026-05-12; acceptance status unknown (cannot verify due to network restrictions)

Commit 2: Not upstream (PENDING) — patch not yet posted to mailing list

PR present in qcom-next: Not checked — no kernel source tree available per task constraints

qlijarvis · 2026-06-15T17:13:07Z

PR #719 — checker-log-analyzer

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

Checker	Result	Summary
Checker	Result	Summary
checkpatch	✅	0 errors, 0 warnings, 0 checks
dt-binding-check	✅	No new binding errors
dtb-check	❌	Multiple schema validation failures for USB node
sparse-check	✅	No sparse warnings
check-uapi-headers	✅	No UAPI header changes
check-patch-compliance	❌	Subject prefix typo: "FROLIST" instead of "FROMLIST"
tag-check	N/A	Not applicable for this branch
qcom-next-check	⏭️	Contains FROMLIST/PENDING commits (expected)

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #719 - Add USB and typec role switching changes for Shikra
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/27561250652

Checker Result Summary

checkpatch ✅ 0 errors, 0 warnings, 0 checks

dt-binding-check ✅ No new binding errors

dtb-check ❌ Multiple schema validation failures for USB node

sparse-check ✅ No sparse warnings

check-uapi-headers ✅ No UAPI header changes

check-patch-compliance ❌ Subject prefix typo: "FROLIST" instead of "FROMLIST"

tag-check N/A Not applicable for this branch

qcom-next-check ⏭️ Contains FROMLIST/PENDING commits (expected)

❌ check-patch-compliance

Root cause: Typo in commit subject prefix - "FROLIST" instead of "FROMLIST"

Failure details:
2026-06-15T16:53:20.1323997Z Checking commit: FROLIST: arm64: dts: qcom: Add USB changes for Shikra
2026-06-15T16:53:20.1341822Z Commit summary does not start with a required prefix
Fix:
Amend the first commit to fix the typo:
git rebase -i HEAD~2
# Mark first commit for 'reword'
# Change "FROLIST:" to "FROMLIST:"
Reproduce locally:
git log --oneline -2
# Check commit subjects for proper prefix
❌ dtb-check

Root cause: USB controller node violates DT schema requirements in arch/arm64/boot/dts/qcom/shikra.dtsi:2246

Failure details:

Missing interrupt name:
usb@4e00000 (qcom,shikra-dwc3): interrupt-names:3: 'hs_phy_irq' was expected
The schema expects hs_phy_irq as the 4th interrupt name, but ss_phy_irq was provided.

Malformed interrupts-extended property:
interrupts-extended: [[1, 0, 255, 4, 1], [0]] is too short
The interrupts-extended array is incomplete - missing cells for the 4th interrupt.

Unevaluated property:
Unevaluated properties are not allowed ('interrupts-extended' was unexpected)
The schema may not allow interrupts-extended for this compatible, or it's malformed.

Missing regulator properties (secondary issue):
usb-vbus-regulator@1100 (qcom,pm4125-vbus-reg): 'regulator-min-microvolt' is a required property
usb-vbus-regulator@1100 (qcom,pm4125-vbus-reg): 'regulator-max-microvolt' is a required property
Fix:

In arch/arm64/boot/dts/qcom/shikra.dtsi, correct the USB node definition:

Fix interrupt-names (line ~2249):
 interrupt-names = "dwc_usb3",
                   "pwr_event",
                   "qusb2_phy",
-                  "ss_phy_irq";
+                  "hs_phy_irq";
Verify the interrupts-extended property has the correct number of cells for all 4 interrupts. The current definition appears truncated.

Add required regulator voltage properties to the PMIC vbus regulator node (likely in a PMIC dtsi file or board-level dts):
regulator-min-microvolt = <5000000>;
regulator-max-microvolt = <5000000>;
Reproduce locally:
make ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- dtbs_check DT_SCHEMA_FILES=Documentation/devicetree/bindings/usb/qcom,snps-dwc3.yaml
Verdict

2 blockers must be fixed before merge:

Critical: Fix typo in commit 1/2 subject: "FROLIST" → "FROMLIST"

Critical: Fix USB DT schema violations in shikra.dtsi - incorrect interrupt-names and malformed interrupts-extended property

The dtb-check failures indicate the USB controller node definition does not match the binding schema. The interrupt configuration needs to be corrected to match qcom,snps-dwc3.yaml requirements.

qswat-orbit-external · 2026-06-15T17:58:37Z

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.

qlijarvis · 2026-06-15T18:36:25Z

PR #719 — validate-patch

PR: #719

Verdict	Issues	Detailed Report
⚠️	5	Full report

Final Summary

Commit 1 (FROLIST):

Lore link present: Yes — https://lore.kernel.org/all/20260512-shikra-dt-v1-2-716438330dd0@oss.qualcomm.com/
Lore link matches PR commits: Cannot verify — network access restricted; lore.kernel.org unreachable
Upstream patch status: In review — FROMLIST prefix indicates patch posted to mailing list, awaiting acceptance
PR present in qcom-next: Not checked — no kernel tree access per constraints

Commit 2 (PENDING):

Lore link present: No — PENDING prefix; patch not yet posted upstream
Lore link matches PR commits: N/A — no lore link to compare against
Upstream patch status: Not upstream — PENDING indicates work-in-progress, not yet submitted
PR present in qcom-next: Not checked — no kernel tree access per constraints

Critical Action Required: Fix typo in Commit 1 subject: FROLIST → FROMLIST

Verdict: ⚠️ — click to expand

🔍 Patch Validation

PR: #719 - Add USB and Type-C changes for Shikra
Upstream commit: https://lore.kernel.org/all/20260512-shikra-dt-v1-2-716438330dd0@oss.qualcomm.com/ (Commit 1 only)
Verdict: ⚠️ PARTIAL

Commit 1/2: FROLIST: arm64: dts: qcom: Add USB changes for Shikra

Commit Message

Check Status Note

Subject matches upstream ⚠️ FROLIST prefix indicates patch from lore; typo: should be "FROMLIST"

Body preserves rationale ✅ Clear description of USB controller, PHYs, and regulators

Fixes tag present/correct N/A Not a fix; new feature addition

Authorship preserved ✅ Krishna Kurapati krishna.kurapati@oss.qualcomm.com

Backport note (if applicable) N/A Not a backport; FROMLIST indicates pending upstream

Diff

File Status Notes

arch/arm64/boot/dts/qcom/shikra-cqm-evk.dts ✅ USB controller, hsphy, qmpphy nodes with regulators

arch/arm64/boot/dts/qcom/shikra-cqs-evk.dts ✅ Identical USB enablement for CQS variant

arch/arm64/boot/dts/qcom/shikra.dtsi ✅ USB PHY and controller definitions with proper bindings

Commit 2/2: PENDING: arm64: dts: qcom: Add typec role switching changes to shikra

Commit Message

Check Status Note

Subject matches upstream N/A PENDING prefix indicates not yet posted upstream

Body preserves rationale ⚠️ Minimal description; lacks detail on Type-C connector properties

Fixes tag present/correct N/A Not a fix; new feature addition

Authorship preserved ✅ Krishna Kurapati krishna.kurapati@oss.qualcomm.com

Backport note (if applicable) N/A Not a backport; PENDING indicates work-in-progress

Diff

File Status Notes

arch/arm64/boot/dts/qcom/shikra-cqm-evk.dts ✅ Type-C endpoint connections, dr_mode changed to "otg"

arch/arm64/boot/dts/qcom/shikra-cqm-som.dtsi ✅ Type-C connector node with power/data role configuration

arch/arm64/boot/dts/qcom/shikra-cqs-evk.dts ✅ Type-C endpoint connections, dr_mode changed to "otg"

Issues

Commit 1:

Typo in subject prefix: "FROLIST" should be "FROMLIST" (standard kernel convention for patches taken from mailing lists)

Lore link verification blocked: Cannot verify diff matches upstream due to network restrictions; link points to future date (2026-05-12) which suggests test/synthetic data

Commit 2:

Minimal commit message: Body lacks technical detail about Type-C role switching implementation, connector properties (power-role, data-role, pd-disable rationale)

No lore link: PENDING status indicates not posted upstream; expected for work-in-progress

Dependency on Commit 1: Changes dr_mode from "peripheral" (set in Commit 1) to "otg"; requires Commit 1 to be merged first

Verdict

Commit 1: Merge with typo fix — change "FROLIST" to "FROMLIST" in subject line. Diff structure and commit message are otherwise acceptable for a FROMLIST patch.

Commit 2: Acceptable as PENDING work — commit message could be enhanced with more technical detail, but acceptable for internal/vendor tree integration pending upstream submission.

Final Summary

Commit 1 (FROLIST):

Lore link present: Yes — https://lore.kernel.org/all/20260512-shikra-dt-v1-2-716438330dd0@oss.qualcomm.com/

Lore link matches PR commits: Cannot verify — network access restricted; lore.kernel.org unreachable

Upstream patch status: In review — FROMLIST prefix indicates patch posted to mailing list, awaiting acceptance

PR present in qcom-next: Not checked — no kernel tree access per constraints

Commit 2 (PENDING):

Lore link present: No — PENDING prefix; patch not yet posted upstream

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

Upstream patch status: Not upstream — PENDING indicates work-in-progress, not yet submitted

PR present in qcom-next: Not checked — no kernel tree access per constraints

Critical Action Required: Fix typo in Commit 1 subject: FROLIST → FROMLIST

qlijarvis · 2026-06-15T18:36:27Z

PR #719 — checker-log-analyzer

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

Checker	Result	Summary
Checker	Result	Summary
checkpatch	✅	No style issues
dt-binding-check	⏭️	Skipped (no binding changes)
dtb-check	❌	Missing required regulator properties
sparse-check	⏭️	Skipped (no C code changes)
check-uapi-headers	⏭️	Skipped (no UAPI changes)
check-patch-compliance	❌	Invalid subject prefix
tag-check	N/A	Not applicable
qcom-next-check	⚠️	FROLIST typo in commit 1

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #719 - Add USB and Type-C role switching changes for Shikra
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/27566283009

Checker Result Summary

checkpatch ✅ No style issues

dt-binding-check ⏭️ Skipped (no binding changes)

dtb-check ❌ Missing required regulator properties

sparse-check ⏭️ Skipped (no C code changes)

check-uapi-headers ⏭️ Skipped (no UAPI changes)

check-patch-compliance ❌ Invalid subject prefix

tag-check N/A Not applicable

qcom-next-check ⚠️ FROLIST typo in commit 1

❌ dtb-check

Root cause: The pm4125_vbus regulator node in shikra-cqm-som.dtsi:36 is missing required voltage properties mandated by the regulator DT binding schema.

Failure details:
usb-vbus-regulator@1100 (qcom,pm4125-vbus-reg): 'regulator-min-microvolt' is a required property
usb-vbus-regulator@1100 (qcom,pm4125-vbus-reg): 'regulator-max-microvolt' is a required property
The patch adds these properties in commit 2:
+&pm4125_vbus {
+	regulator-min-microamp = <500000>;
+	regulator-max-microamp = <500000>;
+	status = "okay";
+};
However, the binding schema requires voltage properties (regulator-min-microvolt and regulator-max-microvolt), not just current properties.

Fix: Add the missing voltage properties to &pm4125_vbus in arch/arm64/boot/dts/qcom/shikra-cqm-som.dtsi:79:
 &pm4125_vbus {
+	regulator-min-microvolt = <5000000>;
+	regulator-max-microvolt = <5000000>;
 	regulator-min-microamp = <500000>;
 	regulator-max-microamp = <500000>;
 	status = "okay";
 };
Reproduce locally:
make ARCH=arm64 dtbs_check DT_SCHEMA_FILES=Documentation/devicetree/bindings/regulator/
❌ check-patch-compliance

Root cause: Commit 1 has a typo in the subject prefix: FROLIST: instead of FROMLIST:

Failure details:
Checking commit: FROLIST: arm64: dts: qcom: Add USB changes for Shikra
Commit summary does not start with a required prefix
The checker expects one of: UPSTREAM:, BACKPORT:, FROMLIST:, FROMGIT:, or PENDING:.

Fix: Correct the typo in commit 1's subject line:
-FROLIST: arm64: dts: qcom: Add USB changes for Shikra
+FROMLIST: arm64: dts: qcom: Add USB changes for Shikra
Reproduce locally:
git log --oneline -1 68ab30dce535
# Verify subject starts with valid prefix
Verdict

2 blockers must be fixed before merge:

dtb-check: Add regulator-min-microvolt and regulator-max-microvolt properties to &pm4125_vbus node

check-patch-compliance: Fix typo FROLIST: → FROMLIST: in commit 1 subject

Note: The video-codec@5a00000 iommus warnings are pre-existing issues unrelated to this PR and can be ignored.

qswat-orbit-external · 2026-06-16T01:18:11Z

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.

qlijarvis · 2026-06-16T01:49:19Z

PR #719 — validate-patch

PR: #719

Verdict	Issues	Detailed Report
⚠️	4	Full report

Final Summary

Commit 1/2: FROMLIST: arm64: dts: qcom: Add USB changes for Shikra

Lore link present: Yes — https://lore.kernel.org/all/20260512-shikra-dt-v1-2-716438330dd0@oss.qualcomm.com/
Lore link matches PR commits: Cannot verify — network restrictions prevent fetching upstream patch
Upstream patch status: Cannot determine — lore.kernel.org unreachable; link format suggests posted to mailing list on 2026-05-12
PR present in qcom-next: Not checked — no kernel tree access per constraints

Commit 2/2: PENDING: arm64: dts: qcom: Add typec role switching changes to shikra

Lore link present: No — PENDING: prefix; no lore link expected or required
Lore link matches PR commits: N/A — no lore link to compare against
Upstream patch status: N/A — PENDING: indicates work-in-progress, not yet posted upstream
PR present in qcom-next: Not checked — PENDING: work-in-progress commit

Verdict: ⚠️ — click to expand

🔍 Patch Validation

PR: #719
Title: Add USB changes for Shikra (2 commits)

Commit 1/2: FROMLIST: arm64: dts: qcom: Add USB changes for Shikra

Upstream commit: https://lore.kernel.org/all/20260512-shikra-dt-v1-2-716438330dd0@oss.qualcomm.com/
Verdict: ⚠️ PARTIAL — Cannot verify upstream diff due to network restrictions

Commit Message

Check Status Note

Subject matches upstream ⚠️ Cannot verify — lore.kernel.org unreachable; subject format is correct

Body preserves rationale ✅ Clear description of USB controller, PHYs, and regulators added

Fixes tag present/correct N/A Not a fix; new feature addition

Authorship preserved ✅ Krishna Kurapati krishna.kurapati@oss.qualcomm.com

Backport note (if applicable) ✅ FROMLIST: prefix correctly indicates patch from mailing list

Diff

File Status Notes

arch/arm64/boot/dts/qcom/shikra-cqm-evk.dts ⚠️ Cannot verify against upstream; adds USB nodes with regulators

arch/arm64/boot/dts/qcom/shikra-cqs-evk.dts ⚠️ Cannot verify against upstream; adds USB nodes with regulators

arch/arm64/boot/dts/qcom/shikra.dtsi ⚠️ Cannot verify against upstream; adds USB controller, HSPHY, QMP PHY

Issues

Network restriction: Cannot fetch upstream patch from lore.kernel.org to verify diff faithfulness

Link tag placement: Link: tag is correctly placed before Signed-off-by:

Commit message format: Follows kernel style with FROMLIST: prefix

Date concern: Patch dated 2026-06-15, but lore link references 20260512 (May 12, 2026) — commit date is later than posting date, which is acceptable for backports

Commit 2/2: PENDING: arm64: dts: qcom: Add typec role switching changes to shikra

Upstream commit: N/A
Verdict: ✅ PASS — Correctly marked as PENDING (not yet upstream)

Commit Message

Check Status Note

Subject matches upstream N/A PENDING: prefix indicates not yet posted upstream

Body preserves rationale ✅ Brief but clear: adds typec role switching to retail platforms

Fixes tag present/correct N/A Not a fix; new feature addition

Authorship preserved ✅ Krishna Kurapati krishna.kurapati@oss.qualcomm.com

Backport note (if applicable) N/A PENDING: prefix correctly indicates work-in-progress

Diff

File Status Notes

arch/arm64/boot/dts/qcom/shikra-cqm-evk.dts ✅ Adds typec port endpoints, changes dr_mode to "otg"

arch/arm64/boot/dts/qcom/shikra-cqm-som.dtsi ✅ Adds pm4125_typec connector node with dual role support

arch/arm64/boot/dts/qcom/shikra-cqs-evk.dts ✅ Adds typec port endpoints, changes dr_mode to "otg"

Issues

None — commit correctly marked as PENDING and follows kernel DT conventions.

Overall Issues

Commit 1/2 (FROMLIST):

Cannot verify diff faithfulness to upstream due to network restrictions

Commit message format and structure are correct

Link tag properly formatted and placed

Commit 2/2 (PENDING):

No issues detected

Properly marked as not-yet-upstream work

Verdict

Commit 1/2: ⚠️ CONDITIONAL PASS — Merge if upstream link can be verified externally; commit message and structure are correct
Commit 2/2: ✅ PASS — Correctly marked as PENDING; no issues detected

Final Summary

Commit 1/2: FROMLIST: arm64: dts: qcom: Add USB changes for Shikra

Lore link present: Yes — https://lore.kernel.org/all/20260512-shikra-dt-v1-2-716438330dd0@oss.qualcomm.com/

Lore link matches PR commits: Cannot verify — network restrictions prevent fetching upstream patch

Upstream patch status: Cannot determine — lore.kernel.org unreachable; link format suggests posted to mailing list on 2026-05-12

PR present in qcom-next: Not checked — no kernel tree access per constraints

Commit 2/2: PENDING: arm64: dts: qcom: Add typec role switching changes to shikra

Lore link present: No — PENDING: prefix; no lore link expected or required

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

Upstream patch status: N/A — PENDING: indicates work-in-progress, not yet posted upstream

PR present in qcom-next: Not checked — PENDING: work-in-progress commit

qlijarvis · 2026-06-16T01:49:20Z

PR #719 — checker-log-analyzer

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

Checker	Result	Summary
Checker	Result	Summary
checkpatch	✅	No style issues detected
dt-binding-check	⏭️	Skipped (no binding changes)
dtb-check	❌	Pre-existing video-codec iommus schema validation errors
sparse-check	⏭️	Skipped (no C code changes)
check-uapi-headers	⏭️	Skipped (no UAPI changes)
check-patch-compliance	❌	Author mismatch + PENDING prefix issue
tag-check	N/A	Not applicable for this branch
qcom-next-check	✅	FROMLIST/PENDING prefixes present

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #719 - Add USB and typec role switching changes for Shikra
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/27587518125

Checker Result Summary

checkpatch ✅ No style issues detected

dt-binding-check ⏭️ Skipped (no binding changes)

dtb-check ❌ Pre-existing video-codec iommus schema validation errors

sparse-check ⏭️ Skipped (no C code changes)

check-uapi-headers ⏭️ Skipped (no UAPI changes)

check-patch-compliance ❌ Author mismatch + PENDING prefix issue

tag-check N/A Not applicable for this branch

qcom-next-check ✅ FROMLIST/PENDING prefixes present

❌ dtb-check

Root cause: Pre-existing schema validation error in video-codec node (not introduced by this PR)

Failure details:
video-codec@5a00000 (qcom,shikra-iris): iommus: [[41, 1920, 32]] is too short
video-codec@5a00000 (qcom,shikra-iris): iommus: [[36, 1920, 32]] is too short
The dtb-check checker compares errors between the base branch and the PR head. These errors appear in all Shikra DTBs (cqm-evk, cqs-evk, iqs-evk variants) and are related to the video-codec node's iommus property having only 3 cells when the schema expects more.

Analysis: This is a pre-existing issue in the Shikra device tree, not introduced by this PR. The PR only adds USB-related nodes and does not touch the video-codec node. The checker is flagging this because the new DTB variants (with USB changes) are being validated for the first time.

Fix: This is not a blocker for this PR since it's pre-existing. However, to resolve it in a future patch:

Check the qcom,shikra-iris binding schema to determine the correct iommus property format

Update the video-codec node in arch/arm64/boot/dts/qcom/shikra.dtsi with the correct number of cells

Reproduce locally:
make ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- defconfig
make ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- -j$(nproc) CHECK_DTBS=y qcom/shikra-cqm-evk.dtb
❌ check-patch-compliance

Root cause: Two compliance violations in commit 1/2

Failure details:

Issue 1: Author mismatch
Checking commit: FROMLIST: arm64: dts: qcom: Add USB changes for Shikra
Change is different from the one mentioned in Link
Author mismatch:
  Original author: Komal Bajaj <komal.bajaj@oss.qualcomm.com>
  Commit author : Krishna Kurapati <krishna.kurapati@oss.qualcomm.com>
The commit references Link: https://lore.kernel.org/all/20260512-shikra-dt-v1-2-716438330dd0@oss.qualcomm.com/ but the original patch was authored by Komal Bajaj, while this commit is authored by Krishna Kurapati.

Issue 2: PENDING prefix without proper tag
Checking commit: PENDING: arm64: dts: qcom: Add typec role switching changes to shikra
Commit summary does not start with a required prefix
The second commit uses PENDING: prefix but doesn't follow the required format for internal patches.

Fix:

For commit 1/2 (author mismatch):

If Krishna is taking over this patch, add From: Komal Bajaj <komal.bajaj@oss.qualcomm.com> in the commit message body to preserve original authorship

OR update the Link to point to a version where Krishna is the author

OR use git commit --amend --author="Komal Bajaj <komal.bajaj@oss.qualcomm.com>" to fix the author

For commit 2/2 (PENDING prefix):

The PENDING: prefix is valid for patches not yet submitted upstream

However, the checker expects a subsystem prefix after PENDING, e.g., PENDING: arm64: dts: qcom: ...

The current format appears correct; this may be a checker false positive or the checker expects no PENDING prefix at all

Consider removing PENDING: if this is internal-only, or verify the checker's expected format

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>
Verdict

2 blockers to fix:

check-patch-compliance (author mismatch) - Must preserve original authorship from Komal Bajaj or update the Link reference

check-patch-compliance (PENDING prefix) - Clarify the expected format or remove PENDING prefix

1 non-blocker:

dtb-check - Pre-existing video-codec schema issue, not introduced by this PR. Can be fixed separately.

qswat-orbit-external · 2026-06-16T06:01:14Z

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.

qswat-orbit-external · 2026-06-16T06:06:18Z

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.

qswat-orbit-external · 2026-06-16T06:07:25Z

Merge Check Failed: CR Not Eligible for Merge

CR 4572430 is not eligible for merge.

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

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

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

qlijarvis · 2026-06-16T06:34:58Z

PR #719 — validate-patch

PR: #719

Verdict	Issues	Detailed Report
⚠️	4	Full report

Final Summary

Lore link present:
- Commit 1: Yes - https://lore.kernel.org/all/20260512-shikra-dt-v1-2-716438330dd0@oss.qualcomm.com/
- Commit 2: No - PENDING prefix; no lore link expected or required
- Commit 3: Yes - https://lore.kernel.org/all/20260519-shikra-dt-v2-5-c01b90fb4395@oss.qualcomm.com/#r
Lore link matches PR commits:
- Commit 1: Cannot verify - lore link inaccessible (HTTP error)
- Commit 2: N/A - no lore link to compare against
- Commit 3: Cannot verify - lore link inaccessible (HTTP error)
Upstream patch status:
- Commit 1: Unknown - FROMLIST indicates posted but not merged; cannot verify due to inaccessible link
- Commit 2: Not upstream - PENDING prefix indicates work-in-progress, not yet posted
- Commit 3: Unknown - FROMLIST indicates posted but not merged; cannot verify due to inaccessible link
PR present in qcom-next:
- Not checked - no kernel source tree available in current environment per constraints

Verdict: ⚠️ — click to expand

🔍 Patch Validation

PR: #719 (USB changes for Shikra platforms)
Upstream commits:

Commit 1: https://lore.kernel.org/all/20260512-shikra-dt-v1-2-716438330dd0@oss.qualcomm.com/

Commit 2: N/A (PENDING)

Commit 3: https://lore.kernel.org/all/20260519-shikra-dt-v2-5-c01b90fb4395@oss.qualcomm.com/#r

Verdict: ⚠️ PARTIAL

Commit 1: FROMLIST: arm64: dts: qcom: Add USB changes for Shikra

Commit Message

Check Status Note

Subject matches upstream ⚠️ Cannot verify - lore link inaccessible

Body preserves rationale ✅ Clear description of USB controller, PHYs, and regulators

Fixes tag present/correct N/A Not a fix commit

Authorship preserved ✅ Krishna Kurapati krishna.kurapati@oss.qualcomm.com

Backport note (if applicable) N/A FROMLIST prefix indicates pending upstream

Diff

File Status Notes

arch/arm64/boot/dts/qcom/shikra-cqm-evk.dts ⚠️ Cannot verify against upstream - adds USB nodes with regulators

arch/arm64/boot/dts/qcom/shikra-cqs-evk.dts ⚠️ Cannot verify against upstream - adds USB nodes with regulators

arch/arm64/boot/dts/qcom/shikra.dtsi ⚠️ Cannot verify against upstream - adds usb_1_hsphy, usb_qmpphy, usb_1 nodes

Issues

Lore link is inaccessible (returns HTTP error) - cannot verify diff faithfulness

Link format appears correct but patch content cannot be compared

Commit message body is well-structured with clear enumeration (a, b, c)

All device tree additions follow standard DT binding patterns

Commit 2: PENDING: arm64: dts: qcom: Add typec role switching changes to shikra

Commit Message

Check Status Note

Subject matches upstream N/A PENDING prefix - not yet posted upstream

Body preserves rationale ⚠️ Very brief - only states "Add typec role switching changes"

Fixes tag present/correct N/A Not a fix commit

Authorship preserved ✅ Krishna Kurapati krishna.kurapati@oss.qualcomm.com

Backport note (if applicable) N/A PENDING indicates work-in-progress

Diff

File Status Notes

arch/arm64/boot/dts/qcom/shikra-cqm-evk.dts ✅ Adds typec port endpoints, changes dr_mode to "otg"

arch/arm64/boot/dts/qcom/shikra-cqm-som.dtsi ✅ Adds pm4125_typec connector with dual role support

arch/arm64/boot/dts/qcom/shikra-cqs-evk.dts ✅ Adds typec port endpoints, changes dr_mode to "otg"

Issues

Commit message is too brief - should explain what typec role switching enables and why it's needed

No lore link provided (expected for PENDING status)

Changes are logically consistent: adds USB-C connector node, links endpoints, enables OTG mode

PENDING prefix correctly indicates this is not yet upstream

Commit 3: FROMLIST: arm64: dts: qcom: Add changes for usb on IQS platform

Commit Message

Check Status Note

Subject matches upstream ⚠️ Cannot verify - lore link inaccessible

Body preserves rationale ✅ Clear enumeration: regulators and OTG mode

Fixes tag present/correct N/A Not a fix commit

Authorship preserved ✅ Krishna Kurapati krishna.kurapati@oss.qualcomm.com

Backport note (if applicable) N/A FROMLIST prefix indicates pending upstream

Diff

File Status Notes

arch/arm64/boot/dts/qcom/shikra-iqs-evk.dts ⚠️ Cannot verify against upstream - adds USB nodes with pm8150 regulators

Issues

Lore link is inaccessible (returns HTTP error) - cannot verify diff faithfulness

Typo in commit message: "Regualtors" should be "Regulators"

Link has unusual #r fragment - may be malformed or pointing to a reply

Changes are consistent with commit 1 pattern but use different PMIC (pm8150 vs pm4125)

Overall Issues

Lore links inaccessible - Both FROMLIST commits reference lore.kernel.org URLs that return errors, preventing verification of diff faithfulness to upstream

Commit 2 message too brief - PENDING commit lacks sufficient rationale

Typo in commit 3 - "Regualtors" → "Regulators"

Link format concern - Commit 3 link ends with #r which may indicate a reply rather than the original patch

Verdict

Cannot fully validate - Lore links are inaccessible, preventing verification that PR diffs match upstream patches. Commit messages follow kernel conventions (FROMLIST/PENDING prefixes, Signed-off-by present), but commit 2 needs more detailed rationale and commit 3 has a typo. Changes appear internally consistent and follow device tree binding patterns.

Recommendation:

Fix typo in commit 3 message ("Regualtors" → "Regulators")

Expand commit 2 message to explain what typec role switching enables

Verify lore links are correct and accessible before merge

If lore patches are not yet posted, consider changing FROMLIST to PENDING

Final Summary

Lore link present:

Commit 1: Yes - https://lore.kernel.org/all/20260512-shikra-dt-v1-2-716438330dd0@oss.qualcomm.com/

Commit 2: No - PENDING prefix; no lore link expected or required

Commit 3: Yes - https://lore.kernel.org/all/20260519-shikra-dt-v2-5-c01b90fb4395@oss.qualcomm.com/#r

Lore link matches PR commits:

Commit 1: Cannot verify - lore link inaccessible (HTTP error)

Commit 2: N/A - no lore link to compare against

Commit 3: Cannot verify - lore link inaccessible (HTTP error)

Upstream patch status:

Commit 1: Unknown - FROMLIST indicates posted but not merged; cannot verify due to inaccessible link

Commit 2: Not upstream - PENDING prefix indicates work-in-progress, not yet posted

Commit 3: Unknown - FROMLIST indicates posted but not merged; cannot verify due to inaccessible link

PR present in qcom-next:

Not checked - no kernel source tree available in current environment per constraints

qlijarvis · 2026-06-16T06:35:00Z

PR #719 — checker-log-analyzer

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

Checker	Result	Summary
Checker	Result	Summary
checkpatch	✅	All commits pass checkpatch with no errors or warnings
dt-binding-check	⏭️	Skipped - no changes in Documentation/devicetree/bindings
dtb-check	❌	Pre-existing video-codec iommus schema validation errors
sparse-check	⏭️	Skipped - no C code changes
check-uapi-headers	⏭️	Skipped - no UAPI header changes
check-patch-compliance	❌	Author mismatch and PENDING prefix issues
tag-check	N/A	Not applicable for this branch
qcom-next-check	✅	FROMLIST commits present with valid lore links

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #719 - Add USB changes for Shikra
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/27597614581

Checker Result Summary

checkpatch ✅ All commits pass checkpatch with no errors or warnings

dt-binding-check ⏭️ Skipped - no changes in Documentation/devicetree/bindings

dtb-check ❌ Pre-existing video-codec iommus schema validation errors

sparse-check ⏭️ Skipped - no C code changes

check-uapi-headers ⏭️ Skipped - no UAPI header changes

check-patch-compliance ❌ Author mismatch and PENDING prefix issues

tag-check N/A Not applicable for this branch

qcom-next-check ✅ FROMLIST commits present with valid lore links

❌ dtb-check

Root cause: Pre-existing schema validation error in video-codec@5a00000 node (unrelated to this PR's USB changes)

Failure details:
video-codec@5a00000 (qcom,shikra-iris): iommus: [[41, 1920, 32]] is too short
video-codec@5a00000 (qcom,shikra-iris): iommus: [[40, 1920, 32]] is too short
The dtb-check compares errors between base (360986b) and head (373862f). These errors appear in all shikra DTBs (cqm-evk, cqs-evk, iqs-evk and their camera variants), indicating this is a pre-existing issue with the video-codec node's iommus property, not introduced by the USB changes in this PR.

Fix: This is a false positive blocker for this PR. The USB changes do not touch the video-codec node. The iommus property in the video-codec node needs additional cells according to the schema, but this should be fixed in a separate patch addressing the video subsystem, not in this USB-focused PR.

Reproduce locally:
make ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- O=out defconfig
make ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- O=out CHECK_DTBS=y qcom/shikra-cqm-evk.dtb
❌ check-patch-compliance

Root cause: Author mismatch between lore upstream patches and PR commits

Failure details:

Commit 1/3: FROMLIST: arm64: dts: qcom: Add USB changes for Shikra
Change is different from the one mentioned in Link
Author mismatch:
  Original author: Komal Bajaj <komal.bajaj@oss.qualcomm.com>
  Commit author : Krishna Kurapati <krishna.kurapati@oss.qualcomm.com>
Link: https://lore.kernel.org/all/20260512-shikra-dt-v1-2-716438330dd0@oss.qualcomm.com/

Commit 2/3: PENDING: arm64: dts: qcom: Add typec role switching changes to shikra
Commit summary does not start with a required prefix
This commit uses PENDING: prefix which is valid for internal/downstream work not yet submitted upstream.

Commit 3/3: FROMLIST: arm64: dts: qcom: Add changes for usb on IQS platform
Change is different from the one mentioned in Link
Author mismatch:
  Original author: Komal Bajaj <komal.bajaj@oss.qualcomm.com>
  Commit author : Krishna Kurapati <krishna.kurapati@oss.qualcomm.com>
Link: https://lore.kernel.org/all/20260519-shikra-dt-v2-5-c01b90fb4395@oss.qualcomm.com/#r

Fix:

For commits 1 and 3 (FROMLIST patches with author mismatch):

If Krishna is taking over these patches from Komal, add From: Komal Bajaj <komal.bajaj@oss.qualcomm.com> as the first line of the commit message body to preserve original authorship

Keep Krishna's Signed-off-by to indicate he handled the integration

Alternatively, if the content differs significantly from upstream, consider whether these should be marked as BACKPORT: or PENDING: instead

For commit 2 (PENDING prefix):

The PENDING: prefix is acceptable for work not yet upstream. If the checker rejects it, this may be a checker configuration issue. Verify that PENDING: is in the allowed prefix list for the target branch.

Reproduce locally:
cd kernel-checkers
bash check-patch-compliance.sh --kernel-src /path/to/kernel --base 360986b713f8 --head 373862f6d962
Verdict

2 blockers to fix:

dtb-check failure - This is a pre-existing issue unrelated to USB changes. The video-codec iommus schema error exists in the base tree. Recommend requesting a waiver or fixing the video-codec node separately.

check-patch-compliance failure - Author mismatch on FROMLIST commits. Add proper From: tags to preserve original authorship, or re-evaluate whether these should use different prefixes (BACKPORT/PENDING) if content differs from upstream.

The actual USB device tree changes are clean and pass checkpatch. The dtb-check failure is a false positive for this PR's scope.

qcomlnxci · 2026-06-16T14:56:33Z

Test jobs on 373862f

qcomlnxci · 2026-06-16T14:56:36Z

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	◻️

ppratap-liveroot · 2026-06-17T05:05:19Z

approved

Kriskura176767 · 2026-06-17T08:56:22Z

Jira for exception : https://jira-dc.qualcomm.com/jira/browse/QLIJIRA-136

qcomlnxci · 2026-06-18T07:05:14Z

Test jobs on 93b1810

qcomlnxci · 2026-06-18T07:05:20Z

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	◻️

Add usb related changes on Shikra specifically: a) Primary controller node b) Primary high speed phy c) QMP Phy for super speed operation Enable USB controller and phys in device mode on CQS and CQM variants. Add the regulators for the phys accordingly. Link: https://lore.kernel.org/all/20260512-shikra-dt-v1-2-716438330dd0@oss.qualcomm.com/ Signed-off-by: Komal Bajaj <komal.bajaj@oss.qualcomm.com> Signed-off-by: Krishna Kurapati <krishna.kurapati@oss.qualcomm.com>

Add typec role switching changes to shikra retail platforms. Signed-off-by: Rakesh Kota <rakesh.kota@oss.qualcomm.com> Signed-off-by: Krishna Kurapati <krishna.kurapati@oss.qualcomm.com>

Add USB changes on IQS Platform: 1. Regualtors for HS and SS Phys 2. OTG mode for forcing role switching for host mode validations Link: https://lore.kernel.org/all/20260519-shikra-dt-v2-5-c01b90fb4395@oss.qualcomm.com/#r Signed-off-by: Komal Bajaj <komal.bajaj@oss.qualcomm.com> Signed-off-by: Krishna Kurapati <krishna.kurapati@oss.qualcomm.com>

Kriskura176767 requested review from a team, aiquny, idlethread and ndechesne June 15, 2026 16:33

Kriskura176767 force-pushed the usbpatches branch from 4561642 to 426f559 Compare June 15, 2026 16:35

Kriskura176767 force-pushed the usbpatches branch from 426f559 to 113cbd4 Compare June 15, 2026 17:58

Kriskura176767 force-pushed the usbpatches branch from 113cbd4 to 528420d Compare June 16, 2026 01:18

sgaud-quic added this to the qli-2.0 GA pull-request freeze milestone Jun 16, 2026

Kriskura176767 force-pushed the usbpatches branch from 528420d to 373862f Compare June 16, 2026 06:01

naala-qcom mentioned this pull request Jun 16, 2026

Add Shikra (QCM2390) display support for CQS and CQM targets #679

Open

akakum-qualcomm approved these changes Jun 16, 2026

View reviewed changes

ppratap-liveroot approved these changes Jun 17, 2026

View reviewed changes

Komal-Bajaj reviewed Jun 17, 2026

View reviewed changes

Comment thread arch/arm64/boot/dts/qcom/shikra-cqm-evk.dts

Komal-Bajaj previously approved these changes Jun 17, 2026

View reviewed changes

Kriskura176767 dismissed Komal-Bajaj’s stale review via 93b1810 June 18, 2026 05:45

Kriskura176767 force-pushed the usbpatches branch from 373862f to 93b1810 Compare June 18, 2026 05:45

qcomlnxci requested a review from a team June 18, 2026 05:46

vvreddy-qualcomm approved these changes Jun 18, 2026

View reviewed changes

Komal-Bajaj previously approved these changes Jun 18, 2026

View reviewed changes

Komal-Bajaj and others added 3 commits June 18, 2026 13:50

PENDING: arm64: dts: qcom: Add typec role switching changes to shikra

06240e4

Add typec role switching changes to shikra retail platforms. Signed-off-by: Rakesh Kota <rakesh.kota@oss.qualcomm.com> Signed-off-by: Krishna Kurapati <krishna.kurapati@oss.qualcomm.com>

Kriskura176767 dismissed Komal-Bajaj’s stale review via 64001c8 June 18, 2026 08:21

Kriskura176767 force-pushed the usbpatches branch from 93b1810 to 64001c8 Compare June 18, 2026 08:21

qcomlnxci requested a review from a team June 18, 2026 08:23

Conversation

Kriskura176767 commented Jun 15, 2026 • edited by Komal-Bajaj Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

qswat-orbit-external Bot commented Jun 15, 2026

Uh oh!

qswat-orbit-external Bot commented Jun 15, 2026

Uh oh!

psarma-qcom commented Jun 15, 2026

Uh oh!

qlijarvis commented Jun 15, 2026

PR #719 — validate-patch

Final Summary

🔍 Patch Validation

Commit 1/2: FROLIST: arm64: dts: qcom: Add USB changes for Shikra

Commit Message

Diff

Issues

Commit 2/2: PENDING: arm64: dts: qcom: Add typec role switching changes to shikra

Commit Message

Diff

Issues

Overall Verdict

What needs fixing:

Final Summary

Uh oh!

qlijarvis commented Jun 15, 2026

PR #719 — checker-log-analyzer

🤖 CI Checker Analysis (checker-log-analyzer)

❌ check-patch-compliance

❌ dtb-check

Verdict

Uh oh!

qswat-orbit-external Bot commented Jun 15, 2026

Uh oh!

qlijarvis commented Jun 15, 2026

PR #719 — validate-patch

Final Summary

🔍 Patch Validation

Commit 1/2: FROLIST: arm64: dts: qcom: Add USB changes for Shikra

Commit Message

Diff

Commit 2/2: PENDING: arm64: dts: qcom: Add typec role switching changes to shikra

Commit Message

Diff

Issues

Verdict

Final Summary

Uh oh!

qlijarvis commented Jun 15, 2026

PR #719 — checker-log-analyzer

🤖 CI Checker Analysis (checker-log-analyzer)

❌ dtb-check

❌ check-patch-compliance

Verdict

Uh oh!

qswat-orbit-external Bot commented Jun 16, 2026

Uh oh!

qlijarvis commented Jun 16, 2026

PR #719 — validate-patch

Final Summary

🔍 Patch Validation

Commit 1/2: FROMLIST: arm64: dts: qcom: Add USB changes for Shikra

Commit Message

Diff

Issues

Commit 2/2: PENDING: arm64: dts: qcom: Add typec role switching changes to shikra

Commit Message

Diff

Issues

Overall Issues

Verdict

Final Summary

Uh oh!

qlijarvis commented Jun 16, 2026

PR #719 — checker-log-analyzer

🤖 CI Checker Analysis (checker-log-analyzer)

❌ dtb-check

❌ check-patch-compliance

Verdict

Kriskura176767 commented Jun 15, 2026 •

edited by Komal-Bajaj

Loading