QCLINUX: Revert Hamoa and Purwa BT always-on workarounds

[weiden (WeiDeng-weiden)]

Revert the temporary BT_EN always-on workaround for both Hamoa and Purwa IoT EVKs, now superseded by the proper M.2 Key E connector DT solution.

Commits:

1. QCLINUX: Revert "WORKAROUND: arm64: dts: qcom: hamoa-iot-evk: support Bluetooth over both USB and UART" — reverts f2ee870
2. QCLINUX: Revert "WORKAROUND: arm64: dts: qcom: purwa-iot-evk: support Bluetooth over both USB and UART" — reverts 3aff695

The workarounds modeled BT_EN (GPIO116) as always-on fixed regulators to prevent hci_qca UART driver interference when BT operates over USB. This is no longer needed with the proper M.2 solution that uses pwrseq-pcie-m2 to control W_DISABLE2# (GPIO116) based on PCIe device enumeration.

M.2 solution PRs:

• arm64: dts: qcom: hamoa, purwa: Describe the PCIe M.2 Key E connector #1629
• power: sequencing: pcie-m2: Hamoa M.2 BT USB/UART coexistence support #1628

CRs-Fixed: 4630764

[qlijarvis]

🔨 Build Failure Analysis — PR #1627

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

#	Error	File:Line	PR-introduced?	Root Cause
1	Merge conflict during automerge	arch/arm64/boot/dts/qcom/qcs8300-ride.dts	No	Pre-existing conflict between PR changes to hamoa-iot-evk.dts and topic branch topic/tech/all/workaround modifications to qcs8300-ride.dts
2	Merge conflict during automerge	drivers/bluetooth/hci_qca.c	No	Pre-existing conflict between PR changes to hamoa-iot-evk.dts and topic branch topic/tech/all/workaround modifications to hci_qca.c

Verdict

This is not a compilation failure. The build failed during the automerge (integration) step when attempting to merge the PR with topic branch topic/tech/all/workaround. Both conflicts are in files NOT modified by this PR and are pre-existing integration issues between the topic branch and the baseline.

📎 Detailed analysis: Full report

[qlijarvis]

🔨 Build Failure Analysis — PR #1627

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

#	Error	File:Line	PR-introduced?	Root Cause
1	Merge conflict during automerge	arch/arm64/boot/dts/qcom/qcs8300-ride.dts	Indirect	PR reverts Bluetooth workaround in hamoa-iot-evk.dts; conflicts with parallel changes in qcs8300-ride.dts when merging topic/tech/all/workaround branch
2	Merge conflict during automerge	drivers/bluetooth/hci_qca.c	Indirect	PR changes Bluetooth configuration in hamoa-iot-evk.dts; conflicts with parallel driver changes in hci_qca.c when merging topic/tech/all/workaround branch

Verdict

This is not a compilation failure. The build failed during the automerge phase when integrating the topic/tech/all/workaround branch with the baseline. The PR itself is syntactically valid but creates merge conflicts with other concurrent changes in the integration branch. The conflicts are indirectly related to the PR's Bluetooth workaround revert.

📎 Detailed analysis: Full report

[qlijarvis]

PR #1627 — validate-patch

PR: #1627

Verdict	Issues	Detailed Report
✅	0	Full report

Final Summary

1. Lore link present: No — QCLINUX: prefix; no lore link expected or required
2. Lore link matches PR commits: N/A — no lore link to compare against
3. Upstream patch status: N/A — vendor-only change, not posted upstream
4. PR present in qcom-next/topics: Yes - all 1 commit(s) are present in qcom-next or topics

Verdict: ✅ — click to expand

🔍 Patch Validation

PR: #1627 - QCLINUX: Revert "WORKAROUND: arm64: dts: qcom: hamoa-iot-evk: support Bluetooth over both USB and UART"
Upstream commit: N/A (vendor-only revert)
Verdict: ✅ PASS

Commit Message

Check	Status	Note
Subject matches upstream	N/A	Vendor-only commit; no upstream to compare
Body preserves rationale	✅	Clear explanation: workaround superseded by proper M.2 Key E connector DT solution
Fixes tag present/correct	N/A	Revert commit; references reverted commit f2ee870
Authorship preserved	✅	Wei Deng authorship and Signed-off-by present
Backport note (if applicable)	N/A	Not a backport

Diff

File	Status	Notes
arch/arm64/boot/dts/qcom/hamoa-iot-evk.dts	✅	Removes vreg_wcn_bt_en regulator, moves bt-enable-gpios to wcn7850-bt node, restores proper PMU supply references

Verdict

Merge as-is. This is a well-formed vendor-only revert that removes a workaround in favor of a proper DT solution. The commit message clearly explains the rationale, and the diff correctly reverts the Bluetooth configuration changes.

Final Summary

1. Lore link present: No — QCLINUX: prefix; no lore link expected or required
2. Lore link matches PR commits: N/A — no lore link to compare against
3. Upstream patch status: N/A — vendor-only change, not posted upstream
4. PR present in qcom-next/topics: Yes — commit is present in topics (all checked added lines verified)

Deterministic Integration Presence

Integration Presence Report

This report is generated by Jarvis before validate-patch runs.
It is the authoritative source for whether PR changes are already present
in qcom-next or in the kernel topic branches.

Kernel repo: /local/mnt/workspace/sgaud/Qgenie/image_pipeline/kernel
qcom-next ref: 8d5dbc1b17adf8fe86a41adcda686785e73f5414
topics remote: topics -> https://github.com/qualcomm-linux/kernel-topics
topics fetch: fetched

Commit	Subject	qcom-next	topics	Final
1/1	[PATCH] QCLINUX: Revert "WORKAROUND: arm64: dts: qcom: hamoa-iot-evk:	partial - subject or partial tree evidence found, but full change was not verified	present - all checked added lines are present	present

Final Status

overall_status: PASS
present_commits: 1/1
partial_commits: 0/1
missing_commits: 0/1
topics_checked_for_commits: 1/1
final_summary: PR present in qcom-next/topics: Yes - all 1 commit(s) are present in qcom-next or topics

[qlijarvis]

PR #1627 — checker-log-analyzer

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

Checker	Result	Summary
Checker	Result	Summary
checkpatch	⏭️	Skipped - automerge failed
dt-binding-check	⏭️	Skipped - automerge failed
dtb-check	⏭️	Skipped - automerge failed
sparse-check	⏭️	Skipped - automerge failed
check-uapi-headers	⏭️	Skipped - automerge failed
check-patch-compliance	⏭️	Skipped - automerge failed
tag-check	⚠️	Subject prefix issue (see below)

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #1627 - QCLINUX: Revert "WORKAROUND: arm64: dts: qcom: hamoa-iot-evk: support Bluetooth over both USB and UART"
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/30790458291

Checker	Result	Summary
checkpatch	⏭️	Skipped - automerge failed
dt-binding-check	⏭️	Skipped - automerge failed
dtb-check	⏭️	Skipped - automerge failed
sparse-check	⏭️	Skipped - automerge failed
check-uapi-headers	⏭️	Skipped - automerge failed
check-patch-compliance	⏭️	Skipped - automerge failed
tag-check	⚠️	Subject prefix issue (see below)

---

⚠️ Critical Infrastructure Issue: Automerge Failure

Root cause: All checker jobs failed during the prerequisite automerge step before any actual checking could occur. The PR could not be merged with the integration baseline due to merge conflicts.

Failure details:

Auto-merging arch/arm64/boot/dts/qcom/qcs8300-ride.dts
CONFLICT (content): Merge conflict in arch/arm64/boot/dts/qcom/qcs8300-ride.dts
Auto-merging drivers/bluetooth/hci_qca.c
CONFLICT (content): Merge conflict in drivers/bluetooth/hci_qca.c
Automatic merge failed; fix conflicts and then commit the result.
Merge failed, manual merge
##[error]Process completed with exit code 1.

Analysis:
The kernel-checkers CI workflow performs an automerge of all topic branches (including this PR) into an integration baseline before running any checks. This PR introduces conflicts with:

1. arch/arm64/boot/dts/qcom/qcs8300-ride.dts
2. drivers/bluetooth/hci_qca.c

These conflicts prevent the integration from completing, which blocks all downstream checker jobs.

Why this happened:
This PR reverts a workaround commit (f2ee87014e91) that modified hamoa-iot-evk.dts. However, when merged with other topic branches in the integration baseline, changes in those branches conflict with this revert—specifically in unrelated files (qcs8300-ride.dts and hci_qca.c), suggesting that:

• Other topic branches have made overlapping changes to Bluetooth/DTS infrastructure
• The integration baseline has diverged significantly from the PR's base

Fix:
This is not a patch defect—the PR itself is syntactically valid. The issue is an integration conflict that must be resolved before checkers can run.

Recommended actions:

1. Rebase the PR onto the latest integration baseline to resolve conflicts:

   git fetch origin
   git rebase origin/<target-branch>
   # Resolve conflicts in qcs8300-ride.dts and hci_qca.c
   git rebase --continue
   git push --force-with-lease

2. Coordinate with topic branch owners: The conflicts in qcs8300-ride.dts and hci_qca.c suggest overlapping work in other topic branches. Check if:

   • tech/all/workaround has conflicting Bluetooth changes
   • Other DTS topic branches modified the same regions

3. Re-trigger CI after resolving conflicts to get actual checker results.

---

⚠️ tag-check — Subject Prefix Issue

Root cause: The commit subject uses QCLINUX: prefix, which is a vendor-internal tag.

Commit subject:

QCLINUX: Revert "WORKAROUND: arm64: dts: qcom: hamoa-iot-evk: support Bluetooth over both USB and UART"

Analysis:
The QCLINUX: prefix is used for vendor-only changes with no upstream equivalent. However, the check-patch-compliance checker (if it had run) would fail for this prefix because it only accepts upstream-linkable prefixes: FROMLIST:, FROMGIT:, UPSTREAM:, BACKPORT:.

Note: This is a known limitation of the checker—vendor-only commits with QCLINUX: or PENDING: prefixes will always fail check-patch-compliance. Since this is a revert of a vendor workaround, the QCLINUX: prefix is appropriate for the content, but the checker will flag it.

Additional observation:
The subject line also contains a nested prefix structure: QCLINUX: Revert "WORKAROUND: ...". Best practice for revert commits is to add a prefix before Revert, e.g.:

QCLINUX: Revert "WORKAROUND: arm64: dts: qcom: hamoa-iot-evk: ..."

This is already correctly formatted.

Verdict:
✅ Subject prefix is correct for a vendor-only revert.
⚠️ check-patch-compliance will fail when it runs (expected for QCLINUX: commits).

---

Verdict

Cannot assess patch quality — all checkers were blocked by automerge conflicts.

Immediate action required:

1. ✅ Resolve merge conflicts in qcs8300-ride.dts and hci_qca.c
2. ✅ Rebase onto latest integration baseline
3. ✅ Re-trigger CI to get actual checker results

Expected checker behavior after rebase:

• checkpatch: Likely ✅ PASS (simple revert, no style issues expected)
• dt-binding-check: ⏭️ SKIP (no binding changes)
• dtb-check: ⏭️ SKIP or ✅ PASS (DTS-only revert)
• sparse-check: ⏭️ SKIP (no C code changes)
• check-uapi-headers: ⏭️ SKIP (no UAPI changes)
• check-patch-compliance: ❌ FAIL (expected for QCLINUX: prefix—known limitation)

Note: The check-patch-compliance failure is not a blocker for vendor-only commits. The QCLINUX: prefix is appropriate for this revert.

[qlijarvis]

🔨 Build Failure Analysis — PR #1627

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

#	Error	File:Line	PR-introduced?	Root Cause
1	Merge conflict during automerge	arch/arm64/boot/dts/qcom/qcs8300-ride.dts	No	Conflict between PR revert and topic/tech/all/workaround branch changes; PR only modifies hamoa-iot-evk.dts
2	Merge conflict during automerge	drivers/bluetooth/hci_qca.c	No	Conflict between PR revert and topic/tech/all/workaround branch changes; PR does not touch this driver file

Verdict

No compilation errors found. Build failed during automerge phase with 2 merge conflicts in files not modified by this PR. These are integration conflicts, not PR-introduced errors.

📎 Detailed analysis: Full report

[qlijarvis]

🔨 Build Failure Analysis — PR #1627

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

#	Error	File:Line	PR-introduced?	Root Cause
1	Merge conflict during automerge	arch/arm64/boot/dts/qcom/qcs8300-ride.dts	Yes	PR reverts Bluetooth workaround in hamoa-iot-evk.dts; conflicts with similar workaround patterns in qcs8300-ride.dts from topic/tech/all/workaround branch
2	Merge conflict during automerge	drivers/bluetooth/hci_qca.c	Yes	PR changes Bluetooth configuration approach; conflicts with workaround code in hci_qca.c from topic/tech/all/workaround branch

Verdict

Both failures are PR-introduced merge conflicts. The PR reverts a Bluetooth workaround that conflicts with the broader workaround topic branch (topic/tech/all/workaround) during integration.

📎 Detailed analysis: Full report

[qlijarvis]

PR #1627 — validate-patch

PR: #1627

Verdict	Issues	Detailed Report
✅	0	Full report

Final Summary

1. Lore link present: No — QCLINUX: prefix; no lore link expected or required
2. Lore link matches PR commits: N/A — no lore link to compare against
3. Upstream patch status: N/A — vendor-only change, not posted upstream
4. PR present in qcom-next/topics: Yes - all 1 commit(s) are present in qcom-next or topics

Verdict: ✅ — click to expand

🔍 Patch Validation

PR: #1627 - QCLINUX: Revert "WORKAROUND: arm64: dts: qcom: hamoa-iot-evk: support Bluetooth over both USB and UART"
Upstream commit: N/A (vendor-only revert)
Verdict: ✅ PASS

Commit Message

Check	Status	Note
Subject matches upstream	N/A	Vendor-only commit; no upstream source
Body preserves rationale	✅	Clear explanation: workaround superseded by proper M.2 Key E connector DT solution
Fixes tag present/correct	N/A	Revert commit; no Fixes tag required
Authorship preserved	✅	Wei Deng correctly listed as author
Backport note (if applicable)	N/A	Not a backport

Diff

File	Status	Notes
arch/arm64/boot/dts/qcom/hamoa-iot-evk.dts	✅	Clean revert: removes workaround regulator, restores proper BT GPIO and PMU supplies

Verdict

Merge as-is. This is a well-documented vendor-only revert that removes a workaround in favor of a proper solution. The commit message clearly explains the rationale, and the diff cleanly removes the temporary workaround code.

Final Summary

1. Lore link present: No — QCLINUX: prefix; no lore link expected or required
2. Lore link matches PR commits: N/A — no lore link to compare against
3. Upstream patch status: N/A — vendor-only change, not posted upstream
4. PR present in qcom-next/topics: Yes — commit is present in topics branch (integration_presence_report.md: PASS, 1/1 commits present)

Deterministic Integration Presence

Integration Presence Report

This report is generated by Jarvis before validate-patch runs.
It is the authoritative source for whether PR changes are already present
in qcom-next or in the kernel topic branches.

Kernel repo: /local/mnt/workspace/sgaud/Qgenie/image_pipeline/kernel
qcom-next ref: 8d5dbc1b17adf8fe86a41adcda686785e73f5414
topics remote: topics -> https://github.com/qualcomm-linux/kernel-topics
topics fetch: fetched

Commit	Subject	qcom-next	topics	Final
1/1	[PATCH] QCLINUX: Revert "WORKAROUND: arm64: dts: qcom: hamoa-iot-evk:	partial - subject or partial tree evidence found, but full change was not verified	present - all checked added lines are present	present

Final Status

overall_status: PASS
present_commits: 1/1
partial_commits: 0/1
missing_commits: 0/1
topics_checked_for_commits: 1/1
final_summary: PR present in qcom-next/topics: Yes - all 1 commit(s) are present in qcom-next or topics

[qlijarvis]

PR #1627 — checker-log-analyzer

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

Checker	Result	Summary
Checker	Result	Summary
checkpatch	⏭️	Skipped - automerge failed
dt-binding-check	⏭️	Skipped - automerge failed
dtb-check	⏭️	Skipped - automerge failed
sparse-check	⏭️	Skipped - automerge failed
check-uapi-headers	⏭️	Skipped - automerge failed
check-patch-compliance	⏭️	Skipped - automerge failed
tag-check	✅	Subject has valid QCLINUX: prefix

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #1627 - QCLINUX: Revert "WORKAROUND: arm64: dts: qcom: hamoa-iot-evk: support Bluetooth over both USB and UART"
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/30794984780

Checker	Result	Summary
checkpatch	⏭️	Skipped - automerge failed
dt-binding-check	⏭️	Skipped - automerge failed
dtb-check	⏭️	Skipped - automerge failed
sparse-check	⏭️	Skipped - automerge failed
check-uapi-headers	⏭️	Skipped - automerge failed
check-patch-compliance	⏭️	Skipped - automerge failed
tag-check	✅	Subject has valid QCLINUX: prefix

---

⚠️ Infrastructure Failure — Automerge Conflicts

Root cause: All checker jobs failed during the automerge/integration setup phase before any actual checker tests could run. The CI workflow attempts to merge the PR into an integration branch that includes topic/tech/all/workaround, but merge conflicts prevent the integration from completing.

Failure details:

CONFLICT (content): Merge conflict in arch/arm64/boot/dts/qcom/qcs8300-ride.dts
CONFLICT (content): Merge conflict in drivers/bluetooth/hci_qca.c
Automatic merge failed; fix conflicts and then commit the result.
automerge returned non-zero; check logs for conflicts
##[error]Process completed with exit code 1.

Analysis:

This is not a patch quality issue — the PR itself (a revert of a workaround commit in hamoa-iot-evk.dts) is clean and well-formed. The failure occurs because:

1. The CI workflow runs automerge to create an integration branch based on baseline 8d5dbc1b17adf8fe86a41adcda686785e73f5414
2. It attempts to merge topic/tech/all/workaround into this integration branch
3. Merge conflicts arise in:
   • arch/arm64/boot/dts/qcom/qcs8300-ride.dts (unrelated to this PR)
   • drivers/bluetooth/hci_qca.c (unrelated to this PR)
4. The automerge fails, preventing all downstream checker jobs from running

Why this happened:

The PR targets the topic/tech/all/workaround branch and reverts commit f2ee87014e91 from that branch. However, when the CI tries to integrate this topic branch with other topic branches (as part of the standard integration workflow), conflicts occur in files that are not touched by this PR.

Fix:

This is an integration conflict, not a patch defect. The conflicts must be resolved in the integration workflow, not in the PR itself. Recommended actions:

1. Option A (Recommended): Resolve the integration conflicts in the affected files (qcs8300-ride.dts, hci_qca.c) at the integration branch level, then re-trigger CI.

2. Option B: If the PR is intended to be merged directly to topic/tech/all/workaround without integration testing, adjust the CI workflow to skip automerge for this PR.

3. Option C: Rebase the topic/tech/all/workaround branch to resolve conflicts with other topic branches, then re-trigger CI.

Reproduce locally:

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

# Fetch the baseline and topic branch
git fetch origin 8d5dbc1b17adf8fe86a41adcda686785e73f5414
git checkout -b integ 8d5dbc1b17adf8fe86a41adcda686785e73f5414

# Attempt the merge that CI is doing
git fetch origin tech/all/workaround
git merge origin/tech/all/workaround

# Conflicts will appear in qcs8300-ride.dts and hci_qca.c
# Resolve them, then:
git add arch/arm64/boot/dts/qcom/qcs8300-ride.dts drivers/bluetooth/hci_qca.c
git commit -m "Resolve integration conflicts"

---

✅ tag-check

Status: PASS

The commit subject starts with QCLINUX:, which is a valid prefix tag. While QCLINUX: is not accepted by the check-patch-compliance checker (which enforces upstream-linkable prefixes only), it is a valid prefix for vendor-only changes in the Qualcomm Linux kernel tree.

Note: The subject also includes Revert "WORKAROUND: ...", which correctly identifies this as a revert of a previous workaround commit. The QCLINUX: prefix applies to the revert action itself.

---

Verdict

No checker tests were executed. All checker jobs failed during the automerge/integration setup phase due to merge conflicts in files unrelated to this PR (qcs8300-ride.dts, hci_qca.c).

The PR patch itself is clean — it is a straightforward revert of a workaround commit with a properly formatted commit message and valid subject prefix.

Action required: Resolve the integration conflicts in the automerge workflow (not in this PR), then re-trigger CI to run the actual checker tests.

[qlijarvis]

🔨 Build Failure Analysis — PR #1627

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

#	Error	File:Line	PR-introduced?	Root Cause
1	Merge conflict during automerge	arch/arm64/boot/dts/qcom/qcs8300-ride.dts	No	Integration conflict with topic/tech/all/workaround branch - not a compilation error
2	Merge conflict during automerge	drivers/bluetooth/hci_qca.c	No	Integration conflict with topic/tech/all/workaround branch - not a compilation error

Verdict

No compilation errors exist. The build failed during the pre-compilation automerge phase due to 2 merge conflicts with the integration branch. These are integration conflicts, not errors introduced by the PR code itself.

📎 Detailed analysis: Full report

[qlijarvis]

🔨 Build Failure Analysis — PR #1627

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

#	Error	File:Line	PR-introduced?	Root Cause
1	Merge conflict during automerge	arch/arm64/boot/dts/qcom/qcs8300-ride.dts	No	Conflict between baseline integration and topic/tech/all/workaround branch; PR does not modify this file
2	Merge conflict during automerge	drivers/bluetooth/hci_qca.c	No	Conflict between baseline integration and topic/tech/all/workaround branch; PR does not modify this file

Verdict

0 of 2 errors are introduced by this PR; both are pre-existing integration conflicts. The PR only modifies hamoa-iot-evk.dts and purwa-iot-evk.dts, which merged cleanly. The failures occurred when the CI system attempted to merge the PR's target branch (topic/tech/all/workaround) with the baseline during the automerge integration step.

📎 Detailed analysis: Full report

[qlijarvis]

PR #1627 — validate-patch

PR: #1627

Verdict	Issues	Detailed Report
✅	0	Full report

Final Summary

1. Lore link present: No — QCLINUX: prefix; no lore link expected or required
2. Lore link matches PR commits: N/A — no lore link to compare against
3. Upstream patch status: N/A — vendor-only changes, not posted upstream
4. PR present in qcom-next/topics: Yes - all 2 commit(s) are present in qcom-next or topics

Verdict: ✅ — click to expand

🔍 Patch Validation

PR: #1627 - QCLINUX: Revert Bluetooth workarounds for hamoa-iot-evk and purwa-iot-evk
Upstream commit: N/A (vendor-only commits)
Verdict: ✅ PASS

Commit Message

Check	Status	Note
Subject matches upstream	N/A	QCLINUX: vendor-only commits
Body preserves rationale	✅	Clear explanation: superseded by proper M.2 Key E connector DT solution
Fixes tag present/correct	N/A	Revert commits; no Fixes tag required
Authorship preserved	✅	Consistent authorship by Wei Deng
Backport note (if applicable)	N/A	Not a backport

Diff

File	Status	Notes
arch/arm64/boot/dts/qcom/hamoa-iot-evk.dts	✅	Clean revert: removes vreg_wcn_bt_en regulator, restores bt-enable-gpios and proper PMU supplies
arch/arm64/boot/dts/qcom/purwa-iot-evk.dts	✅	Clean revert: identical pattern to hamoa-iot-evk changes

Verdict

Merge as-is. Both commits are clean reverts of workarounds, properly justified, and already present in qcom-next/topics.

Final Summary

1. Lore link present: No — QCLINUX: prefix; no lore link expected or required
2. Lore link matches PR commits: N/A — no lore link to compare against
3. Upstream patch status: N/A — vendor-only changes, not posted upstream
4. PR present in qcom-next/topics: Yes — all 2 commit(s) are present in qcom-next or topics (per integration_presence_report.md)

Deterministic Integration Presence

Integration Presence Report

This report is generated by Jarvis before validate-patch runs.
It is the authoritative source for whether PR changes are already present
in qcom-next or in the kernel topic branches.

Kernel repo: /local/mnt/workspace/sgaud/Qgenie/image_pipeline/kernel
qcom-next ref: 8d5dbc1b17adf8fe86a41adcda686785e73f5414
topics remote: topics -> https://github.com/qualcomm-linux/kernel-topics
topics fetch: fetched

Commit	Subject	qcom-next	topics	Final
1/2	[PATCH 1/2] QCLINUX: Revert "WORKAROUND: arm64: dts: qcom:	partial - subject or partial tree evidence found, but full change was not verified	present - all checked added lines are present	present
2/2	[PATCH 2/2] QCLINUX: Revert "WORKAROUND: arm64: dts: qcom:	partial - subject or partial tree evidence found, but full change was not verified	present - all checked added lines are present	present

Final Status

overall_status: PASS
present_commits: 2/2
partial_commits: 0/2
missing_commits: 0/2
topics_checked_for_commits: 2/2
final_summary: PR present in qcom-next/topics: Yes - all 2 commit(s) are present in qcom-next or topics

[qlijarvis]

PR #1627 — checker-log-analyzer

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

Checker	Result	Summary
Checker	Result	Summary
checkpatch	⏭️	Skipped - automerge conflict
dt-binding-check	⏭️	Skipped - automerge conflict
dtb-check	⏭️	Skipped - automerge conflict
sparse-check	⏭️	Skipped - automerge conflict
check-uapi-headers	⏭️	Skipped - automerge conflict
check-patch-compliance	⏭️	Skipped - automerge conflict
tag-check	✅	PASS - qcom-next branch (prefix check not required)
qcom-next-check	⚠️	QCLINUX: prefix used (vendor-only reverts)

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #1627 - Revert Bluetooth workarounds for hamoa/purwa-iot-evk
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/30975486864
Target branch: qcom-next

Checker	Result	Summary
checkpatch	⏭️	Skipped - automerge conflict
dt-binding-check	⏭️	Skipped - automerge conflict
dtb-check	⏭️	Skipped - automerge conflict
sparse-check	⏭️	Skipped - automerge conflict
check-uapi-headers	⏭️	Skipped - automerge conflict
check-patch-compliance	⏭️	Skipped - automerge conflict
tag-check	✅	PASS - qcom-next branch (prefix check not required)
qcom-next-check	⚠️	QCLINUX: prefix used (vendor-only reverts)

---

⚠️ Automerge Conflict (All Checkers)

Root cause: Merge conflicts during CI automerge prevented all checkers from running.

Failure details:

Automatic merge failed; fix conflicts and then commit the result.
Merge failed, manual merge

Merging:
arch/arm64/boot/dts/qcom/qcs8300-ride.dts
drivers/bluetooth/hci_qca.c

Normal merge conflict for 'arch/arm64/boot/dts/qcom/qcs8300-ride.dts':
  {local}: modified file
  {remote}: modified file
automerge returned non-zero; check logs for conflicts

Analysis:

The CI workflow performs an automerge of all topic branches before running checkers. This PR targets qcom-next and reverts two commits from topic/tech/all/workaround:

1. Commit 1: QCLINUX: Revert "WORKAROUND: arm64: dts: qcom: hamoa-iot-evk: support Bluetooth over both USB and UART"
2. Commit 2: QCLINUX: Revert "WORKAROUND: arm64: dts: qcom: purwa-iot-evk: support Bluetooth over both USB and UART"

During automerge, the CI encountered conflicts in:

• arch/arm64/boot/dts/qcom/qcs8300-ride.dts (unrelated to this PR's changes)
• drivers/bluetooth/hci_qca.c (unrelated to this PR's changes)

These conflicts are not caused by this PR — they are pre-existing integration conflicts between other topic branches in the qcom-next tree.

Impact: No checkers could run because the automerge step failed before reaching the checker execution phase.

Fix:

This is a CI/integration issue, not a patch defect. The PR itself is clean. The conflicts need to be resolved in the integration tree:

1. Option A (Recommended): Wait for the conflicting topic branches to be resolved in qcom-next, then re-trigger CI.
2. Option B: Manually resolve the conflicts in the integration tree:

   # Clone and set up the integration environment
   git clone https://github.com/qualcomm-linux/kernel.git
   cd kernel
   git checkout qcom-next
   
   # Run automerge manually
   # (requires kernel-config automerge tooling)
   
   # Resolve conflicts in qcs8300-ride.dts and hci_qca.c
   git mergetool
   git commit

3. Option C: Merge this PR directly into qcom-next without waiting for automerge CI (if the conflicts are in unrelated topic branches).

Reproduce locally:

# This requires the full kernel-config CI automerge setup
# See: https://github.com/qualcomm-linux/kernel-config

---

✅ tag-check — PASS

Analysis:

Both commits use the QCLINUX: prefix:

• QCLINUX: Revert "WORKAROUND: arm64: dts: qcom: hamoa-iot-evk: ..."
• QCLINUX: Revert "WORKAROUND: arm64: dts: qcom: purwa-iot-evk: ..."

Since this PR targets qcom-next, the subject-prefix check (Step 2.7 of the skill) is not required. The tag-check passes by default for qcom-next and qcom-next-staging branches.

Note: The QCLINUX: prefix indicates these are vendor-only changes with no upstream equivalent. These are revert commits removing workarounds that have been superseded by a proper M.2 Key E connector DT solution.

---

Verdict

Cannot assess patch quality — all checkers were blocked by automerge conflicts in unrelated files (qcs8300-ride.dts, hci_qca.c).

Recommendation:

1. The PR patches themselves appear clean based on manual inspection:

   • Both commits are properly formatted revert commits
   • Commit messages explain the rationale (superseded by proper M.2 Key E connector DT solution)
   • Changes are limited to hamoa-iot-evk.dts and purwa-iot-evk.dts
   • Signed-off-by trailers are present

2. Action required: Resolve the automerge conflicts in the qcom-next integration tree (conflicts in qcs8300-ride.dts and hci_qca.c from other topic branches), then re-trigger CI.

3. Alternative: If the conflicts are in unrelated topic branches and this PR is urgent, consider merging directly into qcom-next after manual review, bypassing the automerge CI requirement.