QCLINUX: arm64: dts: qcom: Enable og0va1b camera sensor on glymur crd

[Vishal Verma (vishverm-qli)]

Enable camera sensors og0va1b on the Glymur CRD platform.

Adds required DT updates to support sensor bring-up and probe on Glymur crd board.

CRs-Fixed: 4590425

[qlijarvis]

🔨 Build Failure Analysis — PR #1482

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

#	Error	File:Line	PR-introduced?	Root Cause
N/A	Merge conflict during integration	Multiple files (110 conflicts)	No	Pre-existing integration conflicts with baseline branch

Verdict

This is not a compilation failure. The build failed during the merge/integration phase before compilation could begin. The PR introduces changes to arch/arm64/boot/dts/qcom/glymur-camera-sensor.dtsi which is a device tree file. The CI workflow attempts to merge the PR branch (tech/overlay/dt) into an integration branch based on tag 19b282f417584cfe14ce6a262122c51553d026ec, resulting in 110 merge conflicts across various files. These conflicts are pre-existing integration issues between the PR's base branch and the integration baseline, not errors introduced by the PR's changes themselves.

📎 Detailed analysis: Full report

[qlijarvis]

🔨 Build Failure Analysis — PR #1482

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

#	Error	File:Line	PR-introduced?	Root Cause
N/A	Merge conflict during automerge	Multiple files (110 conflicts)	No	Branch integration failure - not a compilation error

Verdict

This is not a compilation failure. The build failed during the automerge/integration phase when attempting to merge the tech/overlay/dt branch with the qcom-next baseline. The PR modifies only arch/arm64/boot/dts/qcom/glymur-camera-sensor.dtsi, which is not among the 110 conflicted files. All conflicts are pre-existing branch-level integration issues unrelated to this PR's changes.

📎 Detailed analysis: Full report

[qlijarvis]

PR #1482 — validate-patch

PR: #1482

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: No — file glymur-camera-sensor.dtsi does not exist in qcom-next branch

Verdict: ✅ — click to expand

🔍 Patch Validation

PR: #1482 - QCLINUX: arm64: dts: qcom: Enable og0va1b camera sensor on glymur crd
Upstream commit: N/A (vendor-only commit)
Verdict: ✅ PASS (vendor-only commit; validation not applicable)

Commit Message

Check	Status	Note
Subject matches upstream	N/A	QCLINUX: prefix indicates vendor-only commit
Body preserves rationale	✅	Clear description of camera sensor enablement
Fixes tag present/correct	N/A	Not a fix; new feature addition
Authorship preserved	✅	Signed-off-by present
Backport note (if applicable)	N/A	Not a backport

Diff

File	Status	Notes
arch/arm64/boot/dts/qcom/glymur-camera-sensor.dtsi	✅	Adds og0va1b camera sensor node and updates pinctrl configuration

Issues

None. This is a vendor-only commit with QCLINUX: prefix, which by design has no upstream lore link and is not intended for upstream submission.

Verdict

This is a vendor-only device tree change for Qualcomm's Glymur CRD platform. The commit adds support for the og0va1b camera sensor with appropriate device tree bindings, power supplies, GPIO configuration, and clock settings. The change is self-contained and follows standard device tree conventions. No upstream validation is applicable or required for QCLINUX: prefixed commits.

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: No — file glymur-camera-sensor.dtsi does not exist in qcom-next branch

[qlijarvis]

PR #1482 — checker-log-analyzer

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

Checker	Result	Summary
Checker	Result	Summary
checkpatch	⚠️	CI infrastructure failure - merge failed
dt-binding-check	⚠️	CI infrastructure failure - merge failed
dtb-check	⚠️	CI infrastructure failure - merge failed
sparse-check	⚠️	CI infrastructure failure - merge failed
check-uapi-headers	⚠️	CI infrastructure failure - merge failed
check-patch-compliance	⚠️	CI infrastructure failure - merge failed
tag-check	✅	PASS - QCLINUX: prefix present

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #1482 - QCLINUX: arm64: dts: qcom: Enable og0va1b camera sensor on glymur crd
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/28858226660
Target branch: tech/overlay/dt

Checker	Result	Summary
checkpatch	⚠️	CI infrastructure failure - merge failed
dt-binding-check	⚠️	CI infrastructure failure - merge failed
dtb-check	⚠️	CI infrastructure failure - merge failed
sparse-check	⚠️	CI infrastructure failure - merge failed
check-uapi-headers	⚠️	CI infrastructure failure - merge failed
check-patch-compliance	⚠️	CI infrastructure failure - merge failed
tag-check	✅	PASS - QCLINUX: prefix present

---

⚠️ CI Infrastructure Failure

Root cause: All checker jobs failed during the automerge step with "fatal: refusing to merge unrelated histories" when attempting to merge the PR branch with the integration baseline.

Failure details:

2026-07-07T10:24:43.5157766Z fatal: refusing to merge unrelated histories
2026-07-07T10:24:43.6264750Z Merge failed, manual merge
...
2026-07-07T10:25:04.6779346Z fatal: refusing to merge unrelated histories
2026-07-07T10:25:04.7900495Z Merge failed or conflicts detected. Aborting merge.
2026-07-07T10:25:04.7920531Z fatal: There is no merge to abort (MERGE_HEAD missing).
2026-07-07T10:25:04.7940273Z ##[error]Process completed with exit code 3.

This error occurred in all six checker jobs (checkpatch, dt-binding-check, dtb-check, sparse-check, check-uapi-headers, check-patch-compliance), indicating a systematic CI infrastructure issue rather than a patch quality problem.

Analysis:

The CI workflow attempts to:

1. Create an integration branch based on baseline tag 19b282f417584cfe14ce6a262122c51553d026ec
2. Merge topic branch topic/tech/overlay/dt
3. Merge PR QCLINUX: arm64: dts: qcom: Enable og0va1b camera sensor on glymur crd #1482

The failure occurs because the PR branch (tech/overlay/dt) and the baseline integration branch have completely unrelated Git histories. This is a known Git limitation when branches don't share a common ancestor.

This is NOT a patch defect. The patch itself appears clean:

• ✅ Has required QCLINUX: prefix (appropriate for vendor-only DTS changes)
• ✅ Has Signed-off-by: trailer
• ✅ No trailing whitespace detected
• ✅ No long lines detected
• ✅ DTS-only change (no C/H files modified)

Fix: Re-trigger the CI workflow. If the issue persists, the CI configuration needs to be updated to handle the tech/overlay/dt branch merge strategy, possibly by:

• Adding --allow-unrelated-histories flag to the merge command for this specific branch
• Adjusting the baseline selection logic
• Reviewing the automerge configuration for the tech/overlay/dt topic branch

Reproduce locally:
This is a CI-specific issue. To validate the patch quality locally without the automerge step:

# Clone the PR branch
git fetch origin pull/1482/head:pr-1482
git checkout pr-1482

# Run checkpatch on the commit
./scripts/checkpatch.pl --strict --ignore FILE_PATH_CHANGES -g HEAD

# Since this is DTS-only, dt-binding-check and dtb-check would be relevant:
# (requires kernel build environment)
make defconfig
make dtbs_check

---

✅ tag-check

Status: PASS

The commit subject starts with QCLINUX:, which is a valid prefix for vendor-only changes. Since the target branch is tech/overlay/dt (not qcom-next or qcom-next-staging), the subject prefix requirement applies and is satisfied.

Note: While QCLINUX: is a valid prefix for the tag-check, it is not accepted by the check-patch-compliance checker (which only accepts FROMLIST:, FROMGIT:, UPSTREAM:, BACKPORT:). This is a known limitation for vendor-only commits that have no upstream equivalent. However, since check-patch-compliance did not run due to the CI infrastructure failure, we cannot confirm whether it would have flagged this.

---

Verdict

Cannot assess patch quality - all checkers failed due to CI infrastructure issue (unrelated Git histories during automerge).

Recommended action:

1. Re-trigger the CI workflow to attempt the checks again
2. If the issue persists, escalate to the CI/CD team to fix the automerge configuration for the tech/overlay/dt branch
3. The patch itself shows no obvious quality issues in manual inspection and should pass checkers once the CI infrastructure issue is resolved

Patch quality assessment (manual inspection):

• ✅ Proper commit message format
• ✅ Valid QCLINUX: prefix for vendor-only DTS change
• ✅ Signed-off-by: present
• ✅ DTS-only change (camera sensor enablement)
• ✅ No obvious formatting issues