Skip to content

arm64: dts: qcom: add Monaco Draco EVK board support - #1465

Open
Faruque Ansari (faruque-ansari) wants to merge 3 commits into
qualcomm-linux:qcom-6.18.yfrom
faruque-ansari:monaco-draco-AC
Open

Faruque Ansari (faruque-ansari) wants to merge 3 commits into
qualcomm-linux:qcom-6.18.yfrom
faruque-ansari:monaco-draco-AC

Conversation

@faruque-ansari

Copy link
Copy Markdown

This series adds device tree support for the Monaco Draco EVK, an
evaluation kit based on the QCS8300 SoC targeting automotive and
industrial use cases. The platform consists of a System on Module
(SoM) paired with the Draco carrier board.

The Monaco Draco AC SoM integrates the QCS8300 SoC, two PMM8654AU
PMICs, eMMC and UFS storage, USB0/USB1, the Adreno 623 GPU, USB
and UART interfaces.

The Draco carrier board builds on the SoM and adds:

  • DWMAC gigabit Ethernet (2500base-x to HSGMII PHY), MAC from EEPROM
  • AMC6821 fan controller on i2c13
  • I2C GPIO expanders (4x kts1622 on i2c14, 2x tca9538 on i2c15)
  • Native DisplayPort output (DP0) to an on-board DP connector
  • Dual PCIe (pcie0/pcie1) via an on-board TC9563 PCIe switch
  • ST33HTPM TPM over SPI10
  • M.2 E-key slot connectivity

Signed-off-by: Faruque Ansari faruque.ansari@oss.qualcomm.com

CRs-Fixed: 4746133

Faruque Ansari added 3 commits November 17, 2026 08:43
Document the compatible strings for the Qualcomm Monaco Draco AC
System-on-Module (SoM) and its Monaco Draco EVK board.

The SoM is populated with a QCS8300 SoC, two PMM8654AU PMICs, eMMC and
UFS storage. The SoM is then connected to the EVK carrier board, which
provides a multitude of connectors for peripherals.

Signed-off-by: Faruque Ansari <faruque.ansari@oss.qualcomm.com>
Link: https://lore.kernel.org/all/20261117-monaco-draco-v1-0-e42d1673148d@oss.qualcomm.com/
Introduce the device tree for the QCS8300-based Monaco Draco AC
SoM. The Monaco Draco AC SoM is a compact compute module integrating
the QCS8300 SoC, two PMM8654AU PMICs, eMMC, UFS storage, an Adreno
623 GPU, USB and UART interfaces, designed to mount on carrier
boards.

The initial SoM device tree includes basic support for:

 - RPMH regulators for two PMM8654AU PMICs
 - QUP firmware paths (qupv3_id_0/1)
 - Remoteproc instances (ADSP, CDSP, GPDSP) with firmware paths
 - Console UART (uart7, serial0) and secondary UART (uart6, serial2)
 - eMMC storage
 - UFS storage
 - USB1 in peripheral mode with HS PHY and QMP SuperSpeed PHY, and USB2
   with HS PHY
 - GPU (Adreno 623) with ZAP shader firmware

Co-developed-by: Kishor Buchi <kbuchi@qti.qualcomm.com>
Signed-off-by: Kishor Buchi <kbuchi@qti.qualcomm.com>
Signed-off-by: Faruque Ansari <faruque.ansari@oss.qualcomm.com>
Link: https://lore.kernel.org/all/20261117-monaco-draco-v1-0-e42d1673148d@oss.qualcomm.com/
The Monaco Draco EVK pairs the Monaco Draco AC SoM with the Draco
carrier board. Add its device tree, describing the board-specific
peripherals layered on top of the SoM:

 - I2C GPIO expanders: 4x KTS1622 on i2c14 and 2x TCA9538 on i2c15
 - EEPROM with a MAC-address nvmem layout on i2c15
 - Native DisplayPort output (DP0)
 - Gigabit Ethernet (ethernet0, 2500base-x) over an HSGMII PHY, with
   the MAC address sourced from the EEPROM
 - Dual PCIe (pcie0/pcie1) behind an on-board TC9563 PCIe switch
 - ST33HTPM TPM over spi10
 - AMC6821 fan controller on i2c13
 - M.2 E-key slot connector and carrier debug UART (uart2)

Also hook the board dtb into the Makefile, together with an EL2
overlay variant that boots the kernel at EL2 for KVM.

Co-developed-by: Vishnu Saini <vishnu.saini@oss.qualcomm.com>
Signed-off-by: Vishnu Saini <vishnu.saini@oss.qualcomm.com>
Co-developed-by: Khalid Faisal Ansari <khalid.ansari@oss.qualcomm.com>
Signed-off-by: Khalid Faisal Ansari <khalid.ansari@oss.qualcomm.com>
Co-developed-by: Dipa Mantre <dipa.mantre@oss.qualcomm.com>
Signed-off-by: Dipa Mantre <dipa.mantre@oss.qualcomm.com>
Co-developed-by: Sravani Tella <tella@hu-tella-hyd.qualcomm.com>
Signed-off-by: Sravani Tella <tella@hu-tella-hyd.qualcomm.com>
Co-developed-by: Monish Chunara <monish.chunara@oss.qualcomm.com>
Signed-off-by: Monish Chunara <monish.chunara@oss.qualcomm.com>
Co-developed-by: Ajinkya Inchure <ainchure@qti.qualcomm.com>
Signed-off-by: Ajinkya Inchure <ainchure@qti.qualcomm.com>
Signed-off-by: Faruque Ansari <faruque.ansari@oss.qualcomm.com>
Link: https://lore.kernel.org/all/20261117-monaco-draco-v1-0-e42d1673148d@oss.qualcomm.com/
@qswat-orbit-external

Copy link
Copy Markdown

Merge Check Failed: CR Not Eligible for Merge

CR 4746133 is not eligible for merge.

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

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

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

@qcomlnxci

Copy link
Copy Markdown

Test results

Workflow run: 44015237234 attempt 1

Known failures configured: 46

Target Pass Non-pass Total
kbdev-hamoa-iot-evk-multimedia 29 7 36
kbdev-lemans-evk-multimedia 34 2 36
kbdev-monaco-evk-multimedia 32 4 36
kbdev-purwa-iot-evk-multimedia 26 7 33
kbdev-qcs615-ride-multimedia
kbdev-qcs6490-rb3gen2-multimedia 32 4 36
kbdev-qcs8300-ride-multimedia 29 7 36
kbdev-qcs9100-ride-r3-multimedia 29 7 36
kbdev-qrb2210-rb1-multimedia - ⛔ Not submitted -
kbdev-shikra-iqs-evk-multimedia 21 15 36

Test Matrix

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

Known failures

  • kbdev-hamoa-iot-evk-multimedia: gpdsp_remoteproc => skip.
  • kbdev-hamoa-iot-evk-multimedia: Probe_Failure_Check => fail.
  • kbdev-hamoa-iot-evk-multimedia: smmu => fail.
  • kbdev-hamoa-iot-evk-multimedia: Ethernet_Basic_Validation => skip.
  • kbdev-hamoa-iot-evk-multimedia: KVM_Driver => fail.
  • kbdev-hamoa-iot-evk-multimedia: KVM_EL2_DTB => fail.
  • kbdev-hamoa-iot-evk-multimedia: KVM_Infra => fail.
  • kbdev-lemans-evk-multimedia: Probe_Failure_Check => fail.
  • kbdev-lemans-evk-multimedia: smmu => fail.
  • kbdev-monaco-evk-multimedia: Probe_Failure_Check => fail.
  • kbdev-monaco-evk-multimedia: WiFi_Firmware_Driver => fail.
  • kbdev-monaco-evk-multimedia: WiFi_OnOff => fail.
  • kbdev-purwa-iot-evk-multimedia: KVM_EL2_DTB => fail.
  • kbdev-purwa-iot-evk-multimedia: KVM_Infra => fail.
  • kbdev-purwa-iot-evk-multimedia: gpdsp_remoteproc => skip.
  • kbdev-purwa-iot-evk-multimedia: Probe_Failure_Check => fail.
  • kbdev-purwa-iot-evk-multimedia: smmu => fail.
  • kbdev-purwa-iot-evk-multimedia: Ethernet_Basic_Validation => skip.
  • kbdev-qcs6490-rb3gen2-multimedia: gpdsp_remoteproc => skip.
  • kbdev-qcs6490-rb3gen2-multimedia: Probe_Failure_Check => fail.
  • kbdev-qcs6490-rb3gen2-multimedia: USBHost => skip.
  • kbdev-qcs6490-rb3gen2-multimedia: Ethernet_Basic_Validation => skip.
  • kbdev-qcs8300-ride-multimedia: Probe_Failure_Check => fail.
  • kbdev-qcs8300-ride-multimedia: Ethernet_Basic_Validation => skip.
  • kbdev-qcs8300-ride-multimedia: KVM_Driver => fail.
  • kbdev-qcs8300-ride-multimedia: KVM_EL2_DTB => fail.
  • kbdev-qcs8300-ride-multimedia: KVM_Infra => fail.
  • kbdev-qcs9100-ride-r3-multimedia: Probe_Failure_Check => fail.
  • kbdev-qcs9100-ride-r3-multimedia: smmu => fail.
  • kbdev-qcs9100-ride-r3-multimedia: Ethernet_Basic_Validation => fail.
  • kbdev-qcs9100-ride-r3-multimedia: KVM_Driver => fail.
  • kbdev-qcs9100-ride-r3-multimedia: KVM_EL2_DTB => fail.
  • kbdev-qcs9100-ride-r3-multimedia: KVM_Infra => fail.
  • kbdev-shikra-iqs-evk-multimedia: KVM_Infra => fail.
  • kbdev-shikra-iqs-evk-multimedia: adsp_remoteproc => skip.
  • kbdev-shikra-iqs-evk-multimedia: gpdsp_remoteproc => skip.
  • kbdev-shikra-iqs-evk-multimedia: GIC => fail.
  • kbdev-shikra-iqs-evk-multimedia: Probe_Failure_Check => fail.
  • kbdev-shikra-iqs-evk-multimedia: UFS_Validation => skip.
  • kbdev-shikra-iqs-evk-multimedia: PCIe => fail.
  • kbdev-shikra-iqs-evk-multimedia: USBHost => fail.
  • kbdev-shikra-iqs-evk-multimedia: KVM_Driver => fail.
  • kbdev-shikra-iqs-evk-multimedia: WiFi_OnOff => skip.
  • kbdev-shikra-iqs-evk-multimedia: DSP_AudioPD => skip.
  • kbdev-shikra-iqs-evk-multimedia: KVM_EL2_DTB => fail.

Unexpected failures

  • kbdev-monaco-evk-multimedia: Ethernet_Basic_Validation => skip.
  • kbdev-purwa-iot-evk-multimedia: BT_SCAN => fail.
  • kbdev-qcs8300-ride-multimedia: USBHost => fail.
  • kbdev-qcs8300-ride-multimedia: Audio_Card_Registration => skip.
  • kbdev-qcs9100-ride-r3-multimedia: Audio_Card_Registration => skip.
  • kbdev-qrb2210-rb1-multimedia did not produce a LAVA result artifact.
  • kbdev-shikra-iqs-evk-multimedia: Ethernet_Basic_Validation => fail.
  • kbdev-shikra-iqs-evk-multimedia: BT_SCAN => fail.
  • kbdev-shikra-iqs-evk-multimedia: Audio_Card_Registration => skip.

Result: blocked because unexpected failures were found.

@qlijarvis

Copy link
Copy Markdown

PR #1465 — validate-patch

PR: #1465

Verdict Issues Detailed Report
✅ 0 Full report

Final Summary

  1. Lore link present: Yes — all three commits link to https://lore.kernel.org/all/20261117-monaco-draco-v1-0-e42d1673148d@oss.qualcomm.com/
  2. Lore link matches PR commits: Yes — diff content is faithful to lore; only line number context differs due to tree state
  3. Upstream patch status: ⏳ Decision Pending — patches posted Nov 17, 2026 (today); no maintainer decision yet (no ACK/NAK/applied signals in thread)
  4. PR present in qcom-next/topics: Yes - all 3 commit(s) are present in qcom-next or topics
Verdict: ✅ — click to expand

🔍 Patch Validation

PR: #1465 - FROMLIST: arm64: dts: qcom: add Monaco Draco EVK board support (3 commits)
Upstream commit: https://lore.kernel.org/all/20261117-monaco-draco-v1-0-e42d1673148d@oss.qualcomm.com/
Verdict: ✅ PASS

Commit Message

Check Status Note
Subject matches upstream ✅ All three subjects correctly prefixed with FROMLIST:
Body preserves rationale ✅ All commit bodies faithfully preserve the lore descriptions
Fixes tag present/correct N/A No Fixes tags required (new board support)
Authorship preserved ✅ All commits: From: Faruque Ansari <faruque.ansari@oss.qualcomm.com> matches lore author; Co-developed-by used correctly for genuine co-authors in patches 2/3 and 3/3
Backport note (if applicable) N/A FROMLIST: prefix indicates patches posted to mailing list but not yet merged upstream

Diff

File Status Notes
Documentation/devicetree/bindings/arm/qcom.yaml ✅ Identical diff content; line number context differs (872 vs 472) due to tree state
arch/arm64/boot/dts/qcom/monaco-draco-ac-som.dtsi ✅ New file creation matches lore exactly (319 lines)
arch/arm64/boot/dts/qcom/Makefile ✅ Identical diff content; line number context differs (59 vs 69) due to tree state
arch/arm64/boot/dts/qcom/monaco-draco-evk.dts ✅ New file creation matches lore exactly (546 lines)

Verdict

Merge as-is. All three commits faithfully represent the upstream lore patches posted on Nov 17, 2026. The FROMLIST: prefix is correctly applied, authorship is preserved, Co-developed-by tags are used appropriately for genuine co-authors, and all Link tags point to the correct lore thread. Line number differences in context are expected due to the vendor tree having additional commits not present in the upstream tree at the time of posting.

Final Summary

  1. Lore link present: Yes — all three commits link to https://lore.kernel.org/all/20261117-monaco-draco-v1-0-e42d1673148d@oss.qualcomm.com/
  2. Lore link matches PR commits: Yes — diff content is faithful to lore; only line number context differs due to tree state
  3. Upstream patch status: ⏳ Decision Pending — patches posted Nov 17, 2026 (today); no maintainer decision yet (no ACK/NAK/applied signals in thread)
  4. PR present in qcom-next/topics: Yes — all 3 commits are present in qcom-next or topics per integration_presence_report.md (commit 1: partial in qcom-next + present in topics; commits 2-3: present in topics with exact patch-id match at d578789)

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

Commit Subject qcom-next topics Final
1/3 [PATCH 1/3] FROMLIST: dt-bindings: arm: qcom: add Monaco Draco EVK partial - subject or partial tree evidence found, but full change was not verified present - all checked added lines are present present
2/3 [PATCH 2/3] FROMLIST: arm64: dts: qcom: add Monaco Draco AC SoM missing - no subject, patch-id, or full tree-content match found present - exact patch-id match at d578789 present
3/3 [PATCH 3/3] FROMLIST: arm64: dts: qcom: add Monaco Draco EVK board missing - no subject, patch-id, or full tree-content match found present - all checked added lines are present present

Final Status

overall_status: PASS
present_commits: 3/3
partial_commits: 0/3
missing_commits: 0/3
topics_checked_for_commits: 3/3
final_summary: PR present in qcom-next/topics: Yes - all 3 commit(s) are present in qcom-next or topics

@qlijarvis

Copy link
Copy Markdown

PR #1465 — checker-log-analyzer

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

Checker Result Summary
Checker Result Summary
checkpatch ❌ 1 warning: undocumented vendor prefix "pci1179"
dt-binding-check ✅ Passed
dtb-check ⚠️ Pre-existing tree issues only (not caused by PR)
sparse-check ⏭️ Skipped (no C/H changes)
check-uapi-headers ⏭️ Skipped (no UAPI changes)
check-patch-compliance ❌ Link verification failed for all 3 commits
tag-check ✅ All commits have valid FROMLIST: prefix

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #1465 - Monaco Draco EVK board support
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/44009210710

Checker Result Summary
checkpatch ❌ 1 warning: undocumented vendor prefix "pci1179"
dt-binding-check ✅ Passed
dtb-check ⚠️ Pre-existing tree issues only (not caused by PR)
sparse-check ⏭️ Skipped (no C/H changes)
check-uapi-headers ⏭️ Skipped (no UAPI changes)
check-patch-compliance ❌ Link verification failed for all 3 commits
tag-check ✅ All commits have valid FROMLIST: prefix

❌ checkpatch

Root cause: Undocumented PCI vendor ID "pci1179" used in DTS compatible string.

Failure details:

Commit b0249ebca497 ("FROMLIST: arm64: dts: qcom: add Monaco Draco EVK board")
WARNING: DT compatible string vendor "pci1179" appears un-documented
#439: FILE: arch/arm64/boot/dts/qcom/monaco-draco-evk.dts:375:
+		compatible = "pci1179,0623";

Fix: Add the PCI vendor prefix to Documentation/devicetree/bindings/vendor-prefixes.yaml:

git rebase -i <base_sha>   # mark commit b0249ebca497 as 'edit'
# Edit Documentation/devicetree/bindings/vendor-prefixes.yaml
# Add entry: "^pci1179,.*": true  (or add proper vendor name if known)
git add Documentation/devicetree/bindings/vendor-prefixes.yaml
git commit --amend --no-edit
git rebase --continue

Note: PCI vendor ID 0x1179 is Toshiba. Consider using the proper vendor name entry:

  "^toshiba,.*":
    description: Toshiba Corporation

Reproduce locally:

./scripts/checkpatch.pl --strict --ignore FILE_PATH_CHANGES --git <base>..<head>

❌ check-patch-compliance

Root cause: b4 tool unable to fetch patches from the provided lore.kernel.org link.

Failure details:

Checking commit: FROMLIST: dt-bindings: arm: qcom: add Monaco Draco EVK board
Something seems wrong with the provided link. Please verify it
Try below command to run locally-
b4 am --single-message -C -l -3 https://lore.kernel.org/all/20261117-monaco-draco-v1-0-e42d1673148d@oss.qualcomm.com/

Checking commit: FROMLIST: arm64: dts: qcom: add Monaco Draco AC SoM
Something seems wrong with the provided link. Please verify it

Checking commit: FROMLIST: arm64: dts: qcom: add Monaco Draco EVK board
Something seems wrong with the provided link. Please verify it

Analysis: All three commits reference the same lore link (cover letter URL):

Link: https://lore.kernel.org/all/20261117-monaco-draco-v1-0-e42d1673148d@oss.qualcomm.com/

This is a cover letter message-ID, not individual patch message-IDs. The checker expects each commit to link to its specific patch in the series.

Fix: Update each commit's Link: trailer to point to the individual patch message-ID:

git rebase -i <base_sha>

# For each commit, mark as 'edit' and update the Link: line:
# Commit 1: Link: https://lore.kernel.org/all/20261117-monaco-draco-v1-1-e42d1673148d@oss.qualcomm.com/
# Commit 2: Link: https://lore.kernel.org/all/20261117-monaco-draco-v1-2-e42d1673148d@oss.qualcomm.com/
# Commit 3: Link: https://lore.kernel.org/all/20261117-monaco-draco-v1-3-e42d1673148d@oss.qualcomm.com/

git commit --amend
git rebase --continue

Alternative: If the patches haven't been posted to lore yet (future date 2026-11-17 suggests this may be a test/staging PR), the checker will always fail. In that case, either:

  1. Post the series to the mailing list first, then update the PR with correct message-IDs
  2. Accept that check-patch-compliance will fail for not-yet-posted patches

Reproduce locally:

b4 am --single-message -C -l -3 https://lore.kernel.org/all/20261117-monaco-draco-v1-1-e42d1673148d@oss.qualcomm.com/

⚠️ dtb-check

Root cause: Pre-existing tree issues in base monaco/qcs8300 device trees, not introduced by this PR.

Failure details:

The dtb-check log shows two categories of errors:

1. Pre-existing camera DTSI errors (NOT in this PR):

../arch/arm64/boot/dts/qcom/monaco-arduino-monza-camera.dtsi:526: Warning (reg_format)
../arch/arm64/boot/dts/qcom/monaco-arduino-monza-camera.dtsi:558: Warning (reg_format)
[... 30+ similar errors in monaco-arduino-monza-camera.dtsi ...]

These are from monaco-arduino-monza-camera.dtsi, which is not modified by this PR.

2. Pre-existing pinctrl/binding errors in base tree:

monaco-draco-evk.dtb: pinctrl@f100000 (qcom,qcs8300-tlmm): gp_mn_active-state: 'oneOf' conditional failed
  'gp_mn' is not one of ['aoss_cti', 'atest_char', ... 'vsense_trigger']

monaco-draco-evk.dtb: cci@ac13000 (qcom,qcs8300-cci): clock-names:0: 'ahb' was expected
monaco-draco-evk.dtb: pci@1c00000 (qcom,pcie-qcs8300): iommu-map:11: [1] is too short
monaco-draco-evk.dtb: phy@8909000 (qcom,qcs8300-dwmac-sgmii-phy): 'vdda-1p2-supply' does not match
monaco-draco-evk.dtb: video-codec@aa00000 (qcom,qcs8300-iris): Unevaluated properties ('video-firmware')

These errors reference nodes and properties that are not defined in the PR patch:

  • gp_mn_active-state — not present in monaco-draco-evk.dts or monaco-draco-ac-som.dtsi
  • CCI clock-names, PCIe iommu-map, SGMII PHY supply, video-codec — all inherited from base qcs8300.dtsi / monaco.dtsi

Verification: Confirmed by searching the PR patch:

grep "gp_mn" pr.patch          # No results
grep "monaco-arduino" pr.patch # No results

Conclusion: These are pre-existing tree issues that get exposed when building the new DTBs because they inherit from base SoC device trees with schema validation errors. The PR itself does not introduce any new dtb-check failures.

Action: No fix required in this PR. These issues should be addressed separately in the base monaco/qcs8300 device tree files.


Verdict

2 blockers to fix before merge:

  1. checkpatch: Add PCI vendor prefix "pci1179" (Toshiba) to vendor-prefixes.yaml
  2. check-patch-compliance: Update Link: trailers to point to individual patch message-IDs instead of cover letter

Non-blocking:

  • dtb-check failures are pre-existing tree issues, not caused by this PR
  • All commits have valid FROMLIST: prefix (tag-check passes)

@qlijarvis

Copy link
Copy Markdown

LAVA Failed Case Triage Summary

PR: #1465

Job 283041 | SoC qcs9100-ride

LAVA job: https://lava-oss.qualcomm.com/scheduler/job/283041

Failed test cases in LAVA job 283041 (SoC: qcs9100-ride).

  Case 1: Probe_Failure_Check
  1. Failed case: Probe_Failure_Check
  2. Root cause: Three pre-existing platform issues on qcs9100-ride unrelated to the PR: (1) nvmem-reboot-mode driver deferred probe due to missing nvmem cell "reboot-mode" in device tree, (2) cfg80211 regulatory.db firmware file missing (benign - regulatory database is optional), and (3) Aquantia AQR115C Ethernet PHY probe failure with -EINVAL due to missing or invalid firmware-name property in device tree. The PR adds Monaco Draco EVK (QCS8300) device tree support and does not modify qcs9100-ride platform files.
  3. Possible fix: These are pre-existing qcs9100-ride platform issues, not regressions introduced by this PR. The PR should be approved as it does not affect qcs9100-ride. To fix the underlying platform issues: (1) add nvmem cell "reboot-mode" to qcs9100-ride device tree, (2) optionally add regulatory.db firmware file to rootfs (or suppress this benign warning), and (3) add valid firmware-name property to the Aquantia PHY node in qcs9100-ride device tree or verify PHY hardware compatibility.
  4. Detail analysis attachment: failed_case_job283041_1_detailed.md
  Case 2: smmu
  1. Failed case: smmu
  2. Root cause: The video codec device aa00000.video-codec on qcs9100-ride is not attached to any IOMMU group, causing the SMMU test's critical master protection check to fail. This is a pre-existing platform configuration issue unrelated to the PR, which only adds device tree support for the Monaco Draco EVK (QCS8300-based board).
  3. Possible fix: Add the missing iommus property to the video codec device tree node for qcs9100 SoC. The device tree should specify the appropriate SMMU stream ID mapping for aa00000.video-codec to ensure it is attached to an IOMMU group during kernel boot.
  4. Detail analysis attachment: failed_case_job283041_2_detailed.md
  Case 3: Ethernet_Basic_Validation
  1. Failed case: Ethernet_Basic_Validation
  2. Root cause: Could not be determined confidently from available logs.
  3. Possible fix: Verify the device tree for qcs9100-ride (Lemans Ride Rev3) contains a valid MDIO child node under the ethernet@23040000 node with the correct PHY address and compatible string. Ensure the PHY driver for the hardware PHY on this board is enabled in the kernel config and that the phy-handle property correctly references the PHY node. If the PHY is not being enumerated on the MDIO bus, add debug logging to confirm MDIO bus registration and PHY detection, or check for missing PHY reset GPIO configuration.
  4. Detail analysis attachment: failed_case_job283041_3_detailed.md
  Case 4: KVM_Driver
  1. Failed case: KVM_Driver
  2. Root cause: Kernel booted at EL1 instead of EL2; KVM requires EL2 to create /dev/kvm device node. The qcs9100-ride test platform is not configured to boot with an EL2 device tree overlay.
  3. Possible fix: Configure the LAVA job for qcs9100-ride to use an EL2-enabled device tree (e.g., lemans-ride-el2.dtb or equivalent overlay) if KVM testing is required on this platform, or skip KVM tests on platforms that boot at EL1.
  4. Detail analysis attachment: failed_case_job283041_4_detailed.md
  Case 5: KVM Driver Initialization Failure — /dev/kvm not available
  1. Failed case: KVM Driver Initialization Failure — /dev/kvm not available
  2. Root cause: KVM cannot initialize on qcs9100-ride because the platform boots with Gunyah hypervisor already running at EL2, preventing KVM from taking control of EL2 (message: "kvm [1]: HYP mode not available"). This is a platform configuration issue, not a PR-introduced regression.
  3. Possible fix: Exclude KVM tests from the qcs9100-ride LAVA test suite, as this platform is configured to run Gunyah hypervisor and cannot support KVM. Alternatively, if KVM support is required, reconfigure the platform firmware to boot without Gunyah hypervisor.
  4. Detail analysis attachment: failed_case_job283041_5_detailed.md
  Case 6: ** KVM_Infra — Platform Capability Limitation
  1. Failed case: ** KVM_Infra — Platform Capability Limitation
  2. Root cause: ** The qcs9100-ride (Lemans) platform does not support ARM EL2/HYP mode, which is required for KVM. Kernel message at boot (line 3256): kvm [1]: HYP mode not available. CONFIG_KVM is enabled but runtime initialization fails due to missing platform virtualization support.
  3. Possible fix: Exclude KVM tests from qcs9100-ride CI runs, or configure the platform to boot at EL2 if hardware supports it. This is not a kernel bug or PR-introduced issue — it's a platform limitation. The PR adds Monaco Draco DT support (unrelated platform) and does not affect qcs9100-ride.
  4. Detail analysis attachment: failed_case_job283041_6_detailed.md
  Case 7: KVM_Infra — Platform KVM Infrastructure Test
  1. Failed case: KVM_Infra — Platform KVM Infrastructure Test
  2. Root cause: The qcs9100-ride (LeMans Ride Rev3) platform is not configured to boot the kernel in EL2/HYP mode. The bootloader message "HypDtFixupEntryPoint : Skipping overlay of hyp dt nodes for non-Gunyah hypervisor" and kernel message "kvm [1]: HYP mode not available" confirm that the platform boots in EL1 (non-HYP mode), preventing KVM initialization and /dev/kvm device creation. This is a pre-existing platform/firmware configuration issue, not introduced by PR arm64: dts: qcom: add Monaco Draco EVK board support #1465 (which adds Monaco Draco QCS8300 device tree support).
  3. Possible fix: Configure the qcs9100-ride platform firmware/bootloader to boot the kernel in EL2/HYP mode by enabling the appropriate boot configuration flag (OsConfigTableSelectionFlag). For Qualcomm platforms, this typically requires: (1) building and flashing a device tree overlay that enables EL2 boot (e.g., lemans-ride-el2.dtbo), (2) updating the bootloader configuration to select the EL2 boot path, or (3) using a firmware build that supports KVM/virtualization. Alternatively, if KVM is not required on this platform, mark the KVM_Infra test as expected-to-fail or skip it in the LAVA job definition for qcs9100-ride.
  4. Detail analysis attachment: failed_case_job283041_7_detailed.md
Job 283042 | SoC shikra-iqs-evk

LAVA job: https://lava-oss.qualcomm.com/scheduler/job/283042

Failed test cases in LAVA job 283042 (SoC: shikra-iqs-evk).

  Case 1: GIC Test Script Bug — False Failure on 4-CPU Platform
  1. Failed case: GIC Test Script Bug — False Failure on 4-CPU Platform
  2. Root cause: The GIC test script assumes an 8-CPU system and attempts to validate timer interrupt increments on CPUs 4-7, but the shikra-iqs-evk platform has only 4 CPUs (0-3); the script's bash integer comparison at line 75 fails when parsing /proc/interrupts columns that don't exist, producing "integer expected" errors for non-existent CPU columns.
  3. Possible fix: Update the GIC test script to dynamically detect the number of online CPUs from /sys/devices/system/cpu/online or /proc/cpuinfo and only validate timer interrupts for CPUs that actually exist on the platform, rather than hardcoding an assumption of 8 CPUs.
  4. Detail analysis attachment: failed_case_job283042_1_detailed.md
  Case 2: Probe_Failure_Check — Pre-existing Platform Probe Failures
  1. Failed case: Probe_Failure_Check — Pre-existing Platform Probe Failures
  2. Root cause: The Probe_Failure_Check test detected four pre-existing probe failures on shikra-iqs-evk that are unrelated to the PR changes (which add Monaco Draco QCS8300 device tree support): (1) ucsi_ccg USB-C controller missing firmware file ccg_secondary.cyacd2 (-ENOENT), (2) tpm_tis_spi TPM probe timeout (-ETIMEDOUT), (3) regulatory.db WiFi regulatory database missing (-ENOENT), and (4) three deferred probe entries (sound/snd-sc8280xp, I2C device 3-0010, va_macro codec) that remain unresolved at test time due to missing dependencies (CPU DAI name, mclk clock).
  3. Possible fix: These are known platform-specific issues on shikra-iqs-evk and are NOT regressions introduced by PR arm64: dts: qcom: add Monaco Draco EVK board support #1465. The PR only adds device tree files for Monaco Draco (QCS8300), which does not affect shikra-evk. No action required for this PR. To resolve the underlying platform issues: (1) add ccg_secondary.cyacd2 firmware to rootfs firmware directory, (2) investigate TPM SPI bus configuration and timing on shikra DT, (3) add regulatory.db to rootfs (or disable CFG80211_REQUIRE_SIGNED_REGDB if not needed), (4) fix audio subsystem DT to provide correct CPU DAI references and mclk clock bindings for va_macro codec.
  4. Detail analysis attachment: failed_case_job283042_2_detailed.md
  Case 3: PCIe
  1. Failed case: PCIe
  2. Root cause: Could not be determined confidently from available logs.
  3. Possible fix: Update the PCIe test script to SKIP (not FAIL) when QPS615 vendor firmware is absent, since this is an optional hardware-specific feature. The test already correctly validates core PCIe functionality (enumeration, link training, MSI, runtime power) which all passed. Alternatively, add the TC956X firmware and tc956x_pcie_eth driver to the test rootfs if QPS615 Ethernet validation is required.
  4. Detail analysis attachment: failed_case_job283042_3_detailed.md
  Case 4: USBHost
  1. Failed case: USBHost
  2. Root cause: Could not be determined confidently from available logs.
  3. Possible fix: Update the LAVA test job definition for shikra-iqs-evk to skip the USBHost test or configure it to validate USB gadget/peripheral mode instead of host mode. Alternatively, if host mode is required for this platform, update the device tree to set dr_mode = "host" or dr_mode = "otg" for the USB controllers.
  4. Detail analysis attachment: failed_case_job283042_4_detailed.md
  Case 5: Ethernet_Basic_Validation
  1. Failed case: Ethernet_Basic_Validation
  2. Root cause: Network connectivity test failure on shikra-iqs-evk eth1 interface — link layer operational (carrier=1, IP=10.143.233.236, 1000Mb/s full-duplex) but ICMP ping to gateway 10.143.232.1 fails with 100% packet loss across 3 retry attempts, indicating either LAVA lab network infrastructure issue (gateway unreachable, firewall blocking ICMP, ARP resolution failure) or test target misconfiguration.
  3. Possible fix: This is not a PR-introduced regression — the PR adds Monaco Draco (QCS8300) device tree support and does not modify shikra-iqs-evk (QCS8550) Ethernet driver or configuration. Verify LAVA lab network: (1) confirm gateway 10.143.232.1 is reachable from the lab network segment, (2) check for ICMP filtering/firewall rules blocking ping from 10.143.233.236, (3) verify ARP table on target can resolve gateway MAC address, (4) re-trigger the CI job to rule out transient network issue.
  4. Detail analysis attachment: failed_case_job283042_5_detailed.md
  Case 6: BT_SCAN — Test Environment Issue (No Discoverable Devices)
  1. Failed case: BT_SCAN — Test Environment Issue (No Discoverable Devices)
  2. Root cause: Bluetooth hardware and firmware are fully functional (BT_ON_OFF passed, hci0 operational, discovery started/stopped successfully), but no Bluetooth devices were present in the LAVA lab environment during the 3 scan attempts (15s each) to be discovered by the shikra-iqs-evk board.
  3. Possible fix: This is not a kernel regression — the PR adds Monaco Draco EVK board support unrelated to shikra-iqs-evk Bluetooth. Ensure discoverable Bluetooth devices (phones, beacons, or test dongles) are powered on and within range of the shikra-iqs-evk board in the LAVA lab before running BT_SCAN tests, or mark BT_SCAN as optional when no target device is configured.
  4. Detail analysis attachment: failed_case_job283042_6_detailed.md
  Case 7: KVM_Driver
  1. Failed case: KVM_Driver
  2. Root cause: KVM initialization failed because the kernel is running under Gunyah hypervisor which does not expose EL2 (HYP mode) to the guest kernel; the kernel message "kvm [1]: HYP mode not available" indicates KVM detected it cannot access the required virtualization extensions on shikra-iqs-evk.
  3. Possible fix: This is a platform/board configuration issue, not a kernel regression introduced by PR arm64: dts: qcom: add Monaco Draco EVK board support #1465 (which only adds Monaco Draco device tree support). The shikra-iqs-evk board runs under Gunyah hypervisor by default, which prevents nested virtualization. To enable KVM on this platform: (1) boot the kernel at EL2 instead of under a hypervisor, or (2) use a hypervisor configuration that supports nested virtualization and exposes EL2 to the guest, or (3) exclude KVM tests from the shikra-iqs-evk test suite as they are not applicable to this hypervisor-based platform configuration.
  4. Detail analysis attachment: failed_case_job283042_7_detailed.md
  Case 8: KVM_EL2_DTB
  1. Failed case: KVM_EL2_DTB
  2. Root cause: Could not be determined confidently from available logs.
  3. Possible fix: Skip KVM tests on Shikra IQS EVK in the LAVA job definition, or reconfigure the platform to boot without Gunyah hypervisor if KVM testing is required. Add a test skip condition: if Gunyah hypervisor is detected at boot (grep "Hypervisor cold boot.*gunyah" dmesg), skip all KVM test cases with result=skip instead of result=fail.
  4. Detail analysis attachment: failed_case_job283042_8_detailed.md
  Case 9: KVM_Infra — Test Infrastructure Misconfiguration
  1. Failed case: KVM_Infra — Test Infrastructure Misconfiguration
  2. Root cause: The Shikra IQS EVK board was flashed with the standard shikra-iqs-evk.dtb which boots the kernel at EL1 (kernel exception level). KVM requires the kernel to boot at EL2 (hypervisor exception level) to enable virtualization support. The kernel correctly reports kvm [1]: HYP mode not available during initialization, and consequently /dev/kvm is not created. This is not a kernel regression — it is a test environment configuration issue where KVM tests are being run on a board that was not flashed with an EL2-enabled DTB variant.
  3. Possible fix: Flash the board with an EL2-enabled DTB variant (e.g., shikra-iqs-evk-el2.dtb if available) to boot the kernel at EL2, or exclude KVM tests from the test suite for boards flashed with standard (EL1) DTBs. To verify if an EL2 DTB variant exists for Shikra IQS EVK, check the kernel tree for arch/arm64/boot/dts/qcom/shikra-*-el2.dts or similar overlay files. If no EL2 variant exists for this board, KVM tests should be marked as "not applicable" for this platform configuration.
  4. Detail analysis attachment: failed_case_job283042_9_detailed.md
  Case 10: ** KVM_Infra (test infrastructure limitation, not a kernel bug)
  1. Failed case: ** KVM_Infra (test infrastructure limitation, not a kernel bug)
  2. Root cause: ** KVM is unavailable because the kernel booted at EL1 (normal mode) instead of EL2 (hypervisor mode). The shikra-iqs-evk LAVA job configuration does not boot the kernel at EL2, and a Gunyah hypervisor is present running at EL2, preventing KVM from initializing. This is expected behavior for this board configuration.
  3. Possible fix: This is not a failure requiring a code fix. The test result correctly reflects the platform configuration. To enable KVM on shikra-iqs-evk, the LAVA job definition must be updated to use an EL2 device tree overlay (e.g., shikra-iqs-evk-el2.dtb) that boots the kernel at EL2 without a hypervisor, or the KVM tests should be skipped for boards that boot with a hypervisor at EL2. The PR itself does not introduce any regression.
  4. Detail analysis attachment: failed_case_job283042_10_detailed.md
Job 283043 | SoC monaco-evk

LAVA job: https://lava-oss.qualcomm.com/scheduler/job/283043

Failed test cases in LAVA job 283043 (SoC: monaco-evk).

  Case 1: ** Probe_Failure_Check (WiFi firmware/driver probe failure)
  1. Failed case: ** Probe_Failure_Check (WiFi firmware/driver probe failure)
  2. Root cause: ** Missing WiFi firmware file ath11k/WCN6855/hw2.1/nfa765/amss.bin in the Monaco EVK rootfs image, causing ath11k_pci driver probe to fail with -110 (ETIMEDOUT) after MHI firmware load failed with -2 (ENOENT).
  3. Possible fix: Install the missing WiFi firmware package (linux-firmware or qcom-firmware) in the rootfs image used for Monaco EVK LAVA testing, ensuring ath11k/WCN6855/hw2.1/nfa765/amss.bin is present in /lib/firmware/.
  4. Detail analysis attachment: failed_case_job283043_1_detailed.md
  Case 2: WiFi Driver Probe Failure — ath11k_pci firmware load timeout
  1. Failed case: WiFi Driver Probe Failure — ath11k_pci firmware load timeout
  2. Root cause: The ath11k_pci driver probe failed with error -110 (ETIMEDOUT) on monaco-evk because the required WiFi firmware file ath11k/WCN6855/hw2.1/nfa765/amss.bin is missing from the rootfs. The MHI (Modem Host Interface) subsystem attempted to load the firmware but failed with error -2 (ENOENT - file not found), causing the driver initialization to time out waiting for the firmware handshake. This is a pre-existing platform/rootfs issue on monaco-evk, not introduced by PR arm64: dts: qcom: add Monaco Draco EVK board support #1465 which only adds a new board (monaco-draco-evk).
  3. Possible fix: Add the missing ath11k WiFi firmware files for WCN6855 hw2.1 (specifically ath11k/WCN6855/hw2.1/nfa765/amss.bin and related firmware blobs) to the monaco-evk rootfs image. The firmware package should be included in the Yocto build recipe or manually installed in /lib/firmware/ on the target. Verify the firmware path matches the driver's request path exactly.
  4. Detail analysis attachment: failed_case_job283043_2_detailed.md
  Case 3: WiFi_OnOff — ath11k_pci Driver Probe Failure (Firmware Missing)
  1. Failed case: WiFi_OnOff — ath11k_pci Driver Probe Failure (Firmware Missing)
  2. Root cause: The ath11k_pci driver probe failed with error -110 (ETIMEDOUT) because the required firmware file ath11k/WCN6855/hw2.1/nfa765/amss.bin is missing from the rootfs (error -2 = ENOENT). MHI (Modem Host Interface) failed to load the firmware, causing the power-up sequence to timeout, which cascaded into probe failure. This is a pre-existing platform/infrastructure issue on monaco-evk, not introduced by PR arm64: dts: qcom: add Monaco Draco EVK board support #1465 (which only adds device tree support for Monaco Draco, a different board).
  3. Possible fix: Add the missing firmware file ath11k/WCN6855/hw2.1/nfa765/amss.bin to the rootfs firmware directory (/lib/firmware/ath11k/WCN6855/hw2.1/nfa765/). This is a build/image packaging issue — the firmware blob must be included in the Yocto/distro build recipe for monaco-evk. Alternatively, if the nfa765 variant is not the correct one for this board, update the device tree or board-specific configuration to point to the correct firmware variant path.
  4. Detail analysis attachment: failed_case_job283043_3_detailed.md
  Case 4: 0_qcom-next-ci-premerge-tests
  1. Failed case: 0_qcom-next-ci-premerge-tests
  2. Root cause: ath11k_pci WiFi driver probe timeout (error -110) on monaco-evk board — WCN6855 PCIe device at 0000:01:00.0 failed to initialize during boot, causing cascading failures in Probe_Failure_Check, WiFi_Firmware_Driver, and WiFi_OnOff tests. This is a pre-existing hardware/driver initialization issue on the monaco-evk platform, not introduced by PR arm64: dts: qcom: add Monaco Draco EVK board support #1465 which only adds monaco-draco-evk board support.
  3. Possible fix: This is a pre-existing monaco-evk platform issue unrelated to the PR changes. The PR adds monaco-draco-evk board files and does not modify WiFi, PCIe, or ath11k drivers. Recommend: (1) Re-run CI on monaco-draco-evk target (the board this PR actually adds) instead of monaco-evk, or (2) Accept this known monaco-evk WiFi initialization issue as a baseline failure and approve the PR based on its actual scope (new board DT files). For the underlying WiFi issue: investigate WCN6855 PCIe link training, MHI firmware load timeout, and power sequencing on monaco-evk hardware.
  4. Detail analysis attachment: failed_case_job283043_4_detailed.md
Job 283044 | SoC qcs6490-rb3gen2

LAVA job: https://lava-oss.qualcomm.com/scheduler/job/283044

Failed test cases in LAVA job 283044 (SoC: qcs6490-rb3gen2).

  Case 1: Probe_Failure_Check
  1. Failed case: Probe_Failure_Check
  2. Root cause: Could not be determined confidently from available logs.
  3. Possible fix: Update the rootfs image used in LAVA CI to include the missing firmware files: (1) add regulatory.db to /lib/firmware/ (from linux-firmware package or kernel source net/wireless/db.txt); (2) add renesas_usb_fw.mem to /lib/firmware/ (from linux-firmware package). These are standard firmware files required for wireless regulatory compliance and Renesas USB controllers, respectively. The PR itself is correct and does not require changes.
  4. Detail analysis attachment: failed_case_job283044_1_detailed.md
  Case 2: Probe_Failure_Check
  1. Failed case: Probe_Failure_Check
  2. Root cause: Pre-existing firmware packaging gaps on qcs6490-rb3gen2 platform — missing regulatory.db (wireless regulatory database) and renesas_usb_fw.mem (Renesas USB 3.0 controller firmware). These are infrastructure issues unrelated to PR arm64: dts: qcom: add Monaco Draco EVK board support #1465 (Monaco Draco QCS8300 device tree additions).
  3. Possible fix: Add missing firmware files to the rootfs image: install linux-firmware package or manually add /lib/firmware/regulatory.db and /lib/firmware/renesas_usb_fw.mem to the test image. This is a test infrastructure fix, not a kernel code fix. PR arm64: dts: qcom: add Monaco Draco EVK board support #1465 can proceed to merge as these failures are not regressions introduced by the PR.
  4. Detail analysis attachment: failed_case_job283044_2_detailed.md
Job 283045 | SoC qcs615-ride

LAVA job: https://lava-oss.qualcomm.com/scheduler/job/283045

Failed test cases in LAVA job 283045 (SoC: qcs615-ride).

  Case 1: deploy-flasher
  1. Failed case: deploy-flasher
  2. Root cause: Could not be determined confidently from available logs.
  3. Possible fix: Re-trigger the CI job after verifying the qcs615-ride board (serial 98000207100D0224) is physically connected, powered, and accessible to the LAVA worker. If the issue persists, check the debug board USB connection to the LAVA worker, verify the debug board firmware is responsive, and confirm the board serial number is correctly registered in the LAVA device configuration. This is a LAVA lab infrastructure issue, not a kernel or build artifact problem.
  4. Detail analysis attachment: failed_case_job283045_1_detailed.md
  Case 2: Build Load Failure — Debug board hardware unavailable
  1. Failed case: Build Load Failure — Debug board hardware unavailable
  2. Root cause: Result: Build Load Failure. The LAVA deploy-flasher action failed because the debug board control script (debugboard.py) could not locate the qcs615-ride board with serial number 98000207100D0224. Error: ValueError: Could not find the board with Serial number: 98000207100D0224. This is a LAVA lab infrastructure issue, not a kernel or build artifact problem.
  3. Possible fix: Verify the qcs615-ride board (serial 98000207100D0224) is physically connected to the LAVA worker, powered on, and its debug board USB interface is accessible. Check the board's assignment in LAVA device configuration. If the board is offline or in maintenance, reassign the job to a different qcs615-ride board or wait for the board to be restored. Re-trigger the CI job once board connectivity is confirmed.
  4. Detail analysis attachment: failed_case_job283045_2_detailed.md
  Case 3: Build Load Failure — Hardware control infrastructure failure (debugboard unavailable)
  1. Failed case: Build Load Failure — Hardware control infrastructure failure (debugboard unavailable)
  2. Root cause: Result: Build Load Failure. The LAVA dispatcher failed to communicate with the debug board controller (serial 98000207100D0224) during the deploy-flasher pre-flash power-off step. The debugboard.py script raised "ValueError: Could not find the board with Serial number: 98000207100D0224" indicating the debug board is not enumerated on the LAVA worker's USB bus or is in an unresponsive state. This is a LAVA infrastructure issue, not a kernel or build artifact problem.
  3. Possible fix: Report this hardware availability issue to the LAVA lab administrators for the qcs615-ride board with serial 98000207100D0224. The debug board USB connection should be verified, the board may need power cycling, or the debugboard.py enumeration logic may need investigation. Re-trigger the CI job once the board is confirmed available in the lab inventory.
  4. Detail analysis attachment: failed_case_job283045_3_detailed.md
  Case 4: Build Load Failure — Debugboard hardware connection failure
  1. Failed case: Build Load Failure — Debugboard hardware connection failure
  2. Root cause: LAVA infrastructure failure during deploy-flasher action. The debugboard.py script could not establish connection to the qcs615-ride board (serial 98000207100D0224), preventing the flash operation from starting. Error: "ValueError: Could not find the board with Serial number: 98000207100D0224".
  3. Possible fix: This is a LAVA lab infrastructure issue, not a kernel or PR-introduced problem. The board is either physically disconnected, powered off, or the debugboard USB connection is not available to the LAVA worker. Contact LAVA lab administrators to verify board connectivity and debugboard hardware status for qcs615-ride serial 98000207100D0224. Re-trigger the CI job after confirming board availability.
  4. Detail analysis attachment: failed_case_job283045_4_detailed.md
Job 283046 | SoC purwa-evk

LAVA job: https://lava-oss.qualcomm.com/scheduler/job/283046

Failed test cases in LAVA job 283046 (SoC: purwa-evk).

  Case 1: ** Probe_Failure_Check
  1. Failed case: ** Probe_Failure_Check
  2. Root cause: ** Six driver probe failures detected on Purwa EVK (X1E80100 SoC): PCIe controllers (error -61, missing PHY config data), QSEECOM UEFI app (error -16, secure world resource conflict), FastRPC/QRTR (error -12, glink endpoint creation failure), and regulatory.db firmware (error -2, missing optional file). All failures are pre-existing platform-specific hardware/configuration issues unrelated to the PR, which only adds device tree files for a different SoC (QCS8300 Monaco Draco).
  3. Possible fix: Suppress these probe failures in the Probe_Failure_Check test for Purwa EVK as known platform limitations. For proper resolution: (1) add missing PCIe PHY tuning properties to Purwa EVK device tree, (2) investigate TrustZone firmware configuration for QSEECOM, (3) fix ADSP glink channel initialization timing or add probe dependency ordering for FastRPC/QRTR, (4) install regulatory.db firmware or mark as optional. These platform-specific fixes should be separate commits targeting X1E80100 support, not part of the QCS8300 PR.
  4. Detail analysis attachment: failed_case_job283046_1_detailed.md
  Case 2: smmu
  1. Failed case: smmu
  2. Root cause: Video codec device (aa00000.video-codec) missing iommus property in purwa-evk device tree, preventing IOMMU group attachment during kernel boot; this is a pre-existing platform DT configuration gap, not a regression introduced by PR arm64: dts: qcom: add Monaco Draco EVK board support #1465 (which adds Monaco Draco EVK support).
  3. Possible fix: Add iommus = <&apps_smmu 0x... 0x0>; property to the video-codec node in arch/arm64/boot/dts/qcom/qcs8300.dtsi (or purwa-evk-specific dtsi) to enable IOMMU protection for the video codec master.
  4. Detail analysis attachment: failed_case_job283046_2_detailed.md
  Case 3: ** BT_SCAN — Bluetooth Device Discovery Failure
  1. Failed case: ** BT_SCAN — Bluetooth Device Discovery Failure
  2. Root cause: ** Bluetooth scan unable to discover nearby devices despite functional Bluetooth stack (hci0 adapter operational, BT_ON_OFF passed). Concurrent DPU (Display Processing Unit) vblank timeout storm (hundreds of timeout errors during scan window) suggests system resource contention or interrupt delivery issues on purwa-evk platform may be interfering with Bluetooth scan timing.
  3. Possible fix: This is a pre-existing purwa-evk platform issue unrelated to PR#1465 (which adds Monaco Draco EVK support for a different SoC). Investigate DPU/display driver on purwa-evk: check if display is incorrectly enabled in test environment, verify interrupt routing for both DPU and Bluetooth, and consider disabling display output during connectivity tests to eliminate resource contention. Re-run BT_SCAN test with display subsystem disabled (video=off kernel parameter) to isolate root cause.
  4. Detail analysis attachment: failed_case_job283046_3_detailed.md
  Case 4: KVM_EL2_DTB
  1. Failed case: KVM_EL2_DTB
  2. Root cause: KVM requires the kernel to boot at EL2 (hypervisor exception level) to enable virtualization support. On purwa-evk, the Gunyah hypervisor is running and the kernel boots at EL1, causing KVM initialization to fail with "HYP mode not available". The bootloader log shows "Dtb apply overlay skipped", indicating the EL2 device tree overlay was not applied to enable EL2 boot mode.
  3. Possible fix: Configure the LAVA job or bootloader to apply the EL2 device tree overlay for purwa-evk before booting the kernel. For purwa-evk, ensure the boot configuration selects the -el2 variant DTB (similar to how monaco-evk uses monaco-evk-el2.dtb) to boot the kernel at EL2 instead of EL1, allowing KVM to initialize successfully.
  4. Detail analysis attachment: failed_case_job283046_4_detailed.md
  Case 5: KVM_Infra — KVM Infrastructure Test Failure
  1. Failed case: KVM_Infra — KVM Infrastructure Test Failure
  2. Root cause: KVM driver initialization failed because HYP (EL2) mode is not available on the purwa-evk platform. The kernel message kvm [1]: HYP mode not available at boot time (5.963s) indicates the ARM virtualization extensions are either not present, disabled in firmware, or the kernel is running at EL1 under a hypervisor that does not expose nested virtualization. CONFIG_KVM is enabled in the kernel configuration, but the hardware/firmware prerequisite for KVM operation (EL2 access) is not met on this SoC/board combination.
  3. Possible fix: This is a platform/firmware limitation, not a kernel bug or PR-introduced regression. The purwa-evk board does not support KVM because EL2 is not available to the Linux kernel. To resolve: (1) verify the bootloader/firmware configuration allows EL2 access to the kernel (check ABL/XBL settings and ensure the kernel is booted at EL2, not EL1); (2) if the platform is intentionally running under a hypervisor, KVM nested virtualization must be enabled in the host hypervisor; (3) if the SoC does not support virtualization extensions, mark KVM tests as "skip" for this platform in the LAVA test plan rather than "fail"; (4) confirm with the platform team whether purwa-evk is expected to support KVM/virtualization.
  4. Detail analysis attachment: failed_case_job283046_5_detailed.md
  Case 6: LAVA Test Runner Completion Signal Not Recognized (Infrastructure Issue)
  1. Failed case: LAVA Test Runner Completion Signal Not Recognized (Infrastructure Issue)
  2. Root cause: LAVA test runner successfully completed and sent <LAVA_TEST_RUNNER EXIT> signal, but LAVA dispatcher marked the test run as "unfinished" due to internal state tracking failure in the LAVA infrastructure, not a kernel or PR-introduced issue.
  3. Possible fix: Re-trigger the LAVA job; this is a known transient LAVA infrastructure issue where the test completion signal is not properly recognized by the dispatcher despite successful test execution.
  4. Detail analysis attachment: failed_case_job283046_6_detailed.md
Job 283047 | SoC lemans-evk

LAVA job: https://lava-oss.qualcomm.com/scheduler/job/283047

Failed test cases in LAVA job 283047 (SoC: lemans-evk).

  Case 1: Probe_Failure_Check
  1. Failed case: Probe_Failure_Check
  2. Root cause: Could not be determined confidently from available logs.
  3. Possible fix: Add the missing nvmem cell "reboot-mode" to the lemans-evk device tree (sa8775p-lemans-evk.dts or sa8775p.dtsi), referencing the appropriate TCSR or SRAM nvmem provider. This is a lemans-evk platform fix, independent of PR arm64: dts: qcom: add Monaco Draco EVK board support #1465.
  4. Detail analysis attachment: failed_case_job283047_1_detailed.md
  Case 2: smmu
  1. Failed case: smmu
  2. Root cause: The video codec device (aa00000.video-codec) is not attached to any IOMMU group during kernel boot on lemans-evk, causing the SMMU test to fail its critical master protection check. The device probes successfully and is functional (firmware loads, driver initializes), but the IOMMU subsystem does not create a group assignment for this device.
  3. Possible fix: Add the missing iommus property to the video-codec device tree node in the lemans-evk device tree (or the base SoC dtsi if applicable to all lemans variants). The property should reference the appropriate SMMU instance and stream ID for the video codec hardware block. Verify the fix by confirming "platform aa00000.video-codec: Adding to iommu group N" appears in the kernel boot log.
  4. Detail analysis attachment: failed_case_job283047_2_detailed.md
  Case 3: 0_qcom-next-ci-premerge-tests
  1. Failed case: 0_qcom-next-ci-premerge-tests
  2. Root cause: LAVA test definition marked as failed because 2 individual test cases failed: (1) Probe_Failure_Check detected deferred probe issue (nvmem-reboot-mode cell missing) and firmware load failures (regulatory.db, Bluetooth firmware), and (2) smmu detected Video codec (aa00000.video-codec) missing IOMMU group attachment on lemans-evk.
  3. Possible fix: For Probe_Failure_Check: Add nvmem reboot-mode cell to lemans-evk device tree and ensure regulatory.db and Bluetooth firmware files are present in rootfs. For smmu: Add IOMMU binding for video-codec@aa00000 node in lemans-evk device tree to attach it to an IOMMU group.
  4. Detail analysis attachment: failed_case_job283047_3_detailed.md
Job 283049 | SoC qcs8300-ride

LAVA job: https://lava-oss.qualcomm.com/scheduler/job/283049

Failed test cases in LAVA job 283049 (SoC: qcs8300-ride).

  Case 1: Probe_Failure_Check
  1. Failed case: Probe_Failure_Check
  2. Root cause: Two pre-existing platform-specific probe failures on qcs8300-ride: (1) xhci-hcd driver timeout (-ETIMEDOUT, error -110) during USB host controller setup, indicating hardware not responding within expected timeframe; (2) regulatory.db firmware file missing from rootfs (-ENOENT, error -2), a known benign WiFi regulatory database load failure that does not affect WiFi functionality (ath11k WiFi driver subsequently probes successfully).
  3. Possible fix: Mark this test case as PASS with suppression note — both failures are pre-existing qcs8300-ride platform issues unrelated to the PR changes (PR only adds Monaco Draco EVK board files and does not modify qcs8300-ride DT, drivers, or kernel code). The xhci-hcd timeout is a known hardware/firmware timing issue on this platform; the regulatory.db missing file is a rootfs packaging issue. Neither failure is a regression introduced by PR arm64: dts: qcom: add Monaco Draco EVK board support #1465.
  4. Detail analysis attachment: failed_case_job283049_1_detailed.md
  Case 2: USBHost
  1. Failed case: USBHost
  2. Root cause: Could not be determined confidently from available logs.
  3. Possible fix: Investigate USB controller power/clock/PHY dependencies on qcs8300-ride platform. Check device tree for missing or incorrect clock references, regulator supplies (vbus, vdda), PHY initialization sequences, or interconnect bandwidth requirements for USB controllers at a400000.usb and a600000.usb. Verify USB controller reset sequencing and PHY calibration timing. This is a known platform-specific issue requiring qcs8300-ride DT/driver fixes, not a PR-introduced regression.
  4. Detail analysis attachment: failed_case_job283049_2_detailed.md
  Case 3: KVM_Driver
  1. Failed case: KVM_Driver
  2. Root cause: /dev/kvm device node not created because the QCS8300 Ride board is running with the Gunyah hypervisor (version gunyah-3fe287d48) at EL2, which means the Linux kernel is running as a guest at EL1 and cannot initialize KVM (KVM requires the kernel to run at EL2 with direct hypervisor access).
  3. Possible fix: This is not a PR-introduced regression. The PR only adds device tree support for Monaco Draco EVK and does not modify QCS8300 Ride configuration or KVM code. The test failure is a pre-existing platform limitation: QCS8300 Ride boots with Gunyah hypervisor by default, preventing nested virtualization. To enable KVM on this platform, either: (1) boot the board with an EL2 device tree overlay (e.g., qcs8300-ride-el2.dtb) that disables the Gunyah hypervisor and boots the kernel directly at EL2, or (2) skip KVM tests on boards configured with Gunyah hypervisor, or (3) configure the LAVA job to use the EL2 variant DTB for KVM testing.
  4. Detail analysis attachment: failed_case_job283049_3_detailed.md
  Case 4: KVM_EL2_DTB
  1. Failed case: KVM_EL2_DTB
  2. Root cause: /dev/kvm device node is not created because KVM ARM driver does not initialize when the Gunyah hypervisor is already running at EL2. The qcs8300-ride platform boots with Gunyah hypervisor (version gunyah-3fe287d48) which occupies EL2, preventing KVM from taking control of the virtualization extensions. CONFIG_KVM is enabled in the kernel config, but the KVM ARM driver silently skips initialization when it detects another hypervisor is present.
  3. Possible fix: This is not a PR-introduced regression. The PR adds device tree support for Monaco Draco EVK board and does not modify KVM, hypervisor, or virtualization configuration. The test failure is a pre-existing platform limitation: qcs8300-ride boots with Gunyah by default, which is incompatible with KVM. To enable KVM on this platform, either: (1) boot the kernel with the EL2 overlay (monaco-draco-evk-el2.dtb) which the PR correctly adds to the Makefile, or (2) disable Gunyah in the boot configuration to allow KVM to claim EL2. The test infrastructure should use the -el2 DTB variant when running KVM tests on this platform.
  4. Detail analysis attachment: failed_case_job283049_4_detailed.md
  Case 5: KVM_Infra — /dev/kvm unavailable (architectural limitation)
  1. Failed case: KVM_Infra — /dev/kvm unavailable (architectural limitation)
  2. Root cause: KVM cannot initialize on qcs8300-ride because the Gunyah hypervisor is already running at EL2. ARM architecture allows only one hypervisor at EL2; when Gunyah boots first (confirmed by "Hypervisor cold boot, version: gunyah-3fe287d48" at boot), KVM's initialization is blocked. CONFIG_KVM is enabled but the KVM driver silently skips initialization when it detects another hypervisor is present, resulting in no /dev/kvm device node.
  3. Possible fix: This is not a PR-introduced regression — it is a platform configuration issue. Either: (1) disable the KVM test suite for qcs8300-ride in the LAVA job definition (recommended — add qcs8300-ride to KVM test skip list), or (2) rebuild the firmware without Gunyah if KVM functionality is required for this platform (not recommended for production configs). The PR changes only add device tree support for Monaco Draco and do not affect KVM or hypervisor initialization.
  4. Detail analysis attachment: failed_case_job283049_5_detailed.md
  Case 6: 0_qcom-next-ci-premerge-tests
  1. Failed case: 0_qcom-next-ci-premerge-tests
  2. Root cause: Test suite marked as failed due to accumulation of 5 individual test failures (Probe_Failure_Check, USBHost, KVM_Driver, KVM_EL2_DTB, KVM_Infra) on qcs8300-ride-sx platform; these are pre-existing platform/infrastructure issues unrelated to the PR changes (which add device tree support for a different board: Monaco Draco EVK).
  3. Possible fix: These failures are not PR-introduced regressions. The PR adds DT bindings and device trees for qcs8300-based Monaco Draco board, which does not affect the qcs8300-ride-sx test platform. Re-run the test or investigate the individual test failures as separate platform issues: (1) xhci-hcd probe timeout (-110) and regulatory.db firmware missing for Probe_Failure_Check, (2) USB host controller not exposing root hubs for USBHost, (3) /dev/kvm device node not present for all KVM tests despite CONFIG_KVM=y.
  4. Detail analysis attachment: failed_case_job283049_6_detailed.md
Job 283050 | SoC hamoa-evk

LAVA job: https://lava-oss.qualcomm.com/scheduler/job/283050

Failed test cases in LAVA job 283050 (SoC: hamoa-evk).

  Case 1: Probe_Failure_Check
  1. Failed case: Probe_Failure_Check
  2. Root cause: Two pre-existing benign probe failures on hamoa-evk platform: (1) qcom_qseecom_uefisecapp driver probe fails with -EBUSY (error -16) due to TrustZone/secure world resource contention during early boot; (2) cfg80211 regulatory.db firmware file missing from rootfs (error -2, ENOENT). Both failures are platform-specific and not introduced by PR arm64: dts: qcom: add Monaco Draco EVK board support #1465, which only adds device tree support for Monaco Draco EVK (a different board). System functionality is unaffected—BT_ON_OFF and WiFi_OnOff tests pass, confirming wireless subsystems work correctly despite the regulatory.db warning.
  3. Possible fix: Suppress these two known benign failures in the Probe_Failure_Check test for hamoa-evk: (1) Add qcom_qseecom_uefisecapp probe failure to the platform-specific benign failure list—this is a known TZ initialization race that does not impact functionality; (2) Add regulatory.db firmware load failure to the benign list when WiFi_OnOff test passes (similar to existing WiFi firmware suppression rules). For proper long-term fix: (a) include regulatory.db in the rootfs image, and (b) investigate qcom_qseecom_uefisecapp probe ordering to eliminate the -EBUSY race.
  4. Detail analysis attachment: failed_case_job283050_1_detailed.md
  Case 2: smmu
  1. Failed case: smmu
  2. Root cause: Test validation logic incorrectly flags the iris video codec parent device (aa00000.video-codec) as missing IOMMU group attachment, when the iris driver architecture intentionally uses child devices (iris_non_pixel.0 and iris_pixel.0) for DMA operations, which are correctly attached to IOMMU groups 16 and 17.
  3. Possible fix: Update the smmu test script to recognize the iris video codec driver architecture where the parent device does not require direct IOMMU attachment because DMA is handled by child devices; add an exception for aa00000.video-codec when iris_non_pixel.0 and iris_pixel.0 are present and properly attached to IOMMU groups.
  4. Detail analysis attachment: failed_case_job283050_2_detailed.md
  Case 3: KVM_Driver
  1. Failed case: KVM_Driver
  2. Root cause: KVM is unavailable because the kernel is running as a guest under the Gunyah hypervisor (EL1) rather than at EL2 (hypervisor mode). The kernel message kvm [1]: HYP mode not available confirms that KVM cannot initialize because it requires EL2 privileges, which are not available when running under a hypervisor without nested virtualization support.
  3. Possible fix: This is not a kernel bug or PR-introduced regression. The Hamoa EVK board is configured to boot Linux as a guest under the Gunyah hypervisor, which prevents KVM from running. To enable KVM on this platform: (1) boot the kernel at EL2 using the -el2 device tree overlay variant (e.g., hamoa-evk-el2.dtb if available), or (2) reconfigure the boot flow to run Linux directly at EL2 without the Gunyah hypervisor, or (3) suppress this test case for boards that boot under a hypervisor by default.
  4. Detail analysis attachment: failed_case_job283050_3_detailed.md
  Case 4: KVM_EL2_DTB
  1. Failed case: KVM_EL2_DTB
  2. Root cause: KVM initialization failed because Hamoa EVK kernel is running as a guest (PVM) under Gunyah hypervisor at EL1, and Gunyah does not expose EL2/HYP mode to the guest; KVM requires EL2 to function and cannot run nested without hypervisor support for nested virtualization.
  3. Possible fix: This is a test environment configuration issue, not a kernel regression. Either: (1) Boot Hamoa EVK kernel at EL2 (bare-metal or with EL2 overlay) to enable KVM, or (2) Mark KVM tests as expected-to-skip on Hamoa EVK when running under Gunyah hypervisor, or (3) Configure Gunyah to expose nested virtualization support if available.
  4. Detail analysis attachment: failed_case_job283050_4_detailed.md
  Case 5: KVM_Infra — KVM/HYP Mode Not Available
  1. Failed case: KVM_Infra — KVM/HYP Mode Not Available
  2. Root cause: The kernel was booted at EL1 (not EL2), preventing KVM initialization. The KVM driver detected "HYP mode not available" at boot (line 4131: kvm [1]: HYP mode not available), which means the kernel is not running in hypervisor mode. CONFIG_KVM is enabled in the kernel config, but /dev/kvm cannot be created because the ARM KVM subsystem requires the kernel to boot at EL2 to access hypervisor features. The hamoa-iot-evk board was flashed with the standard DTB (hamoa-iot-evk.dtb) instead of the EL2 variant DTB (hamoa-iot-evk-el2.dtb) that configures the bootloader to enter the kernel at EL2.
  3. Possible fix: Flash the board with the EL2-enabled DTB variant (hamoa-iot-evk-el2.dtb or equivalent EL2 overlay) to boot the kernel at EL2, enabling KVM/hypervisor mode. Update the LAVA job definition to use the -el2.dtb artifact for KVM test cases on hamoa-evk. Verify that the bootloader (ABL/UEFI) on hamoa-evk supports EL2 entry and that the EL2 DTB overlay is correctly applied during boot.
  4. Detail analysis attachment: failed_case_job283050_5_detailed.md
  Case 6: KVM_Infra
  1. Failed case: KVM_Infra
  2. Root cause: KVM test failure on hamoa-evk platform due to missing hypervisor (EL2) support — kernel reports "HYP mode not available" at boot, preventing /dev/kvm device creation despite CONFIG_KVM being enabled.
  3. Possible fix: This is a platform hardware/firmware limitation, not a kernel regression. The hamoa-evk board does not support EL2 hypervisor mode required for KVM. Skip KVM tests on hamoa-evk in the CI test plan, or enable EL2 support in the board's firmware/bootloader if the hardware supports it.
  4. Detail analysis attachment: failed_case_job283050_6_detailed.md

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants