arm64: defconfig: Enable CAMSS OPE driver

[Nihal Kumar Gupta (nihal231998)]

Add CONFIG_VIDEO_QCOM_CAMSS_OPE=m to enable the Offline Processing Engine driver for Agatti and Shikra platform.

[qlijarvis]

PR #1688 — validate-patch

PR: #1688

Verdict	Issues	Detailed Report
✅	0	Full report

Final Summary

1. Lore link present: No — PENDING: prefix; no lore link expected or required
2. Lore link matches PR commits: N/A — no lore link to compare against
3. Upstream patch status: N/A — vendor work-in-progress, 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: #1688 - PENDING: arm64: defconfig: Enable CAMSS OPE driver
Upstream commit: N/A (PENDING: prefix - work-in-progress, not yet posted upstream)
Verdict: ✅ PASS

Commit Message

Check	Status	Note
Subject matches upstream	N/A	PENDING: prefix - no upstream source to compare
Body preserves rationale	✅	Clear description of change (enable OPE driver for Agatti/Shikra)
Fixes tag present/correct	N/A	Not a fix commit
Authorship preserved	✅	Proper author and Signed-off-by present
Backport note (if applicable)	N/A	Not a backport

Diff

File	Status	Notes
arch/arm64/configs/defconfig	✅	Single line addition of CONFIG_VIDEO_QCOM_CAMSS_OPE=m in correct alphabetical position

Verdict

Merge as-is. This is a vendor work-in-progress commit that correctly adds the CAMSS OPE driver config option to defconfig. The change is minimal, well-placed alphabetically, and properly documented with the PENDING: prefix indicating it's not yet posted upstream.

Final Summary

1. Lore link present: No — PENDING: prefix; no lore link expected or required
2. Lore link matches PR commits: N/A — no lore link to compare against
3. Upstream patch status: N/A — vendor work-in-progress, not posted upstream
4. PR present in qcom-next/topics: Yes — commit present in topics (1/1 commits present 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: 49dbe0dae5cfb7a1eb3434cde6fc7ba37924fe94
topics remote: topics -> https://github.com/qualcomm-linux/kernel-topics
topics fetch: fetched

Commit	Subject	qcom-next	topics	Final
1/1	[PATCH] PENDING: arm64: defconfig: Enable CAMSS OPE driver	missing - no subject, patch-id, or full tree-content match found	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 #1688 — checker-log-analyzer

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

Checker	Result	Summary
Checker	Result	Summary
checkpatch	✅	0 errors, 0 warnings, 0 checks
dt-binding-check	⏭️	No binding changes
dtb-check	⏭️	No devicetree changes
sparse-check	⏭️	No C/H file changes
check-uapi-headers	⏭️	No UAPI changes
check-patch-compliance	❌	PENDING: prefix not in allowed list
tag-check	✅	PENDING: is a valid subject prefix

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #1688 - PENDING: arm64: defconfig: Enable CAMSS OPE driver
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/31681735064
Target branch: tech/all/config

Checker	Result	Summary
checkpatch	✅	0 errors, 0 warnings, 0 checks
dt-binding-check	⏭️	No binding changes
dtb-check	⏭️	No devicetree changes
sparse-check	⏭️	No C/H file changes
check-uapi-headers	⏭️	No UAPI changes
check-patch-compliance	❌	PENDING: prefix not in allowed list
tag-check	✅	PENDING: is a valid subject prefix

---

❌ check-patch-compliance

Root cause: The commit uses the PENDING: prefix, which is not in the checker's allowed prefix list (FROMLIST:, FROMGIT:, UPSTREAM:, BACKPORT:).

Failure details:

Checking commit: PENDING: arm64: defconfig: Enable CAMSS OPE driver
Commit summary does not start with a required prefix
##[error]Process completed with exit code 1.

Analysis:

This is a known limitation of the check-patch-compliance checker. The checker only accepts upstream-linkable prefixes:

• FROMLIST: (posted to mailing list)
• FROMGIT: (in maintainer tree)
• UPSTREAM: (merged to mainline)
• BACKPORT: (backported with modifications)

The PENDING: prefix is used for work-in-progress commits that have not yet been posted upstream. While this is a valid vendor-internal prefix (and passes the mandatory tag-check for non-qcom-next branches), the check-patch-compliance checker will always fail for it.

Fix options:

1. If the patch has been posted upstream: Change prefix to FROMLIST: and add a Link: trailer pointing to the lore.kernel.org URL:

   git rebase -i <base_sha>   # mark commit as 'edit'
   git commit --amend -m "FROMLIST: arm64: defconfig: Enable CAMSS OPE driver"
   # Add Link: https://lore.kernel.org/... to commit body
   git rebase --continue

2. If the patch is vendor-only and not posted: The checker will continue to fail. This is expected behavior for PENDING: commits. The failure can be acknowledged as a known limitation.

Reproduce locally:

cd <kernel-tree>
git log --oneline -1 f2f79cbd28a01c56883ac97962c2063ed3bce579
# Check if subject starts with FROMLIST/FROMGIT/UPSTREAM/BACKPORT

---

✅ tag-check (mandatory for tech/all/config branch)

Status: PASS

The target branch tech/all/config is not qcom-next or qcom-next-staging, so every commit must start with a valid prefix tag. The commit subject PENDING: arm64: defconfig: Enable CAMSS OPE driver correctly starts with PENDING:, which is one of the allowed prefixes:

• FROMLIST: ✓
• FROMGIT: ✓
• UPSTREAM: ✓
• BACKPORT: ✓
• QCLINUX: ✓
• PENDING: ✓ (used in this PR)
• WORKAROUND: ✓

---

Verdict

One known limitation blocker:

The check-patch-compliance failure is a known checker limitation for PENDING: prefixed commits. This is not a patch defect.

Recommended actions:

1. If the CONFIG_VIDEO_QCOM_CAMSS_OPE driver patch has been posted upstream: Update the commit prefix to FROMLIST: and add the lore.kernel.org link.

2. If this is genuinely a pending/work-in-progress change: The checker failure can be acknowledged and the PR can proceed. The commit correctly follows the mandatory subject-prefix requirement for the tech/all/config branch.

3. Verify integration status: The integration presence report shows this commit is already present in the topics branches, suggesting this may be a sync/backport operation rather than a new change.

All other checkers passed or correctly skipped (no relevant file changes). The patch itself is clean with no coding style, binding, or ABI issues.