PENDING: arm64: media: dts: sm8750-mtp: Add s5kjn5 image sensor on CSIPHY2

[HangxiangMa]

Enable the camera subsystem on the SM8750 MTP along with the S5KJN5 sensor connected to CSIPHY2 through I2C9 on QUPv3_2. Add the sensor reset pin state on the TLMM GPIO and wire up the sensor supplies.

CRs-Fixed: 4640742

[qlijarvis]

PR #1673 — validate-patch

PR: #1673

Verdict	Issues	Detailed Report
⚠️	1	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 — PENDING: work-in-progress, not posted upstream
4. PR present in qcom-next/topics: Partial - 1/1 commit(s) only have partial integration evidence

Verdict: ⚠️ — click to expand

🔍 Patch Validation

PR: #1673 - PENDING: arm64: media: dts: sm8750-mtp: Add s5kjn5 image sensor on CSIPHY2
Upstream commit: N/A (PENDING: prefix indicates work-in-progress)
Verdict: ⚠️ PARTIAL

Commit Message

Check	Status	Note
Subject matches upstream	N/A	PENDING: prefix - no upstream source to compare
Body preserves rationale	✅	Clear description of camera subsystem enablement
Fixes tag present/correct	N/A	Not a fix commit
Authorship preserved	✅	Author and Signed-off-by match
Backport note (if applicable)	N/A	Not a backport

Diff

File	Status	Notes
arch/arm64/boot/dts/qcom/sm8750-mtp.dts	✅	Adds camera sensor configuration, GPIO pinctrl, I2C device, and CAMSS port

Issues

• Integration presence: Integration report shows "partial" status - subject or partial tree evidence found in qcom-next, but full change was not verified. This suggests the commit may exist in a different form or be incomplete in the integration branch.

Verdict

This is a PENDING commit (work-in-progress) with no upstream lore link, which is expected and correct for this prefix. However, the partial integration presence status indicates the change may not be fully integrated into qcom-next yet. Verify the integration status before merging.

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 — PENDING: work-in-progress, not posted upstream
4. PR present in qcom-next/topics: Partial — 1/1 commit(s) only have partial integration evidence (subject or partial tree match found, but full change not verified in qcom-next)

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] PENDING: arm64: media: dts: sm8750-mtp: Add s5kjn5 image	partial - subject or partial tree evidence found, but full change was not verified	missing - no subject, patch-id, or full tree-content match found	partial

Final Status

overall_status: PARTIAL
present_commits: 0/1
partial_commits: 1/1
missing_commits: 0/1
topics_checked_for_commits: 1/1
final_summary: PR present in qcom-next/topics: Partial - 1/1 commit(s) only have partial integration evidence

[qlijarvis]

PR #1673 — checker-log-analyzer

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

Checker	Result	Summary
Checker	Result	Summary
checkpatch	❌	1 warning: undocumented DT compatible string
dt-binding-check	⏭️	Skipped (no binding changes)
dtb-check	✅	Passed
sparse-check	⏭️	Skipped (no C/H changes)
check-uapi-headers	⏭️	Skipped (no UAPI changes)
check-patch-compliance	❌	PENDING: prefix not accepted
tag-check	✅	Subject has valid prefix (PENDING:)

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #1673 - PENDING: arm64: media: dts: sm8750-mtp: Add s5kjn5 image sensor on CSIPHY2
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/31501828809
Target branch: tech/all/dt/pakala (qualcomm-linux/kernel-topics)

Checker	Result	Summary
checkpatch	❌	1 warning: undocumented DT compatible string
dt-binding-check	⏭️	Skipped (no binding changes)
dtb-check	✅	Passed
sparse-check	⏭️	Skipped (no C/H changes)
check-uapi-headers	⏭️	Skipped (no UAPI changes)
check-patch-compliance	❌	PENDING: prefix not accepted
tag-check	✅	Subject has valid prefix (PENDING:)

---

❌ checkpatch

Root cause: The DT compatible string "samsung,s5kjn5" is not documented in Documentation/devicetree/bindings/vendor-prefixes.yaml or lacks a binding YAML file.

Failure details:

WARNING: DT compatible string "samsung,s5kjn5" appears un-documented -- check ./Documentation/devicetree/bindings/
#51: FILE: arch/arm64/boot/dts/qcom/sm8750-mtp.dts:1315:
+		compatible = "samsung,s5kjn5";

57854f43bb896b6415c42afe4ec5c4040e5e58a2 total: 0 errors, 1 warnings, 0 checks, 76 lines checked

Fix:

Option 1 (if binding exists upstream):

• Check if samsung,s5kjn5 has an upstream binding in Documentation/devicetree/bindings/media/i2c/
• If yes, backport the binding YAML file in a separate commit before this DTS change

Option 2 (if no binding exists):

• Create Documentation/devicetree/bindings/media/i2c/samsung,s5kjn5.yaml following the kernel DT binding schema format
• Submit as a separate commit before the DTS change
• Ensure the samsung vendor prefix exists in vendor-prefixes.yaml (it likely already does)

Reproduce locally:

./scripts/checkpatch.pl --strict --ignore FILE_PATH_CHANGES --git 1110d788f08fefe87c7e387e613d4d72c50b7eb8..57854f43bb896b6415c42afe4ec5c4040e5e58a2

---

❌ check-patch-compliance

Root cause: The commit subject uses the PENDING: prefix, which is not in the allowed list for check-patch-compliance (FROMLIST:, FROMGIT:, UPSTREAM:, BACKPORT:).

Failure details:

Checking commit: PENDING: arm64: media: dts: sm8750-mtp: Add s5kjn5 image sensor on CSIPHY2
Commit summary does not start with a required prefix

Analysis:

This is a known limitation of the check-patch-compliance checker. The checker enforces a strict subset of prefixes that require upstream linkage:

• ✅ Accepted: FROMLIST:, FROMGIT:, UPSTREAM:, BACKPORT:
• ❌ Rejected: PENDING:, QCLINUX:, WORKAROUND:

The PENDING: prefix indicates work-in-progress that has not yet been posted upstream. This is a valid use case for topic branches, but the checker will always fail for such commits.

Fix options:

1. If the patch has been posted to a mailing list:

   • Change prefix to FROMLIST:
   • Add Link: <lore.kernel.org URL> to the commit message body

2. If this is vendor-only and will not be posted upstream:

   • Change prefix to QCLINUX: (but note: this will also fail check-patch-compliance)
   • Accept that check-patch-compliance will fail for vendor-only commits

3. If this is genuinely pending and not yet posted:

   • Keep PENDING: prefix
   • Accept that check-patch-compliance will fail
   • This is a known checker limitation for work-in-progress commits

Note: The tag-check (Step 2.7 of the skill) passes because PENDING: is a valid subject-line prefix for all branches except qcom-next and qcom-next-staging. The target branch tech/all/dt/pakala requires a prefix, and PENDING: satisfies that requirement.

---

Verdict

2 blockers to address before merge:

1. checkpatch warning (mandatory fix): Add DT binding documentation for samsung,s5kjn5 or backport existing upstream binding
2. check-patch-compliance failure (policy decision): Either post the patch upstream and change to FROMLIST: + add Link:, or accept that PENDING:/vendor-only commits will fail this checker

Recommendation:

• If the S5KJN5 sensor binding exists upstream, backport it in a separate commit
• If not, create the binding YAML following kernel DT schema conventions
• For the PENDING: prefix issue: if this patch will be posted upstream soon, wait and use FROMLIST: + Link:; otherwise, accept the checker limitation for work-in-progress commits