arm64: dts: qcom: hamoa, purwa: Describe the PCIe M.2 Key E connector - #1629
arm64: dts: qcom: hamoa, purwa: Describe the PCIe M.2 Key E connector#1629weiden (WeiDeng-weiden) wants to merge 4 commits into
Conversation
🔨 Build Failure Analysis — PR #1629PR: #1629
VerdictThis is not a compilation error. The build failed during the merge phase when attempting to integrate PR #1629 with the baseline integration branch that already includes 📎 Detailed analysis: Full report |
🔨 Build Failure Analysis — PR #1629PR: #1629
VerdictThis is not a compilation error. The build failed due to a merge conflict between PR #1629 and the pre-existing topic branch 📎 Detailed analysis: Full report |
PR #1629 — validate-patchPR: #1629
Final Summary
|
PR #1629 — checker-log-analyzerPR: #1629
Detailed report: Full report
|
16367bb to
b0a710a
Compare
🔨 Build Failure Analysis — PR #1629PR: #1629
VerdictThis is not a compilation failure. The build failed during the merge phase due to a merge conflict between PR #1629 and the existing topic branch 📎 Detailed analysis: Full report |
🔨 Build Failure Analysis — PR #1629PR: #1629
VerdictThis is not a compilation error. The build failed during the merge phase before compilation could begin. The conflict is caused by overlapping changes between the PR and the pre-existing 📎 Detailed analysis: Full report |
PR #1629 — validate-patchPR: #1629
Final Summary
|
PR #1629 — checker-log-analyzerPR: #1629
Detailed report: Full report
|
64a8ab1 to
b52387e
Compare
🔨 Build Failure Analysis — PR #1629PR: #1629
VerdictThis is not a compilation error. The build failed during the merge phase because PR #1629 conflicts with changes already present in the integration branch from 📎 Detailed analysis: Full report |
🔨 Build Failure Analysis — PR #1629PR: #1629
VerdictThis is not a compilation error. The build failed during the merge phase due to a git merge conflict between PR #1629 and the integration branch. The conflict must be resolved before the build can proceed. 📎 Detailed analysis: Full report |
PR #1629 — validate-patchPR: #1629
Final Summary
|
PR #1629 — checker-log-analyzerPR: #1629
Detailed report: Full report
|
… pcie4_port0 and uart14 Add empty graph port/endpoint nodes to pcie4_port0 and uart14 in hamoa.dtsi so that board files can reference the endpoint labels (pcie4_port0_ep, uart14_ep) to describe connections to M.2 Key E connectors via remote-endpoint overrides. Suggested-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com> Signed-off-by: Wei Deng <wei.deng@oss.qualcomm.com> Link: https://lore.kernel.org/all/20260804-hamoa-m2-dts-v2-v4-1-1b5ceac74538@oss.qualcomm.com/
Add 'compatible = "pciclass,0604"' to the pcie4_port0 node in hamoa.dtsi to allow the PCI subsystem to associate the DT node with the PCI-to-PCI bridge device, which is required for M.2 connector graph endpoint association. Reviewed-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com> Signed-off-by: Wei Deng <wei.deng@oss.qualcomm.com> Link: https://lore.kernel.org/all/20260804-hamoa-m2-dts-v2-v4-2-1b5ceac74538@oss.qualcomm.com/
…E connector The Hamoa IoT EVK has a PCIe M.2 Mechanical Key E connector for wireless connectivity cards exposing Wi-Fi over PCIe and Bluetooth over UART. Describe the connector node with: - port@0: PCIe for Wi-Fi, linked to pcie4_port0 - port@3: UART for Bluetooth, linked to uart14 This allows the pwrseq-pcie-m2 driver to manage card power and dynamically create the UART serdev for UART BT variants of the M.2 card. Remove the chip-specific wcn7850-pmu node, the static bluetooth serdev under uart14, and the wifi@0 PCI child node, as the M.2 connector approach replaces WCN7850-specific power sequencing with a chip-agnostic model. Also remove the now-unused vreg_wcn_0p95 and vreg_wcn_1p9 dummy fixed regulators whose only consumers were the wcn7850-pmu node. Reviewed-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com> Reviewed-by: Manivannan Sadhasivam <mani@kernel.org> Signed-off-by: Wei Deng <wei.deng@oss.qualcomm.com> Link: https://lore.kernel.org/all/20260804-hamoa-m2-dts-v2-v4-3-1b5ceac74538@oss.qualcomm.com/
…E connector The Purwa IoT EVK has a PCIe M.2 Mechanical Key E connector for wireless connectivity cards exposing Wi-Fi over PCIe and Bluetooth over UART. Purwa inherits hamoa.dtsi via purwa.dtsi and therefore reuses the PCIe root port compatible and the uart14_ep / pcie4_port0_ep endpoint stub labels added there. Describe the connector node with: - port@0: PCIe for Wi-Fi, linked to pcie4_port0 - port@3: UART for Bluetooth, linked to uart14 This allows the pwrseq-pcie-m2 driver to manage card power and dynamically create the UART serdev for UART BT variants of the M.2 card. Remove the chip-specific wcn7850-pmu node, the static bluetooth serdev under uart14, and the wifi@0 PCI child node, as the M.2 connector approach replaces WCN7850-specific power sequencing with a chip-agnostic model. Also remove the now-unused vreg_wcn_0p95 and vreg_wcn_1p9 dummy fixed regulators whose only consumers were the wcn7850-pmu node. Signed-off-by: Wei Deng <wei.deng@oss.qualcomm.com> Link: https://lore.kernel.org/all/20260804-hamoa-m2-dts-v2-v4-4-1b5ceac74538@oss.qualcomm.com/
b52387e to
e6274b8
Compare
weiden (WeiDeng-weiden)
changed the title
🔨 Build Failure Analysis — PR #1629PR: #1629
VerdictThis is not a compilation failure. The build failed during the merge phase when attempting to integrate PR #1629 with the baseline integration branch. Both conflicts are PR-introduced and occur because the PR modifies the same device tree sections that have been changed in the integration branch (topic/tech/all/dt/hamoa). 📎 Detailed analysis: Full report |
🔨 Build Failure Analysis — PR #1629PR: #1629
VerdictThis is NOT a compilation failure. Both errors are git merge conflicts caused by the integration branch already containing changes to the same device tree sections that the PR modifies. The build never reached the compilation stage. 📎 Detailed analysis: Full report |
PR #1629 — validate-patchPR: #1629
Final Summary
|
PR #1629 — checker-log-analyzerPR: #1629
Detailed report: Full report
|
|
The merge conflict in hamoa-iot-evk.dts and purwa-iot-evk.dts is caused by existing workaround commits on tech/all/workaround:
These WA commits modify wcn7850-pmu and add vreg_wcn_bt_en, which conflicts with this PR's removal of the same nodes during the CI The corresponding WA revert (PR #1627) will follow up once this PR is merged. |
|
Hi Salendarsingh Gaud (@sgaud-quic) |
2 participants
Describe the PCIe M.2 Key E connector on the Hamoa and Purwa IoT EVKs
4 commits:
hamoa: Add graph port/endpoint anchors to pcie4_port0 and uart14— endpoint stubs in hamoa.dtsi (Suggested-by: Konrad)hamoa: Add compatible to the PCIe Root Port—pciclass,0604on pcie4_port0 (Reviewed-by: Konrad)hamoa-iot-evk: Describe the PCIe M.2 Key E connector— port@0 PCIe + port@3 UART; remove wcn7850-pmu/static BT(Reviewed-by: Konrad, Mani)purwa-iot-evk: Describe the PCIe M.2 Key E connector— same connector layout; Purwa inherits hamoa.dtsiUpstream V4: https://lore.kernel.org/all/20260804-hamoa-m2-dts-v2-v4-0-1b5ceac74538@oss.qualcomm.com/
CRs-Fixed: 4630764