Shikra: Fix QCE configuration for runtime PM by roopak-houji · Pull Request #1247 · qualcomm-linux/kernel

roopak-houji · 2026-10-07T10:07:45Z

Backport QCE runtime PM and interconnect bandwidth scaling support.
Replace the older Shikra QCE DT configuration with the latest mailing-list fix.
Update the Shikra QCE node to match the Agatti-based hardware integration.
Ensure QCE has the correct resource configuration after clk-smd-rpm proxy voting removal.
Keep cryptobam clocks remotely managed because cryptobam is marked qcom,controlled-remotely

CRs-fixed: 4671922

Signed-off-by: Roopak Houji rhouji@qti.qualcomm.com

qswat-orbit-external · 2026-10-07T10:07:53Z

Merge Check Failed: CR Not Eligible for Merge

CR 4671922 is not eligible for merge.

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

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

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

qswat-orbit-external · 2026-10-07T10:57:46Z

Merge Check Failed: CR Not Eligible for Merge

CR 4671922 is not eligible for merge.

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

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

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

kuld-sing

LGTM!

qswat-orbit-external · 2026-10-07T12:07:16Z

Merge Check Failed: CR Not Eligible for Merge

CR 4671922 is not eligible for merge.

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

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

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

qswat-orbit-external · 2026-10-07T12:31:19Z

Merge Check Failed: CR Not Eligible for Merge

CR 4671922 is not eligible for merge.

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

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

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

qcomlnxci · 2026-10-07T13:00:31Z

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	⚠️ skip	✅ Pass	⚠️ skip	⚠️ skip	⚠️ skip
BT_FW_KMD_Service	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
BT_ON_OFF	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
BT_SCAN	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	❌ Fail
CPUFreq_Validation	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
CPU_affinity	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
DSP_AudioPD	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	⚠️ skip
Ethernet_Basic_Validation	⚠️ skip	◻️	✅ Pass	⚠️ skip	⚠️ skip	⚠️ skip	❌ Fail	❌ Fail	⚠️ skip
Freq_Scaling	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	❌ Fail	✅ Pass	✅ Pass	✅ Pass
GIC	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	❌ Fail	✅ Pass	✅ Pass	❌ Fail
IPA	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
Interrupts	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
KVM_Driver	❌ Fail	◻️	✅ Pass	❌ Fail	❌ Fail	✅ Pass	❌ Fail	❌ Fail	❌ Fail
KVM_EL2_DTB	❌ Fail	◻️	✅ Pass	❌ Fail	❌ Fail	✅ Pass	❌ Fail	❌ Fail	❌ Fail
KVM_Infra	❌ Fail	◻️	✅ Pass	❌ Fail	❌ Fail	✅ Pass	❌ Fail	❌ Fail	❌ Fail
OpenCV	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
PCIe	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	❌ Fail
Probe_Failure_Check	❌ Fail	◻️	❌ Fail	❌ Fail	❌ Fail	❌ Fail	❌ Fail	❌ Fail	❌ Fail
RMNET	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
UFS_Validation	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	⚠️ skip
USBHost	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	⚠️ skip	✅ Pass	✅ Pass	❌ Fail
WiFi_Firmware_Driver	✅ Pass	◻️	❌ Fail	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
WiFi_OnOff	✅ Pass	◻️	❌ Fail	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	⚠️ skip
adsp_remoteproc	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	⚠️ skip
cdsp_remoteproc	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	❌ Fail	✅ Pass	✅ Pass	✅ Pass
gpdsp_remoteproc	⚠️ skip	◻️	✅ Pass	⚠️ skip	⚠️ skip	⚠️ skip	✅ Pass	✅ Pass	⚠️ skip
hotplug	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
irq	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
kaslr	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
pinctrl	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
qcom_hwrng	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
rngtest	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
shmbridge	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
smmu	❌ Fail	◻️	✅ Pass	❌ Fail	❌ Fail	✅ Pass	✅ Pass	❌ Fail	✅ Pass
watchdog	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
wpss_remoteproc	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass

qcomlnxci · 2026-10-07T13:03:21Z

Test jobs on 3e19832

qcomlnxci · 2026-10-07T14:42:20Z

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	◻️	⚠️ skip	✅ Pass	⚠️ skip	⚠️ skip	⚠️ skip
BT_FW_KMD_Service	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
BT_ON_OFF	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
BT_SCAN	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
CPUFreq_Validation	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
CPU_affinity	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
DSP_AudioPD	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	⚠️ skip
Ethernet_Basic_Validation	⚠️ skip	✅ Pass	✅ Pass	◻️	⚠️ skip	⚠️ skip	❌ Fail	⚠️ skip	⚠️ skip
Freq_Scaling	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	❌ Fail	✅ Pass	✅ Pass	✅ Pass
GIC	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	❌ Fail	✅ Pass	✅ Pass	❌ Fail
IPA	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
Interrupts	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
KVM_Driver	❌ Fail	✅ Pass	✅ Pass	◻️	❌ Fail	✅ Pass	❌ Fail	❌ Fail	❌ Fail
KVM_EL2_DTB	❌ Fail	✅ Pass	✅ Pass	◻️	❌ Fail	✅ Pass	❌ Fail	❌ Fail	❌ Fail
KVM_Infra	❌ Fail	✅ Pass	✅ Pass	◻️	❌ Fail	✅ Pass	❌ Fail	❌ Fail	❌ Fail
OpenCV	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
PCIe	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	❌ Fail
Probe_Failure_Check	❌ Fail	❌ Fail	❌ Fail	◻️	❌ Fail	❌ Fail	❌ Fail	❌ Fail	❌ Fail
RMNET	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
UFS_Validation	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	⚠️ skip
USBHost	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	⚠️ skip	✅ Pass	✅ Pass	❌ Fail
WiFi_Firmware_Driver	✅ Pass	✅ Pass	❌ Fail	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
WiFi_OnOff	✅ Pass	✅ Pass	❌ Fail	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	⚠️ skip
adsp_remoteproc	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	⚠️ skip
cdsp_remoteproc	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	❌ Fail	✅ Pass	✅ Pass	✅ Pass
gpdsp_remoteproc	⚠️ skip	✅ Pass	✅ Pass	◻️	⚠️ skip	⚠️ skip	✅ Pass	✅ Pass	⚠️ skip
hotplug	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
irq	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
kaslr	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
pinctrl	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
qcom_hwrng	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
rngtest	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
shmbridge	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
smmu	❌ Fail	❌ Fail	✅ Pass	◻️	❌ Fail	✅ Pass	✅ Pass	❌ Fail	✅ Pass
watchdog	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
wpss_remoteproc	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass

qcomlnxci · 2026-10-07T14:43:19Z

Test jobs on f575ca8

qcomlnxci · 2026-10-07T15:31:06Z

Test Matrix

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

qcomlnxci · 2026-10-07T15:31:58Z

Test jobs on 9b567da

qcomlnxci · 2026-10-08T06:11:51Z

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	✅ Pass
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	⚠️ skip	⚠️ 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 · 2026-10-08T06:12:46Z

Test jobs on 9b567da

qcomlnxci · 2026-10-08T09:53:24Z

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	◻️
BT_FW_KMD_Service	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
BT_ON_OFF	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
BT_SCAN	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
CPUFreq_Validation	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
CPU_affinity	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
DSP_AudioPD	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
Ethernet_Basic_Validation	⚠️ skip	✅ Pass	✅ Pass	⚠️ skip	⚠️ skip	⚠️ skip	⚠️ skip	❌ Fail	◻️
Freq_Scaling	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	❌ Fail	✅ Pass	✅ Pass	◻️
GIC	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	❌ Fail	✅ Pass	✅ Pass	◻️
IPA	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
Interrupts	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
KVM_Driver	❌ Fail	✅ Pass	✅ Pass	❌ Fail	❌ Fail	✅ Pass	❌ Fail	❌ Fail	◻️
KVM_EL2_DTB	❌ Fail	✅ Pass	✅ Pass	❌ Fail	❌ Fail	✅ Pass	❌ Fail	❌ Fail	◻️
KVM_Infra	❌ Fail	✅ Pass	✅ Pass	❌ Fail	❌ Fail	✅ Pass	❌ Fail	❌ Fail	◻️
OpenCV	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
PCIe	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
Probe_Failure_Check	❌ Fail	❌ Fail	❌ Fail	❌ Fail	❌ Fail	❌ Fail	❌ Fail	❌ Fail	◻️
RMNET	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
UFS_Validation	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
USBHost	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	⚠️ skip	❌ Fail	✅ Pass	◻️
WiFi_Firmware_Driver	✅ Pass	✅ Pass	❌ Fail	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
WiFi_OnOff	✅ Pass	✅ Pass	❌ Fail	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
adsp_remoteproc	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
cdsp_remoteproc	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	❌ Fail	✅ Pass	✅ Pass	◻️
gpdsp_remoteproc	⚠️ skip	✅ Pass	✅ Pass	⚠️ skip	⚠️ skip	⚠️ skip	✅ Pass	✅ Pass	◻️
hotplug	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
irq	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
kaslr	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
pinctrl	✅ 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	◻️
shmbridge	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
smmu	❌ Fail	❌ Fail	✅ Pass	❌ Fail	❌ Fail	✅ Pass	✅ Pass	❌ Fail	◻️
watchdog	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
wpss_remoteproc	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️

qcomlnxci · 2026-10-08T09:55:35Z

Test jobs on 6baf3bb

qcomlnxci · 2026-10-08T11:53:16Z

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	◻️
BT_FW_KMD_Service	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
BT_ON_OFF	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
BT_SCAN	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
CPUFreq_Validation	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
CPU_affinity	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
DSP_AudioPD	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
Ethernet_Basic_Validation	⚠️ skip	✅ Pass	✅ Pass	⚠️ skip	⚠️ skip	⚠️ skip	⚠️ skip	❌ Fail	◻️
Freq_Scaling	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	❌ Fail	✅ Pass	✅ Pass	◻️
GIC	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	❌ Fail	✅ Pass	✅ Pass	◻️
IPA	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
Interrupts	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
KVM_Driver	❌ Fail	✅ Pass	✅ Pass	❌ Fail	❌ Fail	✅ Pass	❌ Fail	❌ Fail	◻️
KVM_EL2_DTB	❌ Fail	✅ Pass	✅ Pass	❌ Fail	❌ Fail	✅ Pass	❌ Fail	❌ Fail	◻️
KVM_Infra	❌ Fail	✅ Pass	✅ Pass	❌ Fail	❌ Fail	✅ Pass	❌ Fail	❌ Fail	◻️
OpenCV	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
PCIe	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
Probe_Failure_Check	❌ Fail	❌ Fail	❌ Fail	❌ Fail	❌ Fail	❌ Fail	❌ Fail	❌ Fail	◻️
RMNET	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
UFS_Validation	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
USBHost	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	⚠️ skip	❌ Fail	✅ Pass	◻️
WiFi_Firmware_Driver	✅ Pass	✅ Pass	❌ Fail	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
WiFi_OnOff	✅ Pass	✅ Pass	❌ Fail	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
adsp_remoteproc	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
cdsp_remoteproc	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	❌ Fail	✅ Pass	✅ Pass	◻️
gpdsp_remoteproc	⚠️ skip	✅ Pass	✅ Pass	⚠️ skip	⚠️ skip	⚠️ skip	✅ Pass	✅ Pass	◻️
hotplug	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
irq	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
kaslr	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
pinctrl	✅ 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	◻️
shmbridge	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
smmu	❌ Fail	❌ Fail	✅ Pass	❌ Fail	❌ Fail	✅ Pass	✅ Pass	❌ Fail	◻️
watchdog	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
wpss_remoteproc	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️

qcomlnxci · 2026-10-08T11:54:55Z

Test jobs on 6baf3bb

qlijarvis · 2026-10-12T12:20:14Z

PR #1247 — validate-patch

PR: #1247

Verdict	Issues	Detailed Report
⚠️	0	Full report

Final Summary

Lore link present: Yes — all 5 commits have lore links (commits 2 and 4 are QCLINUX reverts with lore links for context)
Lore link matches PR commits: Partial — Commit 3/5 has a prefix mismatch (says BACKPORT: UPSTREAM: but lore patch is v9, not yet merged); other commits match their lore sources
Upstream patch status:
- Commit 1/5: ✅ Upstreamed — merged as ef8057b07c72 in mainline
- Commit 2/5: N/A — QCLINUX vendor-only revert
- Commit 3/5: ⏳ In review — v9 posted Jul 29, 2026; no merge/NAK signals yet (incorrectly labeled as BACKPORT: UPSTREAM:)
- Commit 4/5: N/A — QCLINUX vendor-only revert
- Commit 5/5: ⏳ In review — v1 posted Oct 6, 2026; no merge/NAK signals yet (correctly labeled as FROMLIST:)
PR present in qcom-next/topics: Partial - 1/5 commit(s) only have partial integration evidence

Verdict: ⚠️ — click to expand

🔍 Patch Validation

PR: #1247 - Shikra QCE runtime PM and DTS fixes (5 commits)
Verdict: ⚠️ PARTIAL — Multiple issues found requiring correction

Summary by Commit

Commit 1/5: UPSTREAM: PM: runtime: Wrapper macros for usage counter guards

Check Status Note

Lore link present ✅ https://patch.msgid.link/3400866.aeNJFYEL58@rafael.j.wysocki

Subject matches upstream ✅ Identical (with UPSTREAM: prefix)

Body preserves rationale ✅ Complete, faithful reproduction

Authorship preserved ✅ Rafael J. Wysocki correctly in From:

Backport note ✅ (cherry picked from commit ef8057b07c72a817537856b98d6e7493b9404eaf)

Upstream status ✅ Merged — commit ef8057b07c72 exists in mainline

qcom-next presence ✅ Present in qcom-next (per integration_presence_report.md)

Diff: include/linux/pm_runtime.h — adds PM_RUNTIME_ACQUIRE* wrapper macros
Verdict: ✅ PASS — Clean cherry-pick from mainline

Commit 2/5: QCLINUX: Revert "FROMLIST: crypto: qce - Add runtime PM..."

Check Status Note

Lore link present ✅ https://lore.kernel.org/all/20251120062443.2016084-1-quic_utiwari@quicinc.com/

Prefix correctness ✅ QCLINUX: — vendor-only revert, lore link for context only

Commit message ✅ Explains revert rationale: "Moving changes from V5 to V9"

Authorship ✅ Udit Tiwari in From:, co-authors in Signed-off-by:

qcom-next presence ⚠️ Partial — only partial integration evidence (per integration_presence_report.md)

Diff: drivers/crypto/qce/core.c — reverts 87 lines of runtime PM code
Verdict: ⚠️ PARTIAL — Revert is vendor-specific; partial qcom-next presence is a concern

Commit 3/5: BACKPORT: UPSTREAM: crypto: qce - Add runtime PM and interconnect bandwidth scaling support

Check Status Note

Lore link present ✅ https://lore.kernel.org/linux-arm-msm/20260729110455.641256-1-kuldeep.singh@oss.qualcomm.com/

Subject matches upstream ❌ FAIL — Subject says "BACKPORT: UPSTREAM:" but lore patch is v9 (not yet merged)

Prefix correctness ❌ FAIL — Should be FROMLIST: not BACKPORT: UPSTREAM:

Body preserves rationale ✅ Core description matches lore v9

Authorship preserved ✅ Udit Tiwari in From: (original author), Kuldeep Singh in Signed-off-by: chain

Upstream status ⏳ Decision Pending — v9 posted Jul 29, 2026; no merge/NAK signals in lore thread

qcom-next presence ✅ Present in qcom-next (per integration_presence_report.md)

Diff: drivers/crypto/qce/core.c — adds 90 lines of runtime PM + ICC scaling
Issues:

Prefix mismatch: Patch is labeled BACKPORT: UPSTREAM: but the lore link points to a v9 patch series that is still under review (posted Jul 29, 2026). The lore thread shows no "applied" or "merged" signal. This should be FROMLIST: not BACKPORT: UPSTREAM:.

Misleading backport note: The commit message does not include a [ upstream commit <sha> ] note because the patch is not yet upstream.

Verdict: ❌ FAIL — Incorrect prefix; patch is not yet merged upstream

Commit 4/5: QCLINUX: Revert "FROMLIST: arm64: dts: qcom: shikra: Correct QCE node configuration"

Check Status Note

Lore link present ✅ https://lore.kernel.org/linux-arm-msm/20260907-b4-shikra_crypto_changse-v6-2-0676f61894b3@oss.qualcomm.com/

Prefix correctness ✅ QCLINUX: — vendor-only revert, lore link for context only

Commit message ✅ Explains revert: "moving to latest changes"

Authorship ✅ Kuldeep Singh in From:, co-authors in Signed-off-by:

qcom-next presence ✅ Present in topics (per integration_presence_report.md)

Diff: arch/arm64/boot/dts/qcom/shikra.dtsi — reverts QCE compatible/clock/interconnect changes
Verdict: ✅ PASS — Vendor-specific revert with clear rationale

Commit 5/5: FROMLIST: arm64: dts: qcom: shikra: Correct QCE node configuration

Check Status Note

Lore link present ✅ https://lore.kernel.org/lkml/20261006-shikra_qce_fix-v1-2-8ac54d81edb4@oss.qualcomm.com/

Subject matches upstream ✅ Identical (with FROMLIST: prefix)

Body preserves rationale ✅ Complete, faithful reproduction

Fixes tag ✅ Fixes: 3cc1e2a68187 ("FROMLIST: arm64: dts: qcom: shikra: Add ICE, TRNG and QCE nodes")

Authorship preserved ✅ Kuldeep Singh in From: and Signed-off-by:

Upstream status ⏳ Decision Pending — v1 posted Oct 6, 2026; no merge/NAK signals yet

qcom-next presence ✅ Present in qcom-next (per integration_presence_report.md)

Diff: arch/arm64/boot/dts/qcom/shikra.dtsi — corrects QCE compatible from sm8150-qce to ipq4019-qce, replaces interconnect with clocks
Verdict: ✅ PASS — Clean FROMLIST patch with correct prefix

Issues Found

Commit 3/5 — Incorrect prefix: Labeled BACKPORT: UPSTREAM: but the lore patch (v9, posted Jul 29, 2026) is not yet merged upstream. The lore thread shows no "applied", "queued", or merge confirmation. This should be FROMLIST: not BACKPORT: UPSTREAM:.

Commit 2/5 — Partial qcom-next presence: Integration presence report shows "partial" evidence for this revert commit. This may indicate the revert is incomplete or conflicts with existing qcom-next state.

Verdict

⚠️ PARTIAL — Commit 3/5 has an incorrect prefix that misrepresents the upstream status. Commit 2/5 has partial integration evidence.

Required fixes:

Commit 3/5: Change subject prefix from BACKPORT: UPSTREAM: to FROMLIST: to accurately reflect that the patch is still under review on the mailing list and not yet merged upstream.

Commit 2/5: Investigate the "partial" qcom-next presence status — verify that the revert is complete and does not conflict with existing qcom-next commits.

Final Summary

Lore link present: Yes — all 5 commits have lore links (commits 2 and 4 are QCLINUX reverts with lore links for context)

Lore link matches PR commits: Partial — Commit 3/5 has a prefix mismatch (says BACKPORT: UPSTREAM: but lore patch is v9, not yet merged); other commits match their lore sources

Upstream patch status:

Commit 1/5: ✅ Upstreamed — merged as ef8057b07c72 in mainline

Commit 2/5: N/A — QCLINUX vendor-only revert

Commit 3/5: ⏳ In review — v9 posted Jul 29, 2026; no merge/NAK signals yet (incorrectly labeled as BACKPORT: UPSTREAM:)

Commit 4/5: N/A — QCLINUX vendor-only revert

Commit 5/5: ⏳ In review — v1 posted Oct 6, 2026; no merge/NAK signals yet (correctly labeled as FROMLIST:)

PR present in qcom-next/topics: Partial — 4/5 commits present, 1/5 (commit 2/5) has partial integration evidence

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/5 [PATCH 1/5] UPSTREAM: PM: runtime: Wrapper macros for usage counter present - all checked added lines are present skipped - not checked because qcom-next already contains the change present

2/5 [PATCH 2/5] QCLINUX: Revert \"FROMLIST: crypto: qce - Add runtime PM partial - subject or partial tree evidence found, but full change was not verified partial - subject or partial tree evidence found, but full change was not verified partial

3/5 [PATCH 3/5] BACKPORT: UPSTREAM: crypto: qce - Add runtime PM and present - all checked added lines are present skipped - not checked because qcom-next already contains the change present

4/5 [PATCH 4/5] QCLINUX: Revert \"FROMLIST: arm64: dts: qcom: shikra: missing - no subject, patch-id, or full tree-content match found present - all checked added lines are present present

5/5 [PATCH 5/5] FROMLIST: arm64: dts: qcom: shikra: Correct QCE node present - all checked added lines are present skipped - not checked because qcom-next already contains the change present

Final Status

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

qlijarvis · 2026-10-12T12:20:16Z

PR #1247 — checker-log-analyzer

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

Checker	Result	Summary
Checker	Result	Summary
checkpatch	✅	Passed
dt-binding-check	⏭️	Skipped - no binding changes
dtb-check	✅	Passed
sparse-check	✅	Passed
check-uapi-headers	✅	Passed
check-patch-compliance	❌	4 failures: 2 prefix violations, 2 content mismatches
tag-check	❌	2 commits missing required prefix

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #1247 - PM runtime and QCE configuration updates
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/38243405352
Target branch: qcom-6.18.y

Checker Result Summary

checkpatch ✅ Passed

dt-binding-check ⏭️ Skipped - no binding changes

dtb-check ✅ Passed

sparse-check ✅ Passed

check-uapi-headers ✅ Passed

check-patch-compliance ❌ 4 failures: 2 prefix violations, 2 content mismatches

tag-check ❌ 2 commits missing required prefix

❌ check-patch-compliance

Root cause: Two types of failures: (1) QCLINUX: Revert commits lack a valid prefix before Revert, and (2) content mismatches between PR patches and upstream links.

Failure details:

Commit 1/5: UPSTREAM: PM: runtime: Wrapper macros for usage counter guards
Change is different from the one mentioned in Link
Commit 2/5: QCLINUX: Revert "FROMLIST: crypto: qce - Add runtime PM and interconnect bandwidth scaling support"
Commit summary does not start with a required prefix
Commit 3/5: BACKPORT: UPSTREAM: crypto: qce - Add runtime PM and interconnect bandwidth scaling support
Change is different from the one mentioned in Link
Commit 4/5: QCLINUX: Revert "FROMLIST: arm64: dts: qcom: shikra: Correct QCE node configuration"
Commit summary does not start with a required prefix
Commit 5/5: FROMLIST: arm64: dts: qcom: shikra: Correct QCE node configuration
✅ Passed

Fix:

For commits 2/5 and 4/5 (prefix violations):

The issue is that Revert commits must have a valid prefix before the word Revert. The current subjects start with QCLINUX: Revert, but QCLINUX: is not in the allowed prefix list for check-patch-compliance (which only accepts FROMLIST:, FROMGIT:, UPSTREAM:, BACKPORT:).

Since these are reverts of FROMLIST: patches, the correct prefix should be:

FROMLIST: Revert "FROMLIST: crypto: qce - Add runtime PM and interconnect bandwidth scaling support"

FROMLIST: Revert "FROMLIST: arm64: dts: qcom: shikra: Correct QCE node configuration"

Or if the revert itself is upstream:

UPSTREAM: Revert "FROMLIST: crypto: qce - Add runtime PM and interconnect bandwidth scaling support"
git rebase -i <base_sha>
# Mark commits 2/5 and 4/5 as 'edit'
git commit --amend -m "FROMLIST: Revert \"FROMLIST: crypto: qce - Add runtime PM and interconnect bandwidth scaling support\""
# Continue for commit 4/5
git rebase --continue
For commits 1/5 and 3/5 (content mismatches):

The checker detected differences between the PR patch and the upstream link. To diagnose:
# For commit 1/5 (UPSTREAM patch):
b4 am --single-message -C -l -3 <link-from-commit-message> -o /tmp/commit1
git format-patch -1 <commit-1-sha> --stdout > /tmp/pr-commit1.patch
diff <(awk '/^diff/,/^--$/' /tmp/commit1/*.mbx | grep -E '^[+-][^+-]') \
     <(awk '/^diff/,/^--$/' /tmp/pr-commit1.patch | grep -E '^[+-][^+-]')

# For commit 3/5 (BACKPORT patch):
b4 am --single-message -C -l -3 <link-from-commit-message> -o /tmp/commit3
git format-patch -1 <commit-3-sha> --stdout > /tmp/pr-commit3.patch
diff <(awk '/^diff/,/^--$/' /tmp/commit3/*.mbx | grep -E '^[+-][^+-]') \
     <(awk '/^diff/,/^--$/' /tmp/pr-commit3.patch | grep -E '^[+-][^+-]')
Classify the differences:

Context-only shift (line numbers changed but code identical) → Not a real issue

Legitimate adaptation (e.g., function signature changed in target tree) → Document in commit message

Missing hunk → Add the missing changes

Extra hunk → Remove or attribute separately

For BACKPORT: patches, differences are expected — ensure the commit message documents what was adapted and why.

Reproduce locally:
cd /path/to/kernel
./scripts/check-patch-compliance.sh --kernel-src . --base <base_sha> --head <head_sha>
❌ tag-check

Root cause: Commits 2/5 and 4/5 use QCLINUX: prefix, which is valid for the tree but not accepted by check-patch-compliance. Since the target branch is qcom-6.18.y (not qcom-next or qcom-next-staging), all commits must start with a valid prefix.

Failure details:

Commit 2/5: QCLINUX: Revert "FROMLIST: crypto: qce - Add runtime PM and interconnect bandwidth scaling support"

Subject starts with QCLINUX:, which is a valid tree prefix but fails check-patch-compliance

For Revert commits, the prefix must come before Revert

Commit 4/5: QCLINUX: Revert "FROMLIST: arm64: dts: qcom: shikra: Correct QCE node configuration"

Same issue as commit 2/5

Fix:

Change the prefix from QCLINUX: to an accepted prefix. Since these are reverts of FROMLIST: patches:
git rebase -i <base_sha>
# Mark commits 2/5 and 4/5 as 'edit'

# For commit 2/5:
git commit --amend -m "FROMLIST: Revert \"FROMLIST: crypto: qce - Add runtime PM and interconnect bandwidth scaling support\""

# For commit 4/5:
git commit --amend -m "FROMLIST: Revert \"FROMLIST: arm64: dts: qcom: shikra: Correct QCE node configuration\""

git rebase --continue
If these reverts are posted to the mailing list, use FROMLIST:. If they're already merged upstream, use UPSTREAM:.

Note: The QCLINUX: prefix is used in the tree for vendor-only changes, but check-patch-compliance enforces upstream-linkable prefixes only (FROMLIST:, FROMGIT:, UPSTREAM:, BACKPORT:). This is a known limitation of the checker.

Verdict

4 blockers must be fixed before merge:

Commit 2/5: Change prefix from QCLINUX: Revert to FROMLIST: Revert (or UPSTREAM: Revert)

Commit 4/5: Change prefix from QCLINUX: Revert to FROMLIST: Revert (or UPSTREAM: Revert)

Commit 1/5: Investigate and resolve content mismatch with upstream link

Commit 3/5: Investigate and resolve content mismatch with upstream link (expected for BACKPORT:, but must be documented)

All other checkers passed. Once these 4 issues are resolved, the PR will be ready to merge.

qcomlnxci · 2026-10-12T12:53:07Z

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	⚠️ skip	✅ Pass	◻️	⚠️ skip	◻️
BT_FW_KMD_Service	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	◻️
BT_ON_OFF	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	◻️
BT_SCAN	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	◻️
CPUFreq_Validation	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
CPU_affinity	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	◻️
DSP_AudioPD	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	◻️
Ethernet_Basic_Validation	⚠️ skip	✅ Pass	◻️	⚠️ skip	⚠️ skip	⚠️ skip	◻️	❌ Fail	◻️
Freq_Scaling	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	◻️
GIC	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	◻️
IPA	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	◻️
Interrupts	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	◻️
KVM_Driver	❌ Fail	✅ Pass	◻️	❌ Fail	❌ Fail	✅ Pass	◻️	❌ Fail	◻️
KVM_EL2_DTB	❌ Fail	✅ Pass	◻️	❌ Fail	❌ Fail	✅ Pass	◻️	❌ Fail	◻️
KVM_Infra	❌ Fail	✅ Pass	◻️	❌ Fail	❌ Fail	✅ Pass	◻️	❌ Fail	◻️
OpenCV	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	◻️
PCIe	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	◻️
Probe_Failure_Check	❌ Fail	❌ Fail	◻️	❌ Fail	❌ Fail	❌ Fail	◻️	❌ Fail	◻️
RMNET	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	◻️
UFS_Validation	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	◻️
USBHost	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	⚠️ skip	◻️	✅ Pass	◻️
WiFi_Firmware_Driver	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	◻️
WiFi_OnOff	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	◻️
adsp_remoteproc	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
cdsp_remoteproc	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
gpdsp_remoteproc	⚠️ skip	✅ Pass	◻️	⚠️ skip	⚠️ skip	⚠️ skip	✅ Pass	✅ Pass	◻️
hotplug	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	◻️
irq	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	◻️
kaslr	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	◻️
pinctrl	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	◻️
qcom_hwrng	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	◻️
rngtest	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	◻️
shmbridge	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	◻️
smmu	❌ Fail	❌ Fail	◻️	❌ Fail	❌ Fail	✅ Pass	◻️	❌ Fail	◻️
watchdog	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	◻️
wpss_remoteproc	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	◻️

qcomlnxci · 2026-10-12T12:54:04Z

Test jobs on 83b2c52

qcomlnxci · 2026-10-12T14:24:49Z

Test Matrix

Test Case	hamoa-iot-evk-multimedia	lemans-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	⚠️ skip	✅ Pass	⚠️ skip	⚠️ skip	◻️
BT_FW_KMD_Service	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
BT_ON_OFF	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
BT_SCAN	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
CPUFreq_Validation	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
CPU_affinity	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
DSP_AudioPD	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
Ethernet_Basic_Validation	⚠️ skip	✅ Pass	⚠️ skip	⚠️ skip	⚠️ skip	❌ Fail	⚠️ skip	◻️
Freq_Scaling	✅ Pass	✅ Pass	✅ Pass	✅ Pass	❌ Fail	✅ Pass	✅ Pass	◻️
GIC	✅ Pass	✅ Pass	✅ Pass	✅ Pass	❌ Fail	✅ Pass	✅ Pass	◻️
IPA	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
Interrupts	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
KVM_Driver	❌ Fail	✅ Pass	❌ Fail	❌ Fail	✅ Pass	❌ Fail	❌ Fail	◻️
KVM_EL2_DTB	❌ Fail	✅ Pass	❌ Fail	❌ Fail	✅ Pass	❌ Fail	❌ Fail	◻️
KVM_Infra	❌ Fail	✅ Pass	❌ Fail	❌ Fail	✅ Pass	❌ Fail	❌ Fail	◻️
OpenCV	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
PCIe	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
Probe_Failure_Check	❌ Fail	❌ Fail	❌ Fail	❌ Fail	❌ Fail	❌ Fail	❌ Fail	◻️
RMNET	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
UFS_Validation	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
USBHost	✅ Pass	✅ Pass	✅ Pass	✅ Pass	⚠️ skip	❌ Fail	✅ Pass	◻️
WiFi_Firmware_Driver	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
WiFi_OnOff	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
adsp_remoteproc	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
cdsp_remoteproc	✅ Pass	✅ Pass	✅ Pass	✅ Pass	❌ Fail	✅ Pass	✅ Pass	◻️
gpdsp_remoteproc	⚠️ skip	✅ Pass	⚠️ skip	⚠️ skip	⚠️ skip	✅ Pass	✅ Pass	◻️
hotplug	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
irq	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
kaslr	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
pinctrl	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
qcom_hwrng	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
rngtest	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
shmbridge	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
smmu	❌ Fail	❌ Fail	❌ Fail	❌ Fail	✅ Pass	✅ Pass	❌ Fail	◻️
watchdog	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
wpss_remoteproc	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️

qcomlnxci · 2026-10-12T14:26:37Z

Test jobs on f0789c7

…nnect bandwidth scaling support\" The Qualcomm Crypto Engine (QCE) driver currently lacks support for runtime power management (PM) and interconnect bandwidth control. As a result, the hardware remains fully powered and clocks stay enabled even when the device is idle. Additionally, static interconnect bandwidth votes are held indefinitely, preventing the system from reclaiming unused bandwidth. Address this by enabling runtime PM and dynamic interconnect bandwidth scaling to allow the system to suspend the device when idle and scale interconnect usage based on actual demand. Improve overall system efficiency by reducing power usage and optimizing interconnect resource allocation. Make the following changes as part of this integration: - Add support for pm_runtime APIs to manage device power state transitions. - Implement runtime_suspend() and runtime_resume() callbacks to gate clocks and vote for interconnect bandwidth only when needed. - Replace devm_clk_get_optional_enabled() with devm_pm_clk_create() + pm_clk_add() and let the PM core manage device clocks during runtime PM and system sleep. - Register dev_pm_ops with the platform driver to hook into the PM framework. Tested: - Verify that ICC votes drop to zero after probe and upon request completion. - Confirm that runtime PM usage count increments during active requests and decrements afterward. - Observe that the device correctly enters the suspended state when idle. This reverts commit 690704e. Moving changes from V5 to V9 Link: https://lore.kernel.org/all/20251120062443.2016084-1-quic_utiwari@quicinc.com/ Signed-off-by: Udit Tiwari <quic_utiwari@quicinc.com> Signed-off-by: Abhinaba Rakshit <abhinaba.rakshit@oss.qualcomm.com> Signed-off-by: Roopak Houji <rhouji@qti.qualcomm.com>

…dwidth scaling support The Qualcomm Crypto Engine (QCE) driver currently lacks support for runtime power management (PM) and interconnect bandwidth control. As a result, the hardware remains fully powered and clocks stay enabled even when the device is idle. Additionally, static interconnect bandwidth votes are held indefinitely, preventing the system from reclaiming unused bandwidth. Address this by enabling runtime PM and dynamic interconnect bandwidth scaling to allow the system to suspend the device when idle and scale interconnect usage based on actual demand. Improve overall system efficiency by reducing power usage and optimizing interconnect resource allocation. Link: https://lore.kernel.org/linux-arm-msm/20260729110455.641256-1-kuldeep.singh@oss.qualcomm.com/ Signed-off-by: Udit Tiwari <udit.tiwari@oss.qualcomm.com> Tested-by: Pankaj Patil <pankaj.patil@oss.qualcomm.com> Signed-off-by: Kuldeep Singh <kuldeep.singh@oss.qualcomm.com> Acked-by: Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com> Tested-by: Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com> Signed-off-by: Roopak Houji <rhouji@qti.qualcomm.com>

…de configuration\" Shikra is derived from Agatti and uses the same QCE integration. Update the QCE node to match the underlying hardware implementation by adjusting the fallback compatible and related properties, including clocks and clock-names. This reverts commit 61a279f. moving to latest changes Signed-off-by: Kuldeep Singh <kuldeep.singh@oss.qualcomm.com> Link: https://lore.kernel.org/linux-arm-msm/20260907-b4-shikra_crypto_changse-v6-2-0676f61894b3@oss.qualcomm.com/ Signed-off-by: Abhinaba Rakshit <abhinaba.rakshit@oss.qualcomm.com> Signed-off-by: Roopak Houji <rhouji@qti.qualcomm.com>

Shikra is derived from Agatti and uses the same QCE integration. Update the QCE node to match the underlying hardware implementation by adjusting the fallback compatible and related properties, including clocks and clock-names. Since cryptobam is marked qcom,controlled-remotely, its clocks are managed remotely and hence don't specify explicitly. Link: https://lore.kernel.org/lkml/20261006-shikra_qce_fix-v1-2-8ac54d81edb4@oss.qualcomm.com/ Fixes: 3cc1e2a ("FROMLIST: arm64: dts: qcom: shikra: Add ICE, TRNG and QCE nodes") Tested-by: Wenjia Zhang <wenjia.zhang@oss.qualcomm.com> #on shikra device Signed-off-by: Kuldeep Singh <kuldeep.singh@oss.qualcomm.com> Signed-off-by: Roopak Houji <rhouji@qti.qualcomm.com>

qcomlnxci · 2026-10-12T16:18:30Z

Test Matrix

Test Case	*

qcomlnxci · 2026-10-12T16:19:27Z

Test jobs on e33dbf7

qlijarvis · 2026-10-12T16:22:44Z

PR #1247 — validate-patch

PR: #1247

Verdict	Issues	Detailed Report
⚠️	0	Full report

Final Summary

Lore link present: Not provided in agent output
Lore link matches PR commits: Not provided in agent output
Upstream patch status: Not provided in agent output
PR present in qcom-next/topics: Partial - 1/5 commit(s) only have partial integration evidence

Verdict: ⚠️ — click to expand

🔍 Patch Validation Report

PR: #1247
Commits: 5 commits (1 UPSTREAM, 2 FROMLIST reverts, 1 BACKPORT, 1 FROMLIST)
Verdict: ⚠️ PARTIAL

Commit 1/5: UPSTREAM: PM: runtime: Wrapper macros for usage counter guards

Upstream: ef8057b07c72 (cherry-picked from mainline)
Lore link: https://patch.msgid.link/3400866.aeNJFYEL58@rafael.j.wysocki (not lore.kernel.org)
Status: ✅ PASS

Check Status Note

Subject matches upstream ✅ Subject preserved with UPSTREAM: prefix

Body preserves rationale ✅ Full commit message preserved

Fixes tag present/correct N/A No Fixes tag in original

Authorship preserved ✅ Rafael J. Wysocki correctly preserved

Backport note ✅ (cherry picked from commit ef8057b07c72...) present

Diff: ✅ PASS - adds PM_RUNTIME_ACQUIRE* wrapper macros to include/linux/pm_runtime.h

Integration: ✅ Present in qcom-next

Commit 2/5: FROMLIST: Revert "FROMLIST: crypto: qce - Add runtime PM..."

Upstream: https://lore.kernel.org/all/20251120062443.2016084-1-quic_utiwari@quicinc.com/
Lore patch: v5 "Add runtime PM" by Udit Tiwari (Nov 2025)
Status: ⚠️ REVIEW REQUIRED

Check Status Note

Subject matches upstream ⚠️ PR reverts a v5 patch; lore link points to the original v5 (not a revert)

Body preserves rationale ⚠️ Revert rationale: "Moving changes from V5 to V9"

Authorship preserved ✅ Udit Tiwari (quic_utiwari@quicinc.com) is the original v5 author

FROMLIST usage ✅ Correct - original v5 patch was posted to lore but superseded by v9

Diff: ✅ PASS - reverts the v5 runtime PM implementation

Upstream status: ⏳ Decision Pending (superseded) - v5 was superseded by v9 (see commit 3)

Integration: ⚠️ Partial in qcom-next/topics

Issues:

The commit message says "Moving changes from V5 to V9" but doesn't explain why the revert is needed

The lore link points to the original v5 patch being reverted (correct), but the revert rationale could be clearer

Commit 3/5: BACKPORT: UPSTREAM: crypto: qce - Add runtime PM...

Upstream: https://lore.kernel.org/linux-arm-msm/20260729110455.641256-1-kuldeep.singh@oss.qualcomm.com/
Lore patch: v9 "Add runtime PM" by Kuldeep Singh (Jul 2026)
Status: ⚠️ PARTIAL - backport adaptation not documented

Check Status Note

Subject matches upstream ✅ Matches v9 subject with BACKPORT: UPSTREAM: prefix

Body preserves rationale ✅ Full rationale preserved

Authorship preserved ✅ Udit Tiwari (original author) in From:, Kuldeep Singh (submitter) in Signed-off-by

Backport note ❌ Missing - no note explaining the adaptation

Acked-by/Tested-by tags ✅ Bartosz Golaszewski tags preserved

Diff: ⚠️ REVIEW - legitimate backport adaptation but undocumented

File Status Notes

drivers/crypto/qce/core.c ⚠️ Semantic difference: PR modifies devm_add_action_or_reset() call; lore v9 modifies devm_qce_register_algs() call. This is a legitimate adaptation to a different tree version, but it's not documented in the commit message.

Upstream status: ✅ ACKed - "Patch applied. Thanks." (Herbert Xu, crypto maintainer)

Integration: ✅ Present in qcom-next

Issues:

Missing backport note - The commit is marked BACKPORT: UPSTREAM: but lacks a note explaining the adaptation (e.g., [ Adapted: modified devm_add_action_or_reset instead of devm_qce_register_algs due to tree differences ])

The semantic difference suggests this tree has a different version of the qce driver than mainline at the time of v9 posting

Commit 4/5: FROMLIST: Revert "FROMLIST: arm64: dts: qcom: shikra: Correct QCE node..."

Upstream: https://lore.kernel.org/linux-arm-msm/20260907-b4-shikra_crypto_changse-v6-2-0676f61894b3@oss.qualcomm.com/
Lore patch: v6 2/2 "Correct QCE node" by Kuldeep Singh (Sep 2026)
Status: ⚠️ REVIEW REQUIRED

Check Status Note

Subject matches upstream ⚠️ PR reverts a v6 patch; lore link points to the original v6 (not a revert)

Body preserves rationale ⚠️ Revert rationale: "moving to latest changes" (vague)

Authorship preserved ✅ Kuldeep Singh correctly preserved

FROMLIST usage ✅ Correct - v6 patch was posted to lore

Diff: ✅ PASS - reverts the v6 DTS changes (compatible, clocks, interconnect)

Upstream status: ⏳ Decision Pending - Reviewed-by: Bartosz Golaszewski present in v6 thread

Integration: ✅ Present in qcom-next/topics

Issues:

Revert rationale "moving to latest changes" is too vague - should explain what "latest changes" means (likely referring to commit 5)

Commit 5/5: FROMLIST: arm64: dts: qcom: shikra: Correct QCE node configuration

Upstream: https://lore.kernel.org/lkml/20261006-shikra_qce_fix-v1-2-8ac54d81edb4@oss.qualcomm.com/
Lore patch: v1 2/2 "Correct QCE node" by Kuldeep Singh (Oct 2026)
Status: ✅ PASS

Check Status Note

Subject matches upstream ✅ Matches lore subject with FROMLIST: prefix

Body preserves rationale ✅ Full rationale preserved

Fixes tag present/correct ✅ Fixes: 3cc1e2a68187 present

Authorship preserved ✅ Kuldeep Singh correctly preserved

Tested-by tag ✅ Wenjia Zhang tag preserved

Diff: ✅ PASS - changes QCE compatible from sm8150 to ipq4019, replaces interconnect with clocks

File Status Notes

arch/arm64/boot/dts/qcom/shikra.dtsi ✅ Faithful to lore patch - adjusts QCE compatible and properties

Upstream status: ✅ ACKed - Reviewed-by: Bartosz Golaszewski

Integration: ✅ Present in qcom-next

Summary of Issues

Critical (❌)

Commit 3 - Missing backport adaptation note explaining the semantic difference in function calls

Warnings (⚠️)

Commit 2 - Revert rationale could be clearer (why move from v5 to v9?)

Commit 3 - Undocumented semantic adaptation in backport

Commit 4 - Vague revert rationale ("moving to latest changes")

Integration Status

Overall: ⚠️ Partial (4/5 present, 1/5 partial)

Commit 2 has only partial integration evidence in qcom-next/topics

Recommendation

Request changes before merging:
Commit 3 - Add a backport note explaining the adaptation:
[ Backport note: Adapted to modify devm_add_action_or_reset() instead of
  devm_qce_register_algs() due to tree differences. The logic remains
  equivalent - both ensure cleanup on error before enabling autosuspend. ]
Commit 2 - Clarify revert rationale:
This reverts commit 690704e6d259bb3329357e97e41fea96f8e9f922.

The v5 implementation is being replaced with the v9 upstream version
(next commit) which includes additional review feedback and fixes.
Commit 4 - Clarify revert rationale:
This reverts commit 61a279f4dfd2d36237afc020e0d17d7e8b77b7e4.

The v6 DTS configuration is being replaced with the v1 fix (next commit)
which corrects the QCE compatible hierarchy based on hardware validation.
Final Summary

Lore link present: Yes - all 5 commits have lore.kernel.org links

Lore link matches PR commits: Mostly - commits 1, 3, 5 match faithfully; commits 2, 4 are reverts (correct lore links to originals); commit 3 has undocumented semantic adaptation

Upstream patch status:

Commit 1: ✅ Upstreamed (cherry-picked from ef8057b)

Commit 2: ⏳ Superseded by v9 (revert is correct)

Commit 3: ✅ Accepted ("Patch applied" by Herbert Xu)

Commit 4: ⏳ Superseded by v1 fix (revert is correct)

Commit 5: ✅ In review (Reviewed-by: Bartosz Golaszewski)

PR present in qcom-next/topics: Partial - 4/5 commits present, 1/5 (commit 2) has only partial evidence

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/5 [PATCH 1/5] UPSTREAM: PM: runtime: Wrapper macros for usage counter present - all checked added lines are present skipped - not checked because qcom-next already contains the change present

2/5 [PATCH 2/5] FROMLIST: Revert \"FROMLIST: crypto: qce - Add runtime PM partial - subject or partial tree evidence found, but full change was not verified partial - subject or partial tree evidence found, but full change was not verified partial

3/5 [PATCH 3/5] BACKPORT: UPSTREAM: crypto: qce - Add runtime PM and present - all checked added lines are present skipped - not checked because qcom-next already contains the change present

4/5 [PATCH 4/5] FROMLIST: Revert \"FROMLIST: arm64: dts: qcom: shikra: missing - no subject, patch-id, or full tree-content match found present - all checked added lines are present present

5/5 [PATCH 5/5] FROMLIST: arm64: dts: qcom: shikra: Correct QCE node present - all checked added lines are present skipped - not checked because qcom-next already contains the change present

Final Status

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

qlijarvis · 2026-10-12T16:22:47Z

PR #1247 — checker-log-analyzer

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

Checker	Result	Summary
Checker	Result	Summary
checkpatch	✅	All 5 commits passed
dt-binding-check	⏭️	Skipped (no binding changes)
dtb-check	✅	Passed
sparse-check	✅	Passed
check-uapi-headers	✅	Passed
check-patch-compliance	❌	5 commits with content mismatch
tag-check	✅	All commits have valid prefixes

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #1247 - PM runtime and QCE crypto fixes for shikra
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/38270284998
Target branch: qcom-6.18.y

Checker Result Summary

checkpatch ✅ All 5 commits passed

dt-binding-check ⏭️ Skipped (no binding changes)

dtb-check ✅ Passed

sparse-check ✅ Passed

check-uapi-headers ✅ Passed

check-patch-compliance ❌ 5 commits with content mismatch

tag-check ✅ All commits have valid prefixes

❌ check-patch-compliance

Root cause: All 5 commits report "Change is different from the one mentioned in Link" — the checker detected differences between the PR commits and their upstream lore references.

Failure details:
Checking commit: UPSTREAM: PM: runtime: Wrapper macros for usage counter guards
Change is different from the one mentioned in Link

Checking commit: FROMLIST: Revert "FROMLIST: crypto: qce - Add runtime PM and interconnect bandwidth scaling support"
Change is different from the one mentioned in Link

Checking commit: BACKPORT: UPSTREAM: crypto: qce - Add runtime PM and interconnect bandwidth scaling support
Change is different from the one mentioned in Link

Checking commit: FROMLIST: Revert "FROMLIST: arm64: dts: qcom: shikra: Correct QCE node configuration"
Change is different from the one mentioned in Link

Checking commit: FROMLIST: arm64: dts: qcom: shikra: Correct QCE node configuration
Change is different from the one mentioned in Link
Analysis:

This is a content mismatch issue. The checker compares the diff in each commit against the upstream patch fetched from the Link: URL using b4 am. Differences can occur for several legitimate reasons:

Commit 1 (UPSTREAM): Contains (cherry picked from commit ef8057b07c72...) — this is a cherry-pick from mainline, not the original mailing list patch. The Link: points to the mailing list discussion, but the actual code was taken from the merged commit. This is a legitimate adaptation but the prefix should be BACKPORT: UPSTREAM: if the cherry-pick required any conflict resolution or context adjustment, or the Link should point to the git commit instead of the mailing list.

Commits 2, 4, 5 (FROMLIST): These are revert commits and a new patch. If they differ from the lore versions, it could be due to:

Context differences (surrounding code changed in the target branch)

Legitimate adaptations for the vendor tree

The lore patch was updated after the Link was captured

Commit 3 (BACKPORT: UPSTREAM): This commit is correctly prefixed as BACKPORT:, acknowledging it's been modified from upstream. However, the commit message does not document what was changed in the backport. This is the key issue — BACKPORT: commits must explain the adaptations in the commit message.

Fix:

For each commit with content mismatch, verify the nature of the difference:
# For each commit, fetch the upstream version and compare
b4 am --single-message -C -l -3 <Link-URL> -o /tmp/upstream.mbx

# Extract the diff lines from both versions
git format-patch -1 <commit-sha> --stdout | awk '/^diff/,/^--$/' | grep -E '^[+-][^+-]' > /tmp/pr-diff.txt
awk '/^diff/,/^--$/' /tmp/upstream.mbx/*.mbx | grep -E '^[+-][^+-]' > /tmp/upstream-diff.txt

# Compare
diff /tmp/pr-diff.txt /tmp/upstream-diff.txt
Then take action based on the difference type:

Difference type Action

Context-only (line numbers shifted, no code change) Acceptable — checker limitation

Legitimate adaptation (e.g., API changed, dependency missing) Document in commit message what was adapted and why

Missing hunk Add the missing code

Extra hunk Remove or split into separate commit with proper attribution

Cherry-pick from mainline (not mailing list) Change Link: to point to the git commit, or change prefix to BACKPORT: UPSTREAM: and document

Specific recommendations:
Commit 1: Either change the Link: to point to the mainline commit (https://git.kernel.org/...ef8057b07c72), or change the prefix to BACKPORT: UPSTREAM: and add a note explaining any context adjustments made during the cherry-pick.
Commit 3: Add a paragraph to the commit message documenting what was changed from the upstream version. For example:
[ Backport notes: Adapted for qcom-6.18.y - <explain what changed> ]
Commits 2, 4, 5: Verify the differences are context-only or legitimate. If legitimate, document them. If the lore patch was updated after the Link was captured, update the Link to the correct version.
Reproduce locally:
cd <kernel-tree>
bash ../kernel-checkers/check-patch-compliance.sh \
  --kernel-src . \
  --base e6879a1e4a7912973929e2261db20279da3ffeb8 \
  --head e33dbf7f192be65694029a675f828e826f99198a
Verdict

4 blockers to fix before merge:

Commit 1 (UPSTREAM): Mismatch between Link (mailing list) and actual source (cherry-pick from mainline). Either update the Link to point to the git commit, or change prefix to BACKPORT: UPSTREAM: and document the adaptation.

Commit 3 (BACKPORT): Missing backport notes in the commit message. Add a paragraph documenting what was changed from the upstream version.

Commits 2, 4, 5 (FROMLIST): Content mismatch with lore. Verify the differences are legitimate and document them if they are adaptations, or fix if they are errors.

General: For any commit with legitimate adaptations, the commit message must explain what was changed and why. This is especially critical for BACKPORT: commits.

Note: All other checkers passed cleanly. The code quality, style, DT validation, sparse analysis, and UAPI compatibility are all good. The only issue is the patch compliance documentation.

qlijarvis · 2026-10-12T16:38:48Z

🔨 Build Failure Analysis — PR #1247

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

#	Error	File:Line	PR-introduced?	Root Cause
N/A	No compilation errors	N/A	N/A	Build succeeded

Verdict

✅ All kernel builds completed successfully. No compilation errors were introduced by this PR. The workflow failure was caused by test infrastructure issues (SSL certificate verification failures when connecting to LAVA test server), not by build errors.

📎 Detailed analysis: Full report

qlijarvis · 2026-10-12T16:44:02Z

🔨 Build Failure Analysis — PR #1247

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

Build Status: ✅ SUCCESS

The kernel compilation completed successfully for all configurations. Both the standard and RT kernel builds passed without any compilation errors or warnings.

Workflow Failure Root Cause

The GitHub Actions workflow was marked as failed due to LAVA test submission failures, not build failures. All 10 test submission jobs failed with the following SSL certificate error:

Unable to connect: HTTPSConnectionPool(host='lava-oss.qualcomm.com', port=443): 
Max retries exceeded with url: /RPC2 (Caused by SSLError(SSLCertVerificationError(1, 
'[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1000)')))

Verdict

No compilation errors were introduced by this PR. The kernel builds succeeded completely. The workflow failure is due to infrastructure issues (SSL certificate problems with the LAVA test server), not code problems.

📎 Detailed analysis: Full report

qlijarvis · 2026-10-12T16:48:53Z

🔨 Build Failure Analysis — PR #1247

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

Build Status: ✅ SUCCESS

The kernel build completed successfully with no compilation errors. All target configurations built cleanly:

Base build: ✅ Success
RT build: ✅ Success
All flat builds (10 targets): ✅ Success

Workflow Status: ❌ FAILED

The workflow was marked as failed due to test infrastructure issues, not build failures:

Root cause: LAVA job submission failed with SSL certificate verification errors
Error: SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate'))
Impact: All 10 test jobs failed to submit to LAVA

Component	Status	Details
Kernel Build	✅ Pass	No compilation errors
RT Build	✅ Pass	No compilation errors
Flat Builds (10 targets)	✅ Pass	All targets built successfully
Test Submission	❌ Fail	LAVA SSL certificate verification failure

Verdict

Zero compilation errors. The PR changes compile cleanly. The workflow failure is due to test infrastructure (LAVA SSL certificate) issues, not code problems introduced by this PR.

📎 Detailed analysis: Full report

qlijarvis · 2026-10-12T16:53:36Z

🔨 Build Failure Analysis — PR #1247

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

Verdict

No compilation errors found. The kernel build completed successfully. The workflow failure was caused by LAVA test infrastructure connectivity issues (SSL certificate verification failure), not by compilation errors introduced in this PR.

Build Status: ✅ SUCCESS

All kernel modules compiled successfully
No compilation errors or warnings-as-errors detected
The PR changes to drivers/crypto/qce/core.c, include/linux/pm_runtime.h, and arch/arm64/boot/dts/qcom/shikra.dtsi built cleanly

Test Status: ❌ FAILED (Infrastructure Issue)

LAVA job submission failed due to SSL certificate verification error
Error: Unable to connect: HTTPSConnectionPool(host='lava-oss.qualcomm.com', port=443): Max retries exceeded with url: /RPC2 (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1000)')))
This is a pre-existing infrastructure issue, not related to the PR changes

📎 Detailed analysis: Full report

qlijarvis · 2026-10-12T16:59:08Z

🔨 Build Failure Analysis — PR #1247

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

Build Status: ✅ ALL BUILDS SUCCEEDED

The workflow was marked as failed, but this was not due to compilation errors. All kernel builds completed successfully:

✅ Base build (arm64 defconfig): SUCCESS
✅ RT build: SUCCESS
✅ All 10 flat builds (hamoa, lemans, monaco, purwa, qcs615, qcs6490-rb3gen2, qcs8300, qcs9100, qrb2210, shikra): SUCCESS

Actual Failure Cause

The workflow failed during the test submission phase, not the build phase. All 10 test jobs failed with:

Unable to connect: HTTPSConnectionPool(host='lava-oss.qualcomm.com', port=443): 
Max retries exceeded with url: /RPC2 (Caused by SSLError(SSLCertVerificationError(1, 
'[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate')))

This is an infrastructure/environment issue with the LAVA test submission system, not a code or build problem introduced by this PR.

Verdict

0 compilation errors. The PR builds cleanly. The workflow failure is unrelated to the code changes and is caused by LAVA SSL certificate verification failures in the test infrastructure.

📎 Detailed analysis: Full report

qlijarvis · 2026-10-12T17:03:58Z

🔨 Build Failure Analysis — PR #1247

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

#	Error	File:Line	PR-introduced?	Root Cause
N/A	No compilation errors	N/A	N/A	All kernel builds completed successfully

Verdict

No compilation errors found. All 10 kernel builds (base + 9 flat builds) completed successfully. The workflow failure was caused by LAVA test submission failures due to SSL certificate verification errors when connecting to lava-oss.qualcomm.com, which is an infrastructure issue unrelated to the PR code changes.

📎 Detailed analysis: Full report

qlijarvis · 2026-10-12T17:08:26Z

🔨 Build Failure Analysis — PR #1247

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

Build Status: ✅ SUCCESS

All kernel builds completed successfully with zero compilation errors across all target platforms:

hamoa-iot-evk
lemans-evk
monaco-evk
purwa-iot-evk
qcs615-ride
qcs6490-rb3gen2
qcs8300-ride
qcs9100-ride-r3
qrb2210-rb1
shikra-iqs-evk

Workflow Failure Root Cause

The GitHub Actions workflow was marked as failed due to LAVA test job submission failures, not compilation errors. All 10 test jobs failed with SSL certificate verification errors when attempting to submit jobs to lava-oss.qualcomm.com:

Unable to connect: HTTPSConnectionPool(host='lava-oss.qualcomm.com', port=443): 
Max retries exceeded with url: /RPC2 (Caused by SSLError(SSLCertVerificationError(1, 
'[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local 
issuer certificate (_ssl.c:1000)')))

Verdict

No compilation errors were introduced by this PR. The kernel builds successfully for all target platforms. The workflow failure is due to infrastructure issues (LAVA SSL certificate problems), not code quality issues.

📎 Detailed analysis: Full report

qlijarvis · 2026-10-12T17:13:23Z

🔨 Build Failure Analysis — PR #1247

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

Verdict

✅ Build Successful — No compilation errors detected. All build jobs completed successfully.

The PR introduces runtime PM and interconnect bandwidth scaling support for the Qualcomm Crypto Engine (QCE) driver, along with related device tree updates for the Shikra platform. The changes compiled cleanly across all tested configurations.

📎 Detailed analysis: Full report

qlijarvis · 2026-10-12T17:18:33Z

🔨 Build Failure Analysis — PR #1247

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

#	Error	File:Line	PR-introduced?	Root Cause
N/A	No compilation errors	N/A	N/A	Build succeeded

Verdict

The kernel build completed successfully with no compilation errors. The workflow failure was caused by LAVA test submission failing due to an SSL certificate verification error when connecting to lava-oss.qualcomm.com, which is an infrastructure issue unrelated to the PR code changes.

📎 Detailed analysis: Full report

qlijarvis · 2026-10-12T17:23:42Z

🔨 Build Failure Analysis — PR #1247

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

Verdict

No compilation errors found. All kernel builds completed successfully. The workflow failure was caused by test infrastructure issues (SSL certificate verification failures when connecting to LAVA), not by compilation problems or code introduced in this PR.

Build Status Summary

Main build: ✅ Success
RT build: ✅ Success
All flat builds (10 targets): ✅ Success
Test jobs: ❌ Failed (infrastructure issue - SSL cert verification)

Analysis

This PR introduces 5 patches:

PM runtime wrapper macros (include/linux/pm_runtime.h)
Revert of QCE runtime PM support (drivers/crypto/qce/core.c)
Backport of QCE runtime PM support (drivers/crypto/qce/core.c)
Revert of Shikra QCE DTS changes (arch/arm64/boot/dts/qcom/shikra.dtsi)
Shikra QCE DTS configuration (arch/arm64/boot/dts/qcom/shikra.dtsi)

All changes compiled cleanly across all target configurations. The only warnings present in the logs are pre-existing device tree warnings unrelated to this PR (graph_port unit address warnings in camera sensor DTSIs).

📎 Detailed analysis: Full report

roopak-houji · 2026-10-13T10:19:25Z

Regarding the Kernel-checker failure
I do see below failures
1.Checking commit: UPSTREAM: PM: runtime: Wrapper macros for usage counter guards
Change is different from the one mentioned in Link

2.Checking commit: FROMLIST: Revert "FROMLIST: crypto: qce - Add runtime PM and interconnect bandwidth scaling support"
Change is different from the one mentioned in Link

3.Checking commit: BACKPORT: UPSTREAM: crypto: qce - Add runtime PM and interconnect bandwidth scaling support
Change is different from the one mentioned in Link

4.Checking commit: FROMLIST: Revert "FROMLIST: arm64: dts: qcom: shikra: Correct QCE node configuration"
Change is different from the one mentioned in Link

Change 2,3,4 are expected as the code change will be different.
Change 1 - I checked the changes from the lore link and the updates I ported are the same. However, it is still reporting that the change is different. I'm not sure why this discrepancy is being flagged.
.

Regarding pre-merge failure
Unable to submit ./renders/lava_job_definition.yaml: <Fault 400: "Device unavailable: Device type 'rb1' is unavailable.">
ERROR: LAVA submission did not return a numeric job ID.
Unable to submit ./renders/lava_job_definition.yaml: <Fault 400: "Device unavailable: Device type 'rb1' is unavailable.">
Error: Process completed with exit code 1.
Not sure what this error is it is unrelated to our changes

qcomlnxci · 2026-10-13T12:01:32Z

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	✅ Pass
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	❌ Fail	⚠️ 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 · 2026-10-13T12:03:28Z

Test jobs on e33dbf7

roopak-houji requested review from a team, Amit Kucheria (idlethread), Kaushal Kumar (quic-kaushalk) and Salendarsingh Gaud (sgaud-quic) October 7, 2026 10:07

roopak-houji force-pushed the shikra_pm_qce_fix branch from e8df8bb to 3e19832 Compare October 7, 2026 10:57

roopak-houji changed the title ~~arm64: dts: qcom: shikra: Fix QCE configuration for runtime PM~~ shikra: Fix QCE configuration for runtime PM Oct 7, 2026

roopak-houji changed the title ~~shikra: Fix QCE configuration for runtime PM~~ Shikra: Fix QCE configuration for runtime PM Oct 7, 2026

kuld-sing approved these changes Oct 7, 2026

View reviewed changes

roopak-houji force-pushed the shikra_pm_qce_fix branch from 3e19832 to f575ca8 Compare October 7, 2026 12:07

roopak-houji force-pushed the shikra_pm_qce_fix branch from f575ca8 to 9b567da Compare October 7, 2026 12:31

roopak-houji force-pushed the shikra_pm_qce_fix branch from 9b567da to 6baf3bb Compare October 8, 2026 07:04

Komal Bajaj (Komal-Bajaj) approved these changes Oct 8, 2026

View reviewed changes

roopak-houji force-pushed the shikra_pm_qce_fix branch from 6baf3bb to 46cd21e Compare October 8, 2026 10:00

qcomlnxci requested a review from a team October 8, 2026 10:02

Udit Tiwari and others added 4 commits October 12, 2026 20:53

roopak-houji force-pushed the shikra_pm_qce_fix branch from f0789c7 to e33dbf7 Compare October 12, 2026 15:25

Qualcomm Linux (qualcomm-linux) deleted a comment from qlijarvis Oct 12, 2026

Salendarsingh Gaud (sgaud-quic) merged commit a746938 into qualcomm-linux:qcom-6.18.y Oct 13, 2026
6 of 8 checks passed

Conversation

roopak-houji commented Oct 7, 2026 • edited by sgaud-quic Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

qswat-orbit-external Bot commented Oct 7, 2026

Uh oh!

qswat-orbit-external Bot commented Oct 7, 2026

Uh oh!

kuld-sing left a comment

Choose a reason for hiding this comment

Uh oh!

qswat-orbit-external Bot commented Oct 7, 2026

Uh oh!

qswat-orbit-external Bot commented Oct 7, 2026

Uh oh!

qcomlnxci commented Oct 7, 2026

Test Matrix

Uh oh!

qcomlnxci commented Oct 7, 2026

Test jobs on 3e19832

Uh oh!

qcomlnxci commented Oct 7, 2026

Test Matrix

Uh oh!

qcomlnxci commented Oct 7, 2026

Test jobs on f575ca8

Uh oh!

qcomlnxci commented Oct 7, 2026

Test Matrix

Uh oh!

qcomlnxci commented Oct 7, 2026

Test jobs on 9b567da

Uh oh!

qcomlnxci commented Oct 8, 2026

Test Matrix

Uh oh!

qcomlnxci commented Oct 8, 2026

Test jobs on 9b567da

Uh oh!

qcomlnxci commented Oct 8, 2026

Test Matrix

Uh oh!

qcomlnxci commented Oct 8, 2026

Test jobs on 6baf3bb

Uh oh!

qcomlnxci commented Oct 8, 2026

Test Matrix

Uh oh!

qcomlnxci commented Oct 8, 2026

Test jobs on 6baf3bb

Uh oh!

qlijarvis commented Oct 12, 2026

PR #1247 — validate-patch

Final Summary

🔍 Patch Validation

Summary by Commit

Commit 1/5: UPSTREAM: PM: runtime: Wrapper macros for usage counter guards

Commit 2/5: QCLINUX: Revert "FROMLIST: crypto: qce - Add runtime PM..."

Commit 3/5: BACKPORT: UPSTREAM: crypto: qce - Add runtime PM and interconnect bandwidth scaling support

Commit 4/5: QCLINUX: Revert "FROMLIST: arm64: dts: qcom: shikra: Correct QCE node configuration"

Commit 5/5: FROMLIST: arm64: dts: qcom: shikra: Correct QCE node configuration

Issues Found

Verdict

Final Summary

Deterministic Integration Presence

Integration Presence Report

Final Status

Uh oh!

qlijarvis commented Oct 12, 2026

PR #1247 — checker-log-analyzer

🤖 CI Checker Analysis (checker-log-analyzer)

❌ check-patch-compliance

❌ tag-check

Verdict

Uh oh!

qcomlnxci commented Oct 12, 2026

Test Matrix

Uh oh!

qcomlnxci commented Oct 12, 2026

Test jobs on 83b2c52

roopak-houji commented Oct 7, 2026 •

edited by sgaud-quic

Loading