QCLINUX: qcom.config: Enable DMA_CMA for DMA-BUF heap support

[Bibek Kumar Patro (bibekpatro)]

Enable CONFIG_DMA_CMA as a dependency to allow the DMA-BUF heap configs (DMABUF_HEAPS, DMABUF_HEAPS_CMA, DMABUF_HEAPS_SYSTEM) to be selected in qcom.config.

CRs-fixed:4593767

[qswat-orbit-external]

Merge Check Failed: CR Not Eligible for Merge

CR 4593767 is not eligible for merge.

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

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

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

[qlijarvis]

PR #803 — validate-patch

PR: #803

Verdict	Issues	Detailed Report
⚠️	3	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 — CONFIG_DMA_CMA is not present in current qcom-next; patch context lines (BTF configs) also absent, indicating patch is based on a different branch or future state of the tree

Verdict: ⚠️ — click to expand

🔍 Patch Validation

PR: #803 - QCLINUX: qcom.config: Enable DMA_CMA for DMA-BUF heap support
Upstream commit: N/A (vendor-only QCLINUX: commit)
Verdict: ⚠️ PARTIAL

Commit Message

Check	Status	Note
Subject matches upstream	N/A	Vendor-only commit; no upstream equivalent
Body preserves rationale	✅	Clear explanation of dependency requirement
Fixes tag present/correct	N/A	Not a fix; new config enablement
Authorship preserved	✅	Bibek Kumar Patro correctly attributed
Backport note (if applicable)	N/A	Not a backport

Diff

File	Status	Notes
arch/arm64/configs/qcom.config	⚠️	Patch context mismatch with current qcom-next

Issues

• Context mismatch: Patch hunks reference CONFIG_DEBUG_INFO_BTF, CONFIG_DEBUG_INFO_BTF_MODULES, and # CONFIG_MODULE_ALLOW_BTF_MISMATCH is not set as context lines, but these configs do not exist in the current qcom-next branch (arch/arm64/configs/qcom.config:1). The file is alphabetically sorted and currently has # CONFIG_DEBUG_INFO_REDUCED is not set at line 24, followed immediately by CONFIG_DMABUF_HEAPS=y at line 25.
• Technical correctness: ✅ The change itself is valid — CONFIG_DMA_CMA=y is indeed a required dependency for CONFIG_DMABUF_HEAPS_CMA per drivers/dma-buf/heaps/Kconfig:3.
• Insertion point: The patch would insert CONFIG_DMA_CMA=y between BTF configs and DMABUF configs, but qcom-next follows alphabetical ordering. CONFIG_DMA_CMA should be placed after CONFIG_DEBUG_INFO_REDUCED (line 24) and before CONFIG_DMABUF_HEAPS (line 25) to maintain alphabetical order.

Verdict

Patch is technically correct but based on a different branch; will likely fail to apply cleanly to current qcom-next due to context mismatch. Needs rebase.

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 — CONFIG_DMA_CMA is not present in current qcom-next; patch context lines (BTF configs) also absent, indicating patch is based on a different branch or future state of the tree

[qlijarvis]

PR #803 — checker-log-analyzer

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

Checker	Result	Summary
Checker	Result	Summary
checkpatch	✅	No style issues detected (0 errors, 0 warnings, 0 checks)
dt-binding-check	⏭️	Skipped - no changes in Documentation/devicetree/bindings
dtb-check	⏭️	Skipped - no changes in Devicetree
sparse-check	⏭️	Skipped - no relevant code changes
check-uapi-headers	⏭️	Skipped - no UAPI header changes
check-patch-compliance	❌	FAILED - commit subject missing required prefix
tag-check	N/A	Not applicable for this branch
qcom-next-check	⚠️	Requires FROMLIST:/UPSTREAM:/BACKPORT: prefix

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #803 - QCLINUX: qcom.config: Enable DMA_CMA for DMA-BUF heap support
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/28525909738

Checker	Result	Summary
checkpatch	✅	No style issues detected (0 errors, 0 warnings, 0 checks)
dt-binding-check	⏭️	Skipped - no changes in Documentation/devicetree/bindings
dtb-check	⏭️	Skipped - no changes in Devicetree
sparse-check	⏭️	Skipped - no relevant code changes
check-uapi-headers	⏭️	Skipped - no UAPI header changes
check-patch-compliance	❌	FAILED - commit subject missing required prefix
tag-check	N/A	Not applicable for this branch
qcom-next-check	⚠️	Requires FROMLIST:/UPSTREAM:/BACKPORT: prefix

❌ check-patch-compliance

Root cause: Commit subject "QCLINUX: qcom.config: Enable DMA_CMA for DMA-BUF heap support" does not start with a required prefix (UPSTREAM:, FROMLIST:, or BACKPORT:).

Failure details:

2026-07-01T14:59:52.9173849Z Checking commit: QCLINUX: qcom.config: Enable DMA_CMA for DMA-BUF heap support
2026-07-01T14:59:52.9188745Z Commit summary does not start with a required prefix
2026-07-01T14:59:52.9189348Z Leaving /opt/actions-runner/_work/kernel-config/kernel-config/kernel
2026-07-01T14:59:52.9205260Z ##[error]Process completed with exit code 1.

Fix: Update the commit subject to include one of the required prefixes:

1. If this is a Qualcomm-specific configuration change (not from upstream), the commit should either:

   • Use a different subject format that doesn't include "QCLINUX:" prefix, OR
   • Be submitted to a branch that doesn't enforce upstream prefix requirements (e.g., qcom-next or qcom-next-staging)

2. If this change is based on or related to an upstream patch:

   • Use UPSTREAM: prefix if the patch is already merged in mainline
   • Use FROMLIST: prefix if the patch is posted to a mailing list but not yet merged
   • Use BACKPORT: prefix if backporting from a newer kernel version

Example corrected subject:

FROMLIST: arm64: configs: qcom.config: Enable DMA_CMA for DMA-BUF heap support

Reproduce locally:

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

# Run the check-patch-compliance checker
cd kernel-checkers
bash check-patch-compliance.sh --kernel-src /path/to/kernel \
  --base 483a4490aadd7c75ef84303b5d28387e5848208c \
  --head a706e9d1c229661985cc1676499af89d84be92a9

Verdict

1 blocker to fix: The commit subject must be updated to include a required prefix (UPSTREAM:, FROMLIST:, or BACKPORT:) or the PR should target a branch that doesn't enforce this requirement (qcom-next/qcom-next-staging).

[qcomlnxci]

Test Matrix

Test Case	lemans-evk	monaco-evk	qcs615-ride	qcs6490-rb3gen2	qcs8300-ride	qcs9100-ride-r3	x1e80100-crd
BT_FW_KMD_Service	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
BT_ON_OFF	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
BT_SCAN	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
CPUFreq_Validation	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
CPU_affinity	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
DSP_AudioPD	⚠️ skip	◻️	⚠️ skip	✅ Pass	✅ Pass	⚠️ skip	◻️
Ethernet	⚠️ skip	◻️	⚠️ skip	⚠️ skip	⚠️ skip	⚠️ skip	◻️
Freq_Scaling	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
GIC	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
IPA	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
Interrupts	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
OpenCV	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
PCIe	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
Probe_Failure_Check	❌ Fail	◻️	✅ Pass	❌ Fail	❌ Fail	❌ Fail	◻️
RMNET	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
UFS_Validation	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
USBHost	❌ Fail	◻️	❌ Fail	❌ Fail	❌ Fail	❌ Fail	◻️
WiFi_Firmware_Driver	❌ Fail	◻️	❌ Fail	❌ Fail	✅ Pass	✅ Pass	◻️
WiFi_OnOff	✅ Pass	◻️	⚠️ skip	✅ Pass	✅ Pass	✅ Pass	◻️
adsp_remoteproc	❌ Fail	◻️	✅ Pass	✅ Pass	✅ Pass	❌ Fail	◻️
cdsp_remoteproc	❌ Fail	◻️	✅ Pass	✅ Pass	✅ Pass	❌ Fail	◻️
gpdsp_remoteproc	❌ Fail	◻️	⚠️ skip	⚠️ skip	✅ Pass	❌ Fail	◻️
hotplug	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
irq	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
kaslr	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
pinctrl	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
qcom_hwrng	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
remoteproc	❌ Fail	◻️	✅ Pass	✅ Pass	✅ Pass	❌ Fail	◻️
rngtest	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
shmbridge	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
smmu	❌ Fail	◻️	❌ Fail	✅ Pass	✅ Pass	❌ Fail	◻️
watchdog	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
wpss_remoteproc	✅ Pass	◻️	⚠️ skip	✅ Pass	✅ Pass	✅ Pass	◻️

[qcomlnxci]

Test jobs on a706e9d

• Job 148697 on lemans-evk
• Job 148703 on monaco-evk
• Job 148701 on qcs615-ride
• Job 148702 on qcs6490-rb3gen2
• Job 148698 on qcs8300-ride
• Job 148704 on qcs9100-ride-r3
• Job 148699 on x1e80100-crd

[Salendarsingh Gaud (sgaud-quic)]

Mainline PR is not yet merged
qualcomm-linux/kernel-topics#1452