FROMLIST: arm64: dts: qcom: qcs6490-rb3gen2: Enable 4-lane DisplayPort by sauana · Pull Request #494 · qualcomm-linux/kernel

sauana · 2026-04-20T12:45:08Z

Add the mode-switch property to the QMP combo PHY so that mode-switch
events are routed to it, allowing the PHY to enter DisplayPort Alternate
Mode. Expand the DP data-lanes assignment from two to four lanes to make
use of the full link bandwidth available in this configuration.

CRs-Fixed: 4429824

Fuzzying CXL triggered: BUG: KASAN: null-ptr-deref in cxl_num_decoders_committed+0x3e/0x80 drivers/cxl/core/port.c:49 Read of size 4 at addr 0000000000000642 by task syz.0.97/2282 CPU: 2 UID: 0 PID: 2282 Comm: syz.0.97 Not tainted 7.0.0-rc1-gebd11be59f74-dirty qualcomm-linux#494 PREEMPT(full) Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.17.0-0-gb52ca86e094d-prebuilt.qemu.org 04/01/2014 Call Trace: <TASK> __dump_stack lib/dump_stack.c:94 [inline] dump_stack_lvl+0x116/0x1f0 lib/dump_stack.c:120 kasan_report+0xe0/0x110 mm/kasan/report.c:595 cxl_num_decoders_committed+0x3e/0x80 drivers/cxl/core/port.c:49 cxl_mem_sanitize+0x141/0x170 drivers/cxl/core/mbox.c:1304 security_sanitize_store+0xb0/0x120 drivers/cxl/core/memdev.c:173 dev_attr_store+0x46/0x70 drivers/base/core.c:2437 sysfs_kf_write+0x95/0xb0 fs/sysfs/file.c:142 kernfs_fop_write_iter+0x276/0x330 fs/kernfs/file.c:352 new_sync_write fs/read_write.c:595 [inline] vfs_write+0x5df/0xaa0 fs/read_write.c:688 ksys_write+0x103/0x1f0 fs/read_write.c:740 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0x111/0x680 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f60a584ba79 Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f60a42a7038 EFLAGS: 00000246 ORIG_RAX: 0000000000000001 RAX: ffffffffffffffda RBX: 00007f60a5ab5fa0 RCX: 00007f60a584ba79 RDX: 0000000000000002 RSI: 00002000000001c0 RDI: 0000000000000003 RBP: 00007f60a58a49df R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007f60a5ab6038 R14: 00007f60a5ab5fa0 R15: 00007ffe58fad8b8 </TASK> This goes away using the correct check instead of abusing cxlmd->endpoint, which is unusable (ENXIO) until the driver has probed. During that window the memdev sysfs attributes are already visible, as soon as device_add() completes. Fixes: 29317f8 ("cxl/mem: Introduce cxl_memdev_attach for CXL-dependent operation") Signed-off-by: Davidlohr Bueso <dave@stgolabs.net> Reviewed-by: Jonathan Cameron <jonathan.cameron@huawei.com> Reviewed-by: Gregory Price <gourry@gourry.net> Link: https://patch.msgid.link/20260301221739.1726722-1-dave@stgolabs.net Signed-off-by: Dave Jiang <dave.jiang@intel.com>

qcomlnxci · 2026-05-07T11:05:13Z

Test jobs on 62ad886

qcomlnxci · 2026-05-07T11:05:13Z

Test Matrix

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

qcomlnxci · 2026-05-11T13:39:36Z

Test jobs on 62ad886

qcomlnxci · 2026-05-11T13:39:37Z

Test Matrix

Test Case	glymur-crd	kaanapali-mtp	lemans-evk	monaco-evk	qcs615-ride	qcs6490-rb3gen2	qcs8300-ride	qcs9100-ride-r3	sm8750-mtp	x1e80100-crd
0_qcom-next-ci-premerge-tests	◻️	◻️	◻️	◻️	❌ Fail	❌ Fail	◻️	❌ Fail	◻️	◻️
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	⚠️ skip	✅ Pass	◻️	⚠️ skip	◻️	◻️
Ethernet	◻️	◻️	◻️	✅ Pass	⚠️ skip	⚠️ skip	◻️	⚠️ skip	◻️	◻️
Freq_Scaling	◻️	◻️	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	◻️	◻️
GIC	◻️	◻️	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	◻️	◻️
IPA	◻️	◻️	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	◻️	◻️
Interrupts	◻️	◻️	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	◻️	◻️
OpenCV	◻️	◻️	◻️	⚠️ skip	✅ Pass	✅ Pass	◻️	✅ Pass	◻️	◻️
PCIe	◻️	◻️	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	◻️	◻️
Probe_Failure_Check	◻️	◻️	◻️	◻️	❌ Fail	❌ Fail	◻️	❌ Fail	◻️	◻️
RMNET	◻️	◻️	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	◻️	◻️
UFS_Validation	◻️	◻️	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	◻️	◻️
USBHost	◻️	◻️	◻️	✅ Pass	❌ Fail	❌ Fail	◻️	❌ Fail	◻️	◻️
WiFi_Firmware_Driver	◻️	◻️	◻️	⚠️ skip	✅ Pass	✅ Pass	◻️	✅ Pass	◻️	◻️
WiFi_OnOff	◻️	◻️	◻️	❌ Fail	✅ Pass	✅ Pass	◻️	✅ Pass	◻️	◻️
adsp_remoteproc	◻️	◻️	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	❌ Fail	◻️	◻️
cdsp_remoteproc	◻️	◻️	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	❌ Fail	◻️	◻️
gpdsp_remoteproc	◻️	◻️	◻️	✅ Pass	⚠️ skip	⚠️ skip	◻️	❌ Fail	◻️	◻️
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	◻️	◻️
remoteproc	◻️	◻️	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	❌ Fail	◻️	◻️
rngtest	◻️	◻️	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	◻️	◻️
shmbridge	◻️	◻️	◻️	✅ Pass	❌ Fail	❌ Fail	◻️	❌ Fail	◻️	◻️
smmu	◻️	◻️	◻️	✅ Pass	❌ Fail	✅ Pass	◻️	❌ Fail	◻️	◻️
watchdog	◻️	◻️	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	◻️	◻️
wpss_remoteproc	◻️	◻️	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	◻️	◻️

Salendarsingh Gaud (sgaud-quic) · 2026-05-11T15:42:05Z

sauana please rebase this on tip

qcomlnxci · 2026-05-11T15:50:43Z

Test jobs on 62ad886

qcomlnxci · 2026-05-11T15:50:44Z

Test Matrix

Test Case	glymur-crd	kaanapali-mtp	lemans-evk	monaco-evk	qcs615-ride	qcs6490-rb3gen2	qcs8300-ride	qcs9100-ride-r3	sm8750-mtp	x1e80100-crd
0_qcom-next-ci-premerge-tests	◻️	◻️	◻️	◻️	❌ Fail	❌ Fail	◻️	❌ Fail	◻️	◻️
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	⚠️ skip	✅ Pass	◻️	⚠️ skip	◻️	◻️
Ethernet	◻️	◻️	◻️	✅ Pass	⚠️ skip	⚠️ skip	◻️	⚠️ skip	◻️	◻️
Freq_Scaling	◻️	◻️	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	◻️	◻️
GIC	◻️	◻️	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	◻️	◻️
IPA	◻️	◻️	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	◻️	◻️
Interrupts	◻️	◻️	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	◻️	◻️
OpenCV	◻️	◻️	◻️	⚠️ skip	✅ Pass	✅ Pass	◻️	✅ Pass	◻️	◻️
PCIe	◻️	◻️	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	◻️	◻️
Probe_Failure_Check	◻️	◻️	◻️	◻️	❌ Fail	❌ Fail	◻️	❌ Fail	◻️	◻️
RMNET	◻️	◻️	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	◻️	◻️
UFS_Validation	◻️	◻️	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	◻️	◻️
USBHost	◻️	◻️	◻️	✅ Pass	❌ Fail	❌ Fail	◻️	❌ Fail	◻️	◻️
WiFi_Firmware_Driver	◻️	◻️	◻️	⚠️ skip	✅ Pass	✅ Pass	◻️	✅ Pass	◻️	◻️
WiFi_OnOff	◻️	◻️	◻️	❌ Fail	✅ Pass	✅ Pass	◻️	✅ Pass	◻️	◻️
adsp_remoteproc	◻️	◻️	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	❌ Fail	◻️	◻️
cdsp_remoteproc	◻️	◻️	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	❌ Fail	◻️	◻️
gpdsp_remoteproc	◻️	◻️	◻️	✅ Pass	⚠️ skip	⚠️ skip	◻️	❌ Fail	◻️	◻️
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	◻️	◻️
remoteproc	◻️	◻️	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	❌ Fail	◻️	◻️
rngtest	◻️	◻️	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	◻️	◻️
shmbridge	◻️	◻️	◻️	✅ Pass	❌ Fail	❌ Fail	◻️	❌ Fail	◻️	◻️
smmu	◻️	◻️	◻️	✅ Pass	❌ Fail	✅ Pass	◻️	❌ Fail	◻️	◻️
watchdog	◻️	◻️	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	◻️	◻️
wpss_remoteproc	◻️	◻️	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	◻️	◻️

Salendarsingh Gaud (sgaud-quic) · 2026-05-12T08:59:27Z

Please rebase on top of qcom-6.18.y, this is incorrect

…t Alt Mode Add the mode-switch property to the QMP combo PHY so that mode-switch events are routed to it, allowing the PHY to enter DisplayPort Alternate Mode. Expand the DP data-lanes assignment from two to four lanes to make use of the full link bandwidth available in this configuration. Link: https://lore.kernel.org/all/20260420-kodiak_4k-v1-1-83dfc66b8f06@oss.qualcomm.com/ Signed-off-by: Mahadevan P <mahadevan.p@oss.qualcomm.com>

qcomlnxci · 2026-05-12T16:44:36Z

Test jobs on 7d45b5f

qcomlnxci · 2026-05-12T16:44:45Z

Test Matrix

Test Case	glymur-crd	kaanapali-mtp	lemans-evk	monaco-evk	qcs615-ride	qcs6490-rb3gen2	qcs8300-ride	qcs9100-ride-r3	sm8750-mtp	x1e80100-crd
0_qcom-next-ci-premerge-tests	◻️	◻️	❌ Fail	◻️	❌ Fail	◻️	◻️	❌ Fail	◻️	◻️
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	⚠️ skip	◻️	◻️	⚠️ skip	◻️	◻️
Ethernet	◻️	◻️	⚠️ 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	◻️	◻️
OpenCV	◻️	◻️	✅ Pass	⚠️ skip	✅ 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	◻️	◻️	❌ Fail	✅ Pass	❌ Fail	◻️	◻️	❌ Fail	◻️	◻️
WiFi_Firmware_Driver	◻️	◻️	❌ Fail	⚠️ skip	✅ Pass	◻️	◻️	✅ Pass	◻️	◻️
WiFi_OnOff	◻️	◻️	✅ Pass	❌ Fail	✅ Pass	◻️	◻️	✅ Pass	◻️	◻️
adsp_remoteproc	◻️	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	◻️	❌ Fail	◻️	◻️
cdsp_remoteproc	◻️	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	◻️	❌ Fail	◻️	◻️
gpdsp_remoteproc	◻️	◻️	✅ Pass	✅ Pass	⚠️ skip	◻️	◻️	❌ Fail	◻️	◻️
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	◻️	◻️
remoteproc	◻️	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	◻️	❌ Fail	◻️	◻️
rngtest	◻️	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	◻️	✅ Pass	◻️	◻️
shmbridge	◻️	◻️	❌ Fail	✅ Pass	❌ Fail	◻️	◻️	❌ Fail	◻️	◻️
smmu	◻️	◻️	❌ Fail	✅ Pass	❌ Fail	◻️	◻️	❌ Fail	◻️	◻️
watchdog	◻️	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	◻️	✅ Pass	◻️	◻️
wpss_remoteproc	◻️	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	◻️	✅ Pass	◻️	◻️

Salendarsingh Gaud (sgaud-quic) · 2026-05-12T17:59:22Z

Passed jon on qcs6490-rb3gen2 : https://lava-oss.qualcomm.com/scheduler/job/95585

Salendarsingh Gaud (sgaud-quic) · 2026-05-14T09:35:55Z

PR #494 — validate-patch

PR:#494

Verdict	Issues	Detailed Report
⚠️	0	Full report

Verdict: ⚠️ — click to expand
Patch Validation Report
PR: qualcomm-linux/kernel #494 — FROMLIST: arm64: dts: qcom: qcs6490-rb3gen2: Enable 4-lane DisplayPort Alt Mode
Upstream:https://lore.kernel.org/all/20260420-kodiak_4k-v1-1-83dfc66b8f06@oss.qualcomm.com/
Verdict:⚠️ PARTIAL
Step 1 — PR Parse & Lore Link
PR changes one file: arch/arm64/boot/dts/qcom/qcs6490-rb3gen2.dts.
Lore link found: https://lore.kernel.org/all/20260420-kodiak_4k-v1-1-83dfc66b8f06@oss.qualcomm.com/
Prefix: FROMLIST: — patch posted to mailing list, not yet merged.
Step 2 — Upstream Lore Fetch
Network access is restricted in this environment; curl returned exit code 6 (no route to host) and b4 is not installed. The lore patch could not be fetched. Diff comparison (Steps 4–5) is performed by static analysis of the PR patch alone; the commit message and structural consistency are assessed against the lore URL metadata.
Step 3 — Upstream Patch Status
⏭️ Skipped — network unavailable; lore.kernel.org unreachable. Cannot confirm ACK/NACK/Pending status.
The message-ID 20260420-kodiak_4k-v1-1-83dfc66b8f06@oss.qualcomm.com encodes:
Date: 2026-04-20 (matches commit Date: header exactly)
Series tag: kodiak_4k, version v1, patch 1 of series
Author domain: oss.qualcomm.com (consistent with From: address)
This is a v1 posting with no evidence of a later revision in the PR. Community verdict cannot be confirmed offline.
Step 4–5 — PR Diff & Normalisation
Two hunks in one file; no upstream patch available for interdiff. Static analysis of the diff:
Hunk 1 (&mdss_dp_out node, line ~941):
-	data-lanes = <0 1>;+	data-lanes = <0 1 2 3>;
Expands DP from 2-lane to 4-lane. Semantically coherent with the commit description ("Expand the DP data-lanes assignment from two to four lanes").
Hunk 2 (USB QMP combo PHY node, line ~1619):
+	mode-switch;
orientation-switch;
Adds mode-switch property before the existing orientation-switch. Semantically coherent with the commit description ("Add the mode-switch property to the QMP combo PHY so that mode-switch events are routed to it").
Both hunks are internally consistent with the stated purpose. No extraneous or undocumented additions detected.
Step 6 — Commit Message Analysis
Check Status Note
Subject matches upstream ✅ FROMLIST: prefix correctly prepended; kernel subject arm64: dts: qcom: qcs6490-rb3gen2: Enable 4-lane DisplayPort Alt Mode is well-formed
Body preserves rationale ✅ Two-sentence body accurately describes both changes (mode-switch routing + 4-lane expansion)
Fixes tag present/correct N/A No Fixes: tag — this is a feature addition, not a bug fix; absence is correct
Authorship preserved ✅ FROMLIST: rule: submitter in From: is legitimate; Signed-off-by: Mahadevan P <mahadevan.p@oss.qualcomm.com> present — original lore author's SoB is present (same person)
Backport note N/A Not a backport; FROMLIST: commits do not require [ upstream commit <sha> ]
Co-developed-by misuse ✅ No Co-developed-by: present; no misuse
Link tag format ✅ Link: https://lore.kernel.org/all/<msg-id>/ — accepted form
Step 7–8 — Diff Content & File Paths
File Hunks Status Notes
arch/arm64/boot/dts/qcom/qcs6490-rb3gen2.dts 2 ✅ Both hunks internally consistent with commit description; no extra/missing code detected statically
File path is canonical for Qualcomm DTS in the upstream tree. No renames or path discrepancies.
Step 9 — Dependency Completeness
The mode-switch property on a QMP combo PHY is a standard USB-C alt-mode property defined in the usb-connector / phy DT bindings. No prerequisite patches are referenced in the commit message. The data-lanes property for mdss_dp_out is a standard DP endpoint property. No Depends-on: tags present.
⚠️Note: The lore message-ID encodes this as patch 1 of a series (v1-1). If this is part of a multi-patch series (e.g., a cover letter + patches), dependent patches from the same series may need to be present. This cannot be confirmed without network access to fetch the full thread. Recommend verifying that no companion patches in the kodiak_4k series are required.
Step 10 — qcom-next Presence
⏭️ Skipped — network unavailable; cannot clone or fetch https://github.com/qualcomm-linux/kernel qcom-next branch. Verify manually:
git -C <qcom-kernel-repo> log origin/qcom-next --oneline \
--grep="qcs6490-rb3gen2: Enable 4-lane DisplayPort Alt Mode"| head -5
Upstream Patch Status
Commit Community Verdict
arm64: dts: qcom: qcs6490-rb3gen2: Enable 4-lane DisplayPort Alt Mode ⏭️ Skipped — network unavailable; verify at https://lore.kernel.org/all/20260420-kodiak_4k-v1-1-83dfc66b8f06@oss.qualcomm.com/
Commit Message
Check Status Note
Subject matches upstream ✅ Correctly prefixed with FROMLIST:
Body preserves rationale ✅ Accurately describes both DTS changes
Fixes tag present/correct N/A Feature addition; no Fixes tag needed
Authorship preserved ✅ FROMLIST: — submitter = lore author; SoB present
Backport note N/A Not applicable for FROMLIST:
Diff
File Status Notes
arch/arm64/boot/dts/qcom/qcs6490-rb3gen2.dts ✅ 2 hunks; both consistent with stated purpose; no undocumented additions
Issues
Series completeness unverified — The lore message-ID 20260420-kodiak_4k-v1-1-83dfc66b8f06@oss.qualcomm.com indicates patch 1 of a potentially multi-patch series (kodiak_4k). If the series has additional patches (e.g., binding updates, driver changes), they must either already be in the target tree or be included in this PR. Cannot confirm without network access.
Upstream status unverified — Network unavailable; lore fetch and qcom-next search both skipped. The patch is v1 with no revision indicator suggesting it was superseded, but community acceptance (ACK/NACK/Pending) must be confirmed manually before merge.
Verdict
The patch is structurally sound and internally consistent — commit message, authorship, FROMLIST: prefix, Link: tag, and diff content all align correctly; request changes only to confirm series completeness and upstream community status before merging.

Salendarsingh Gaud (sgaud-quic) · 2026-05-14T09:35:56Z

PR #494 — checker-log-analyzer

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

Checker	Result	Summary
Checker	Result	Summary
checkpatch	❌	CI infrastructure failure — merge conflict blocked checkout (exit 128)
dt-binding-check	❌	CI infrastructure failure — merge conflict blocked checkout (exit 128)
dtb-check	❌	CI infrastructure failure — merge conflict blocked checkout (exit 128)
sparse-check	❌	CI infrastructure failure — merge conflict blocked checkout (exit 128)
check-uapi-headers	❌	CI infrastructure failure — merge conflict blocked checkout (exit 128)
check-patch-compliance	❌	CI infrastructure failure — merge conflict blocked checkout (exit 128)
tag-check	✅	Single commit has valid `FROMLIST:` prefix
qcom-next-check	⏭️	Network unavailable; manual check required

Detailed report: Full report

Checker analysis — click to expand
🤖 CI Checker Analysis (checker-log-analyzer)
PR:#494 — FROMLIST: arm64: dts: qcom: qcs6490-rb3gen2: Enable 4-lane DisplayPort Alt Mode
Run:https://github.com/qualcomm-linux/kernel-config/actions/runs/25718244068
Target branch:qcom-6.18.y
Base SHA:2eda00b1ebc26941a0aae653b455e47662b1d94f
Head SHA:da6a9c7fa1942fa8740bf34058b7320a4fcdec82
Checker Result Summary
checkpatch ❌ CI infrastructure failure — merge conflict blocked checkout (exit 128)
dt-binding-check ❌ CI infrastructure failure — merge conflict blocked checkout (exit 128)
dtb-check ❌ CI infrastructure failure — merge conflict blocked checkout (exit 128)
sparse-check ❌ CI infrastructure failure — merge conflict blocked checkout (exit 128)
check-uapi-headers ❌ CI infrastructure failure — merge conflict blocked checkout (exit 128)
check-patch-compliance ❌ CI infrastructure failure — merge conflict blocked checkout (exit 128)
tag-check ✅ Single commit has valid FROMLIST: prefix
qcom-next-check ⏭️ Network unavailable; manual check required
❌ All Checkers — Merge Conflict (CI Infrastructure Failure)
Root cause: The CI sync step (git merge pr-494 --no-commit) produced 655 merge conflicts when attempting to merge the PR branch onto qcom-6.18.y, causing every checker job to abort with fatal: Exiting because of an unresolved conflict (exit code 128) before any actual checking could run.
Failure details:
git merge pr-494 --no-commit || echo "Merge already applied or fast-forwarded"
...
CONFLICT (add/add): Merge conflict in Documentation/ABI/testing/sysfs-bus-coresight-devices-tpda
CONFLICT (content): Merge conflict in Documentation/devicetree/bindings/arm/qcom.yaml
CONFLICT (content): Merge conflict in Documentation/devicetree/bindings/clock/qcom,sm8450-videocc.yaml
CONFLICT (content): Merge conflict in arch/arm64/boot/dts/qcom/qcs6490-rb3gen2.dts
... (655 conflicts total across Documentation/, arch/, drivers/, fs/, mm/, net/, etc.)
error: Committing is not possible because you have unmerged files.
fatal: Exiting because of an unresolved conflict.
##[error]Process completed with exit code 128.
What this means: The PR branch (da6a9c7) is based on a commit that has diverged significantly from the current tip of qcom-6.18.y (2eda00b). The PR itself touches only arch/arm64/boot/dts/qcom/qcs6490-rb3gen2.dts (a 3-line change), but the base of the PR branch is far behind the target branch, causing hundreds of unrelated conflicts when the CI tries to merge.
Fix: Rebase the PR branch onto the current tip of qcom-6.18.y:
git fetch origin qcom-6.18.y
git rebase origin/qcom-6.18.y
# Resolve any conflicts in qcs6490-rb3gen2.dts if needed
git push --force-with-lease
After rebasing, re-trigger the CI run. The actual patch change is minimal (3 lines in one DTS file) and should pass all checkers cleanly once the branch is up to date.
Reproduce locally:
git checkout qcom-6.18.y
git fetch origin pull/494/head:pr-494
git merge pr-494 --no-commit
# Will show the same conflicts
✅ tag-check
The single commit subject FROMLIST: arm64: dts: qcom: qcs6490-rb3gen2: Enable 4-lane DisplayPort Alt Mode starts with the valid FROMLIST: prefix. A Link: trailer pointing to https://lore.kernel.org/all/20260420-kodiak_4k-v1-1-83dfc66b8f06@oss.qualcomm.com/ is present. No tag-check issues.
⏭️ qcom-next-check
Commit 7d45b5f8 (FROMLIST: arm64: dts: qcom: qcs6490-rb3gen2: Enable 4-lane DisplayPort Alt Mode) requires a qcom-next presence check. Network access to git.kernel.org was unavailable in this environment.
Manually verify:
git remote add qcom-linux https://git.kernel.org/pub/scm/linux/kernel/git/qcom/linux.git
git fetch qcom-linux qcom-next
git log qcom-linux/qcom-next --oneline --grep="qcs6490-rb3gen2: Enable 4-lane DisplayPort Alt Mode"
Verdict
Not ready to merge — 1 blocker: The PR branch is severely out of date with qcom-6.18.y (655 merge conflicts). No checker results are available because all jobs aborted before running. The author must rebase onto the current qcom-6.18.y tip and re-trigger CI. The actual patch change (3 lines in qcs6490-rb3gen2.dts) is clean and well-formed.

Salendarsingh Gaud (sgaud-quic) · 2026-05-14T09:41:32Z

🔨 Build Failure Analysis — PR #494

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

#	Error	File:Line	PR-introduced?	Root Cause
1	`CONFLICT (content): Merge conflict in arch/arm64/boot/dts/qcom/qcs6490-rb3gen2.dts`	`arch/arm64/boot/dts/qcom/qcs6490-rb3gen2.dts`	Yes	PR #494 modifies `qcs6490-rb3gen2.dts` (changes `data-lanes` and adds `mode-switch`), but the `qcom-6.18.y` base branch also has concurrent changes to the same file, causing a 3-way merge conflict when the CI merges the PR head into the branch.
2	`fatal: Exiting because of an unresolved conflict` (exit code 128)	N/A — git merge step	Yes (triggered by #1)	The `git commit -m "Merged PR #494"` step aborts because the merge left 655 unresolved conflicts (including the PR's own file); the build never reaches the compiler.
3	654 additional `CONFLICT` entries across unrelated files (e.g. `Makefile`, `arch/arm64/configs/defconfig`, `drivers/…`, `mm/…`, etc.)	Various	No	These conflicts are between the PR branch base and the current `qcom-6.18.y` tip; they exist independently of PR #494's changes and indicate the PR branch is significantly behind the target branch.

Verdict

1 conflict is directly introduced by PR #494 touching qcs6490-rb3gen2.dts; the remaining 654 conflicts are pre-existing rebase debt between the PR's base commit and the current qcom-6.18.y tip — the build never reached compilation in either the default or RT variant.

📎 Detailed analysis:Full report

Salendarsingh Gaud (sgaud-quic) · 2026-05-14T09:42:00Z

🔨 Build Failure Analysis — PR #494

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

#	Error	File:Line	PR-introduced?	Root Cause
1	`CONFLICT (content): Merge conflict in arch/arm64/boot/dts/qcom/qcs6490-rb3gen2.dts`	`arch/arm64/boot/dts/qcom/qcs6490-rb3gen2.dts`	Yes	PR #494 modifies `qcs6490-rb3gen2.dts` (changes `data-lanes` and adds `mode-switch`), but the same file has diverged on `qcom-6.18.y` since the PR's base commit, causing a 3-way merge conflict when the CI tries `git merge pr-494 --no-commit`
2	`error: Committing is not possible because you have unmerged files` / `fatal: Exiting because of an unresolved conflict`	N/A (git merge step)	Yes (triggered by conflict #1 and 654 other pre-existing conflicts)	The merge of PR #494 into `qcom-6.18.y` left unresolved conflicts; git refuses to commit, aborting the build pipeline with exit code 128 — both `build / build` and `build_rt / build` jobs fail identically
3	654 additional `CONFLICT` lines across the tree (Makefile, DT bindings, drivers, mm, net, fs, …)	Various	No (pre-existing)	The PR branch (`da6a9c7`) is significantly behind `qcom-6.18.y`; the base branch has accumulated hundreds of conflicting changes unrelated to this PR

Verdict

1 of the merge conflicts is directly caused by this PR touching arch/arm64/boot/dts/qcom/qcs6490-rb3gen2.dts; the remaining 654 conflicts are pre-existing branch-divergence issues that block the merge regardless of this PR's content.

📎 Detailed analysis:Full report

sauana requested review from a team, Komal Bajaj (Komal-Bajaj), Kaushal Kumar (quic-kaushalk) and Trilok Soni (trsoni)April 20, 2026 12:45

sauana force-pushed the mybranch_2 branch from 91c3c30 to 62ad886Compare April 22, 2026 09:23

riteshk-quic approved these changes Apr 22, 2026
View reviewed changes

Shiraz Hashim (shashim-quic) approved these changes Apr 22, 2026
View reviewed changes

Shiraz Hashim (shashim-quic) previously approved these changes Apr 22, 2026
View reviewed changes

qcomlnxci requested a review from a teamMay 7, 2026 08:31

sauana dismissed Shiraz Hashim (shashim-quic)’s stale review via c369299May 12, 2026 06:35

sauana force-pushed the mybranch_2 branch from 62ad886 to c369299Compare May 12, 2026 06:35

sauana force-pushed the mybranch_2 branch from da6a9c7 to 7d45b5fCompare May 12, 2026 11:24

Shiraz Hashim (shashim-quic) approved these changes May 12, 2026
View reviewed changes

qcomlnxci requested a review from a teamMay 12, 2026 14:17

Salendarsingh Gaud (sgaud-quic) merged commit 25ea67b into qualcomm-linux:qcom-6.18.yMay 12, 2026
7 of 8 checks passed

sauana mentioned this pull request May 13, 2026
FROMLIST: arm64: dts: qcom: qcs6490-rb3gen2: Enable 4-lane DisplayPort #574
Closed

Uh oh!

Conversation

sauana commented Apr 20, 2026• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

qcomlnxci commented May 7, 2026

Test jobs on 62ad886

Uh oh!

qcomlnxci commented May 7, 2026

Test Matrix

Uh oh!

qcomlnxci commented May 11, 2026

Test jobs on 62ad886

Uh oh!

qcomlnxci commented May 11, 2026

Test Matrix

Uh oh!

Salendarsingh Gaud (sgaud-quic) commented May 11, 2026

Uh oh!

qcomlnxci commented May 11, 2026

Test jobs on 62ad886

Uh oh!

qcomlnxci commented May 11, 2026

Test Matrix

Uh oh!

Salendarsingh Gaud (sgaud-quic) commented May 12, 2026

Uh oh!

qcomlnxci commented May 12, 2026

Test jobs on 7d45b5f

Uh oh!

qcomlnxci commented May 12, 2026

Test Matrix

Uh oh!

Salendarsingh Gaud (sgaud-quic) commented May 12, 2026

Uh oh!

Uh oh!

Salendarsingh Gaud (sgaud-quic) commented May 14, 2026

PR #494 — validate-patch

Patch Validation Report

Step 1 — PR Parse & Lore Link

Step 2 — Upstream Lore Fetch

Step 3 — Upstream Patch Status

Step 4–5 — PR Diff & Normalisation

Step 6 — Commit Message Analysis

Step 7–8 — Diff Content & File Paths

Step 9 — Dependency Completeness

Step 10 — qcom-next Presence

Upstream Patch Status

Commit Message

Diff

Issues

Verdict

Uh oh!

Salendarsingh Gaud (sgaud-quic) commented May 14, 2026

PR #494 — checker-log-analyzer

🤖 CI Checker Analysis (checker-log-analyzer)

❌ All Checkers — Merge Conflict (CI Infrastructure Failure)

✅ tag-check

⏭️ qcom-next-check

Verdict

Uh oh!

Salendarsingh Gaud (sgaud-quic) commented May 14, 2026

🔨 Build Failure Analysis — PR #494

Verdict

Uh oh!

Salendarsingh Gaud (sgaud-quic) commented May 14, 2026

🔨 Build Failure Analysis — PR #494

Verdict

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

sauana commented Apr 20, 2026•
edited
Loading