QCLINUX: qcom.config: Disable CPUFREQ_DT driver

[imrashai]

A SoC-specific cpufreq driver already handles CPU frequency scalinig on Qualcomm platforms. As a result, the generic cpufreq-dt driver fails to register against the same CPUs:

cpufreq-dt cpufreq-dt: failed register driver: -17
cpufreq-dt cpufreq-dt: probe with driver cpufreq-dt failed with error -17

Disable CPUFREQ_DT to avoid this redundant probe/registration conflict on Qualcomm targets

CRs-Fixed: 4675852

[qswat-orbit-external]

Merge Check Failed: CR Not Eligible for Merge

CR 4675852 is not eligible for merge.

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

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

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

[qcomlnxci]

Test Matrix

Test Case	hamoa-iot-evk-multimedia	lemans-evk-multimedia	monaco-evk-multimedia	purwa-iot-evk-multimedia	qcs615-ride-multimedia	qcs6490-rb3gen2-multimedia	qcs8300-ride-multimedia	qcs9100-ride-r3-multimedia	shikra-iqs-evk-multimedia
Audio_Card_Registration	✅ Pass	✅ Pass	✅ Pass	✅ Pass	⚠️ skip	✅ Pass	⚠️ skip	⚠️ skip	⚠️ skip
BT_FW_KMD_Service	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
BT_ON_OFF	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
BT_SCAN	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	❌ Fail
CPUFreq_Validation	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
CPU_affinity	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
DSP_AudioPD	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	⚠️ skip
Ethernet_Basic_Validation	⚠️ skip	✅ Pass	✅ Pass	⚠️ skip	⚠️ skip	⚠️ skip	❌ Fail	⚠️ skip	⚠️ skip
Freq_Scaling	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
GIC	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	❌ Fail
IPA	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
Interrupts	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
KVM_Driver	❌ Fail	✅ Pass	✅ Pass	❌ Fail	❌ Fail	✅ Pass	❌ Fail	❌ Fail	❌ Fail
KVM_EL2_DTB	❌ Fail	✅ Pass	✅ Pass	❌ Fail	❌ Fail	✅ Pass	❌ Fail	❌ Fail	❌ Fail
KVM_Infra	❌ Fail	✅ Pass	✅ Pass	❌ Fail	❌ Fail	✅ Pass	❌ Fail	❌ Fail	❌ Fail
OpenCV	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
PCIe	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	❌ Fail
Probe_Failure_Check	❌ Fail	❌ Fail	❌ Fail	❌ Fail	❌ Fail	❌ Fail	❌ Fail	❌ Fail	❌ Fail
RMNET	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
UFS_Validation	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	⚠️ skip
USBHost	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	⚠️ skip	❌ Fail	✅ Pass	❌ Fail
WiFi_Firmware_Driver	✅ Pass	✅ Pass	❌ Fail	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
WiFi_OnOff	✅ Pass	✅ Pass	❌ Fail	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	⚠️ skip
adsp_remoteproc	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	⚠️ skip
cdsp_remoteproc	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
gpdsp_remoteproc	⚠️ skip	✅ Pass	✅ Pass	⚠️ skip	⚠️ skip	⚠️ skip	✅ Pass	✅ Pass	⚠️ skip
hotplug	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
irq	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
kaslr	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
pinctrl	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
qcom_hwrng	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
rngtest	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
shmbridge	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
smmu	❌ Fail	❌ Fail	✅ Pass	❌ Fail	❌ Fail	✅ Pass	✅ Pass	❌ Fail	✅ Pass
watchdog	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
wpss_remoteproc	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass

[qcomlnxci]

Test jobs on 4da39b6

• multimedia Job 249138 on hamoa-iot-evk
• multimedia Job 249135 on lemans-evk
• multimedia Job 249133 on monaco-evk
• multimedia Job 249137 on purwa-iot-evk
• multimedia Job 249139 on qcs615-ride
• multimedia Job 249141 on qcs6490-rb3gen2
• multimedia Job 249136 on qcs8300-ride
• multimedia Job 249134 on qcs9100-ride-r3
• multimedia Job on qrb2210-rb1
• multimedia Job 249140 on shikra-iqs-evk

[qlijarvis]

PR #1226 — validate-patch

PR: #1226

Verdict	Issues	Detailed Report
✅	1	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: #1226 - QCLINUX: qcom.config: Disable CPUFREQ_DT driver
Upstream commit: N/A (vendor-only commit)
Verdict: ✅ PASS

Commit Message

Check	Status	Note
Subject matches upstream	N/A	Vendor-only commit; no upstream source
Body preserves rationale	✅	Clear explanation of cpufreq-dt conflict
Fixes tag present/correct	N/A	Not a bug fix; config adjustment
Authorship preserved	✅	Correct author and Signed-off-by
Backport note (if applicable)	N/A	Not a backport

Diff

File	Status	Notes
arch/arm64/configs/qcom.config	✅	Single-line config disable; correct placement

Issues

• Minor typo in commit message: "scalinig" should be "scaling" (line 3 of body)

Verdict

Merge as-is. This is a valid vendor-only configuration change with clear rationale. The typo is cosmetic and does not affect functionality.

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 present in topics (all added lines verified); integration_presence_report.md status: PASS

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: ba86f67908354f41f269ca1d64b22e4624766dcf
topics remote: topics -> https://github.com/qualcomm-linux/kernel-topics
topics fetch: fetched

Commit	Subject	qcom-next	topics	Final
1/1	[PATCH] QCLINUX: qcom.config: Disable CPUFREQ_DT 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 #1226 — checker-log-analyzer

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

Checker	Result	Summary
Checker	Result	Summary
checkpatch	✅	No style issues
dt-binding-check	⏭️	Skipped (no DT binding changes)
dtb-check	⏭️	Skipped (no DTS changes)
sparse-check	⏭️	Skipped (no C/H changes)
check-uapi-headers	⏭️	Skipped (no UAPI changes)
check-patch-compliance	❌	QCLINUX: prefix not in allowed list
tag-check	⚠️	QCLINUX: is valid for tag-check but fails patch-compliance

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #1226 — QCLINUX: qcom.config: Disable CPUFREQ_DT driver
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/36845967996
Target branch: qcom-6.18.y

Checker	Result	Summary
checkpatch	✅	No style issues
dt-binding-check	⏭️	Skipped (no DT binding changes)
dtb-check	⏭️	Skipped (no DTS changes)
sparse-check	⏭️	Skipped (no C/H changes)
check-uapi-headers	⏭️	Skipped (no UAPI changes)
check-patch-compliance	❌	QCLINUX: prefix not in allowed list
tag-check	⚠️	QCLINUX: is valid for tag-check but fails patch-compliance

---

❌ check-patch-compliance

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

Failure details:

Checking commit: QCLINUX: qcom.config: Disable CPUFREQ_DT driver
Commit summary does not start with a required prefix

Analysis:

This is a known limitation of the check-patch-compliance checker. The commit is a vendor-only configuration change with no upstream equivalent, correctly tagged with QCLINUX:. However, the checker only accepts upstream-linkable prefixes.

Context from skill references (log-patterns.md Section 7):

QCLINUX: and PENDING: prefixes always fail check-patch-compliance — this is a known checker limitation for vendor-only commits.

The commit:

• ✅ Has a valid subject prefix (QCLINUX:) per the tag-check requirements
• ✅ Is properly formatted (checkpatch passed)
• ✅ Has a clear rationale (disables generic cpufreq-dt to avoid conflict with SoC-specific driver)
• ❌ Fails check-patch-compliance because QCLINUX: is not in the checker's allowed list

Options:

1. Accept the failure — This is a vendor-only change with no upstream link. The check-patch-compliance failure is expected and does not indicate a patch defect.

2. Change prefix to FROMLIST: + add Link — Only if this change has been posted upstream. If not posted, this would be incorrect.

3. Remove the prefix entirely — This would violate the tag-check requirement for branches other than qcom-next/qcom-next-staging.

Reproduce locally:

cd kernel
git log --oneline -1 4da39b6449c8c656667abd568c5c027f71808515
# Verify the commit subject starts with QCLINUX:

---

⚠️ tag-check (manual verification)

Status: The commit subject starts with QCLINUX:, which is a valid prefix for the tag-check requirement.

Target branch: qcom-6.18.y (not qcom-next or qcom-next-staging) → subject prefix is mandatory.

Valid prefixes: FROMLIST:, FROMGIT:, UPSTREAM:, BACKPORT:, QCLINUX:, PENDING:, WORKAROUND:

Verdict: ✅ PASS — The commit has a valid prefix (QCLINUX:).

---

Verdict

This is a vendor-only configuration change that correctly uses the QCLINUX: prefix.

The check-patch-compliance failure is a known checker limitation — the checker does not accept QCLINUX: or PENDING: prefixes because they are not upstream-linkable. This does not indicate a patch defect.

Recommendation:

• ✅ Merge as-is if this is genuinely a vendor-only change with no upstream equivalent.
• The failure is expected and documented in the checker's known limitations.
• All other checkers passed or were correctly skipped.
• The commit is properly formatted, has a clear rationale, and follows the tag-check requirements.

If the change has been posted upstream: Change the prefix to FROMLIST: and add a Link: trailer pointing to the lore.kernel.org URL. Otherwise, accept the check-patch-compliance failure as a known limitation for vendor-only commits.