Skip to content

FROMLIST: arm64: dts: qcom: sa8775p: Add qref and refgen supply for P… - #1733

Open
qianyu-qcom wants to merge 27 commits into
qualcomm-linux:tech/all/dt/qcs9100from
qianyu-qcom:tech/all/dt/qcs9100
Open

FROMLIST: arm64: dts: qcom: sa8775p: Add qref and refgen supply for P…#1733
qianyu-qcom wants to merge 27 commits into
qualcomm-linux:tech/all/dt/qcs9100from
qianyu-qcom:tech/all/dt/qcs9100

Conversation

@qianyu-qcom

Copy link
Copy Markdown

…CIe PHYs

The QMP PCIe PHYs on SA8775p require dedicated qref and refgen voltage supplies for stable operation. Without these supplies, the system may occasionally crash.

Add vdda-qref-supply and vdda-refgen-supply in the board files (Lemans-EVK, Lemans-RIDE, QCS9100-RIDE and QCS9100-RIDE-R3).

Link: https://lore.kernel.org/all/20260810112735.1326807-5-ziyue.zhang@oss.qualcomm.com/
Fixes: 94d7d37 ("arm64: dts: qcom: lemans-evk: Enable PCIe support")
Fixes: 76326da ("arm64: dts: qcom: lemans: Refactor ride/ride-r3 boards based on daughter cards")

Shivendra Pratap and others added 27 commits August 18, 2026 23:36
Add support for SYSTEM_RESET2 vendor-specific resets
as reboot-modes in the psci node.  Describe the resets:
"bootloader" will cause device to reboot and stop in the
bootloader's fastboot mode.  "edl" will cause device to reboot
into "emergency download mode", which permits loading images via
the Firehose protocol.

Link: https://lore.kernel.org/r/20251109-arm-psci-system_reset2-vendor-reboots-v17-10-46e085bca4cc@oss.qualcomm.com
Signed-off-by: Elliot Berman <elliot.berman@oss.qualcomm.com>
Signed-off-by: Shivendra Pratap <shivendra.pratap@oss.qualcomm.com>
There's a WCN6855 WiFi/Bluetooth module on an M.2 card. To make
Bluetooth work, we need to define the necessary device tree nodes,
including UART configuration and power supplies.

Since there is no standard M.2 binding in the device tree at present,
the PMU is described using dedicated PMU nodes to represent the
internal regulators required by the module.

The module provides a 3.3V supply, which originates from the
main board’s 12V rail. To represent this power hierarchy in the device
tree, add a fixed 12V regulator node as the DC-IN source and link it
to the 3.3V regulator node.

Link: https://lore.kernel.org/all/20251112071147.1450258-2-wei.deng@oss.qualcomm.com/
Signed-off-by: Wei Deng <wei.deng@oss.qualcomm.com>
Unlike the CPU, the CDSP does not throttle its speed automatically
when it reaches high temperatures in lemans.

Set up CDSP cooling for both instances by throttling the cdsp, when
it reaches 105°C.

Signed-off-by: Gaurav Kohli <gaurav.kohli@oss.qualcomm.com>
Link: https://lore.kernel.org/r/20260609-qmi-tmd-v3-5-291a2ff4c634@oss.qualcomm.com
…bypass pwrseq flow

There is a conflict between the current DTS configuration and the
driver behavior for the WCN6855 Bluetooth path. With the PMU node in
place, the driver takes the pwrseq code path unintentionally, which
leads to Bluetooth failing to power up during an on -> off -> on
transition.

To unblock function, temporarily remove the WCN6855 PMU node so that
the driver follows the non-pwrseq path and avoids the unexpected sequence.

This is a TEMPORARY WORKAROUND. Once a proper M.2 binding/solution is
upstreamed, will re-submit both DTS and driver changes aligned with
the M.2 model.

Signed-off-by: Wei Deng <wei.deng@oss.qualcomm.com>
Add support for IRIS on lemans when Linux host running at EL2.

Signed-off-by: Vikash Garodia <vikash.garodia@oss.qualcomm.com>
… controller

Add the "wakeup-source" property to the primary port controller node so its
interrupt can wake the system from low‑power states on lemans EVK
platform.

Link: https://lore.kernel.org/all/20260215183325.3836178-3-swati.agarwal@oss.qualcomm.com/
Signed-off-by: Swati Agarwal <swati.agarwal@oss.qualcomm.com>
Switch the iris video codec node in sa8775p (lemans) from the legacy
'iommus' property to 'iommu-map', using IRIS_NON_PIXEL_VCODEC and
IRIS_PIXEL function IDs to identify the non-pixel and pixel context
bank SMMU stream mappings respectively.

Signed-off-by: Vishnu Reddy <busanna.reddy@oss.qualcomm.com>
Signed-off-by: Vikash Garodia <vikash.garodia@oss.qualcomm.com>
Signed-off-by: Gourav Kumar <gouravk@qti.qualcomm.com>
As per memory map, video firmware memory region is 7MB for sa8775*
variants while it is 16MB for qcs9100* variants. Keeping the 7MB variant
of video firmware in ride common DTS does not allow qcs9100* to pick the
16MB variant. Drop it from common and define in respective variant DTS.

Signed-off-by: Gourav Kumar <gouravk@qti.qualcomm.com>
Signed-off-by: Vikash Garodia <vikash.garodia@oss.qualcomm.com>
Signed-off-by: Venkata Siva Pavan KumarVenkatapatigari <venvenk@qti.qualcomm.com>
…r primary port controller

Rename the hd3ss3220_ instance to improve clarity and simplify usage when
adding a secondary port controller.

Reviewed-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Signed-off-by: Swati Agarwal <swati.agarwal@oss.qualcomm.com>
Link: https://lore.kernel.org/r/20260406110113.1709886-2-swati.agarwal@oss.qualcomm.com
…er in host mode

Enable secondary USB controller in host mode on lemans EVK Platform.

Secondary USB controller is connected to a Genesys Logic USB HUB GL3590
having 4 ports. The ports of hub that are present on lemans EVK standalone
board are used as follows:-
1) port-1 is connected to HD3SS3220 Type-C port controller.
2) port-4 is used for the M.2 E key on corekit. Standard core kit uses UART
for Bluetooth. This port is to be used only if user optionally replaces the
WiFi card with the NFA765 chip which uses USB for Bluetooth.

Remaining 2 ports will become functional when the interface plus mezzanine
board is stacked on top of corekit:

3) port-2 is connected to another hub which is present on the mezz through
which 4 type-A ports are connected.
4) port-3 is used for the M.2 B key for a 5G card when the mezz is
connected.

Secondary USB Controller
          ↓
GL3590 USB Hub (4 ports)
    |
    |-- Port 1 → HD3SS3220 Type‑C Port Controller → USB‑C Connector
    |
    |-- Port 2 → Mezzanine USB Hub (when mezz attached)
    |
    |-- Port 3 → M.2 B‑Key Slot (when mezz attached)
    |
    |-- Port 4 → M.2 E‑Key Slot
                         (Default: BT via UART;
                          USB only if NFA765 module is installed)

Mark the second USB controller as host only capable and add the HD3SS3220
Type-C port controller along with Type-C connector for controlling vbus
supply.

Signed-off-by: Swati Agarwal <swati.agarwal@oss.qualcomm.com>
Link: https://lore.kernel.org/r/20260406110113.1709886-3-swati.agarwal@oss.qualcomm.com
…oller

Enable the tertiary usb controller connected to micro usb port in OTG mode
on Lemans EVK platform.

Reviewed-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Signed-off-by: Swati Agarwal <swati.agarwal@oss.qualcomm.com>
Link: https://lore.kernel.org/r/20260306091355.1178333-5-swati.agarwal@oss.qualcomm.com
Add dailinks for DISPLAY-PORT to enable audio functionality
on edp0.

Link: https://lore.kernel.org/all/20260413043713.1659-1-kumar.singh@oss.qualcomm.com/

Signed-off-by: Karthik S <karthik.s@oss.qualcomm.com>
The lemans EVK board supports either eMMC or SD-card, but only one can
be active at a time.

Move the SDHC node for SD card into a dedicated device tree overlay.
This decoupling allows the storage medium to be selected dynamically by
applying the appropriate overlay for either SD card or eMMC support.

Link: https://lore.kernel.org/all/20260227102405.2339544-2-monish.chunara@oss.qualcomm.com/
Signed-off-by: Monish Chunara <monish.chunara@oss.qualcomm.com>
…a overlay

Enable the SDHCI controller for eMMC functionality on the lemans EVK
using a device tree overlay. Configure the corresponding addresse space
and resources for eMMC.

Link: https://lore.kernel.org/all/20260227102405.2339544-3-monish.chunara@oss.qualcomm.com/
Signed-off-by: Monish Chunara <monish.chunara@oss.qualcomm.com>
Add AEST RAS error source nodes for the Lemans SoC.

The DT describes a processor error source covering all CPU cores and a
shared L3 cache error source for the cluster. These nodes model the
hardware error reporting blocks and associated interrupts as required
by the Arm AEST specification.

Link: https://lore.kernel.org/lkml/20260505-aest-devicetree-support-v1-7-d5d6ffacf0a5@oss.qualcomm.com/
Co-developed-by: Faruque Ansari <faruque.ansari@oss.qualcomm.com>
Signed-off-by: Faruque Ansari <faruque.ansari@oss.qualcomm.com>
Signed-off-by: Umang Chheda <umang.chheda@oss.qualcomm.com>
…no SMMU

On Lemans platforms, the Adreno SMMU requires a bandwidth vote on
the GEM_NOC path (MASTER_GPU_TCU -> SLAVE_EBI1) before its registers
are accessible. Without this vote, the SMMU may become unreachable,
leading to intermittent probe failures and runtime issues.

Add the required interconnect to ensure reliable register access.

Link: https://lore.kernel.org/all/20260526-smmu_interconnect_addition-v2-4-2a6d8ca30d63@oss.qualcomm.com/
Signed-off-by: Bibek Kumar Patro <bibek.patro@oss.qualcomm.com>
…node

Qualcomm Inline Crypto Engine (ICE) platform driver now supports
an optional OPP-table.

Add OPP-table for ICE UFS device nodes for LeMans platform.

Signed-off-by: Abhinaba Rakshit <abhinaba.rakshit@oss.qualcomm.com>
Link: https://lore.kernel.org/r/20260609-enable-ice-clock-scaling-v11-6-1cebc8b3275b@oss.qualcomm.com
… devices

Add label properties to TPDM and CTI nodes in the lemans device tree to
provide human-readable identifiers for each CoreSight device. These
labels allow userspace tools and the CoreSight framework to identify
devices by name rather than by base address.

Link: https://lore.kernel.org/linux-arm-msm/20260414-add-label-to-coresight-device-v2-1-5017d07358f2@oss.qualcomm.com/
Reviewed-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Signed-off-by: Jie Gan <jie.gan@oss.qualcomm.com>
Add 'compatible = "pciclass,0604"' to the pcieport0 node in lemans.dtsi
to allow the PCI subsystem to associate the DT node with the PCI-to-PCI
bridge device. This is required for downstream DT nodes (such as M.2
connectors described as graph endpoints of the Root Port) to be matched
to PCI devices.

Link: https://lore.kernel.org/r/20260622-v3-lemans-split-v3-1-d26bb22594e3@oss.qualcomm.com
Reviewed-by: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Reviewed-by: Manivannan Sadhasivam <mani@kernel.org>
Signed-off-by: Wei Deng <wei.deng@oss.qualcomm.com>
…onnector

The lemans EVK has the PCIe M.2 Mechanical Key E connector to connect
wireless connectivity cards over PCIe and UART interfaces. Hence,
describe the connector node and link it with the PCIe 0 Root Port and
UART17 nodes through graph port/endpoint.

The M.2 Key E connector is powered by a 3.3V fixed regulator
(vreg_wcn_3p3) which is sourced from the board's 12V DC input rail
(vreg_dcin_12v). Both regulators are always-on and are required by the
pcie-m2-e-connector binding.

Also add the serial1 = &uart17 alias, which is required for the
Bluetooth serdev device to be enumerated on the UART17 interface.

Link: https://lore.kernel.org/r/20260622-v3-lemans-split-v3-2-d26bb22594e3@oss.qualcomm.com
Reviewed-by: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Reviewed-by: Manivannan Sadhasivam <mani@kernel.org>
Reviewed-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Signed-off-by: Wei Deng <wei.deng@oss.qualcomm.com>
The ADSP PAS on several Qualcomm SoCs (e.g. SA8775P/lemans, QCS8300,
Monaco) needs more than a single SMMU stream ID for the audio ML
(machine-learning) offload use case. In addition to the primary
ADSP stream ID, the DSP/SPF issues DMA transactions through extra
stream IDs that are not covered by the existing single-entry mapping.

Relax the iommus constraint to allow between 1 and 3 entries so the
additional ML offload stream IDs can be described, fixing dtb_check
schema violations on device trees that add them.

Link: https://lore.kernel.org/all/20260717095825.3962666-2-pratyush.meduri@oss.qualcomm.com/
Signed-off-by: Pratyush Meduri <pratyush.meduri@oss.qualcomm.com>
…d SMMU mappings

The audio ML (machine-learning) offload use case requires a contiguous,
physically addressable buffer shared with the audio DSP/SPF, and issues
DMA transactions through additional SMMU stream IDs that are not
covered by the existing ADSP mapping.

Add a dedicated reusable shared-dma-pool CMA region (16 MiB, 4 MiB
aligned) and wire it to the q6apm DAIs node via memory-region. A
dedicated pool guarantees the alignment and contiguity the DSP expects
and isolates these allocations from the default CMA region.

Under the EL2 (Gunyah/hypervisor) configuration the SMMU is fully
enforcing, so the ML transactions are otherwise blocked and faulted:

 arm-smmu 15000000.iommu: Blocked unknown Stream ID 0x3060
 arm-smmu 15000000.iommu: Blocked unknown Stream ID 0x3062

Add the ML-related stream IDs (0x3060 mask 0x9, 0x3062 mask 0x1) to the
remoteproc_adsp iommus property in the EL2 overlay so these buffers are
translated by the SMMU instead of being rejected.

Link: https://lore.kernel.org/all/20260717095825.3962666-3-pratyush.meduri@oss.qualcomm.com/
Signed-off-by: Pratyush Meduri <pratyush.meduri@oss.qualcomm.com>
…u-map"

This reverts commit e1af6fe.

Signed-off-by: Vishnu Reddy <busanna.reddy@oss.qualcomm.com>
The Iris VPU has separate streams with different IOVA constraints. The
non-pixel stream must be limited to the 0-600 MB IOVA range, while the
pixel stream can use the full IOVA space.
Using a single set of IOMMU entries for the Iris node does not describe
these per-stream limits and can allow accesses outside the supported
range, which may lead to device crashes. One such issue was reported at:
https://gitlab.freedesktop.org/drm/msm/-/work_items/100

Add non-pixel and pixel child nodes, move each stream ID to its
corresponding child node, and add a reserved IOVA range for the
non-pixel stream.

Link: https://lore.kernel.org/all/20260709-vpu_iommu_iova_handling-v1-9-72bb62cb2dfd@oss.qualcomm.com
Co-developed-by: Vishnu Reddy <busanna.reddy@oss.qualcomm.com>
Signed-off-by: Vishnu Reddy <busanna.reddy@oss.qualcomm.com>
Signed-off-by: Vikash Garodia <vikash.garodia@oss.qualcomm.com>
Tested-by: Daniel J Blueman <daniel@quora.org>
…emory and SMMU mappings"

This reverts commit 4009109.

Signed-off-by: Sairamreddy Bojja <sbojja@qti.qualcomm.com>
…to 3 iommus"

This reverts commit cd76d7f.

Signed-off-by: Sairamreddy Bojja <sbojja@qti.qualcomm.com>
…CIe PHYs

The QMP PCIe PHYs on SA8775p require dedicated qref and refgen voltage
supplies for stable operation. Without these supplies, the system may
occasionally crash.

Add vdda-qref-supply and vdda-refgen-supply in the board files
(Lemans-EVK, Lemans-RIDE, QCS9100-RIDE and QCS9100-RIDE-R3).

Link: https://lore.kernel.org/all/20260810112735.1326807-5-ziyue.zhang@oss.qualcomm.com/
Fixes: 94d7d37 ("arm64: dts: qcom: lemans-evk: Enable PCIe support")
Fixes: 76326da ("arm64: dts: qcom: lemans: Refactor ride/ride-r3 boards based on daughter cards")
Signed-off-by: Ziyue Zhang <ziyue.zhang@oss.qualcomm.com>
Signed-off-by: Qiang Yu <qiang.yu@oss.qualcomm.com>
@qcomlnxci
qcomlnxci requested review from a team and Nicolas Dechesne (ndechesne) and removed request for a team August 24, 2026 02:58
@qlijarvis

Copy link
Copy Markdown

PR #1733 — validate-patch

PR: #1733

Verdict Issues Detailed Report
0 Full report

Final Summary

  1. Lore link present: Yes — https://lore.kernel.org/all/20260810112735.1326807-5-ziyue.zhang@oss.qualcomm.com/
  2. Lore link matches PR commits: Yes — diff content faithful to lore; context line numbers differ due to different baseline (expected for FROMLIST:)
  3. Upstream patch status: ⏳ In review — Reviewed-by from Krzysztof Kozlowski (2026-08-14); Manivannan Sadhasivam requested commit message clarification (2026-08-20); no merge or NAK decision yet
  4. PR present in qcom-next/topics: Partial - 1/1 commit(s) only have partial integration evidence
Verdict: ✅ — click to expand

🔍 Patch Validation

PR: #1733 — FROMLIST: arm64: dts: qcom: sa8775p: Add qref and refgen supply for PCIe PHYs
Upstream commit: https://lore.kernel.org/all/20260810112735.1326807-5-ziyue.zhang@oss.qualcomm.com/
Verdict: ✅ PASS

Commit Message

Check Status Note
Subject matches upstream Identical except for FROMLIST: prefix (expected)
Body preserves rationale Key rationale preserved: "require dedicated qref and refgen voltage supplies for stable operation. Without these supplies, the system may occasionally crash."
Fixes tag present/correct Both Fixes tags present and match lore exactly
Authorship preserved From: matches lore author (Ziyue Zhang); both Signed-off-by: lines present
Backport note (if applicable) N/A Not a backport — FROMLIST: prefix indicates patch posted to mailing list but not yet merged

Diff

File Status Notes
arch/arm64/boot/dts/qcom/lemans-evk.dts:897 Identical code change; context line numbers differ (lore: 851, PR: 897) — expected for different baseline
arch/arm64/boot/dts/qcom/lemans-ride-common.dtsi:981 Identical code change; context line numbers differ (lore: 983, PR: 981) — expected for different baseline
arch/arm64/boot/dts/qcom/qcs9100-ride-r3.dts:14 Identical — adds vdda-refgen-supply for both PHYs
arch/arm64/boot/dts/qcom/qcs9100-ride.dts:14 Identical — adds vdda-refgen-supply for both PHYs

Upstream Patch Status

Commit Community Verdict
arm64: dts: qcom: sa8775p: Add qref and refgen supply for PCIe PHYs Decision Pending — Reviewed-by: Krzysztof Kozlowski (dt-bindings maintainer) on 2026-08-14; Manivannan Sadhasivam (PHY maintainer) requested additional commit message context on 2026-08-20; no merge/NAK decision yet

qcom-next/topics Presence

Commit Status
FROMLIST: arm64: dts: qcom: sa8775p: Add qref and refgen supply for PCIe PHYs ⚠️ Partial — integration_presence_report.md shows "partial - subject or partial tree evidence found, but full change was not verified"

Verdict

Merge as-is. The PR faithfully represents the lore patch (patch 4/4 of series v1). Diff content is identical; context line number differences are expected and acceptable for a FROMLIST: patch applied to a different baseline. Commit message preserves all key information including rationale, Fixes tags, and authorship. The patch has received Reviewed-by: from the dt-bindings maintainer and is under active review by the PHY maintainer.

Final Summary

  1. Lore link present: Yes — https://lore.kernel.org/all/20260810112735.1326807-5-ziyue.zhang@oss.qualcomm.com/
  2. Lore link matches PR commits: Yes — diff content faithful to lore; context line numbers differ due to different baseline (expected for FROMLIST:)
  3. Upstream patch status: ⏳ In review — Reviewed-by from Krzysztof Kozlowski (2026-08-14); Manivannan Sadhasivam requested commit message clarification (2026-08-20); no merge or NAK decision yet
  4. PR present in qcom-next/topics: Partial — per integration_presence_report.md: "partial - subject or partial tree evidence found, but full change was not verified"

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

Commit Subject qcom-next topics Final
1/1 [PATCH] FROMLIST: arm64: dts: qcom: sa8775p: Add qref and refgen missing - no subject, patch-id, or full tree-content match found partial - subject or partial tree evidence found, but full change was not verified partial

Final Status

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

@qlijarvis

Copy link
Copy Markdown

PR #1733 — checker-log-analyzer

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

Checker Result Summary
Checker Result Summary
checkpatch ⚠️ CI merge failure - no checker execution
dt-binding-check ⚠️ CI merge failure - no checker execution
dtb-check ⚠️ CI merge failure - no checker execution
sparse-check ⚠️ CI merge failure - no checker execution
check-uapi-headers ⚠️ CI merge failure - no checker execution
check-patch-compliance ⚠️ CI merge failure - no checker execution
tag-check PASS - commit has valid FROMLIST: prefix
qcom-next-check N/A Not applicable (target: tech/all/dt/qcs9100)

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #1733 - FROMLIST: arm64: dts: qcom: sa8775p: Add qref and refgen supply for PCIe PHYs
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/32684833900
Target branch: tech/all/dt/qcs9100

Checker Result Summary
checkpatch ⚠️ CI merge failure - no checker execution
dt-binding-check ⚠️ CI merge failure - no checker execution
dtb-check ⚠️ CI merge failure - no checker execution
sparse-check ⚠️ CI merge failure - no checker execution
check-uapi-headers ⚠️ CI merge failure - no checker execution
check-patch-compliance ⚠️ CI merge failure - no checker execution
tag-check PASS - commit has valid FROMLIST: prefix
qcom-next-check N/A Not applicable (target: tech/all/dt/qcs9100)

⚠️ CI Infrastructure Failure

Root cause: All checker jobs failed during the merge phase with "fatal: refusing to merge unrelated histories" before any actual checker validation could run.

Failure details:

2026-08-24T03:16:41.0522528Z fatal: refusing to merge unrelated histories
2026-08-24T03:17:03.1494578Z Merge failed or conflicts detected. Aborting merge.
2026-08-24T03:17:03.1513262Z fatal: There is no merge to abort (MERGE_HEAD missing).
2026-08-24T03:17:03.1533894Z ##[error]Process completed with exit code 3.

This error occurred identically across all six checker jobs (checkpatch, dt-binding-check, dtb-check, sparse-check, check-uapi-headers, check-patch-compliance) during the CI workflow's attempt to merge the PR branch with the integration baseline.

Analysis:

The "refusing to merge unrelated histories" error indicates that the CI infrastructure encountered a Git history incompatibility when attempting to merge:

  1. The baseline integration branch (based on tag 3c1e80ceb9fb6978aa94bc0624e7c0003f3b4f6e)
  2. The topic branch topic/tech/all/dt/qcs9100
  3. The PR branch pr-1733

This is a CI infrastructure/configuration issue, not a patch quality defect. The patch itself could not be validated because the checkers never executed.

Fix: Re-trigger the CI workflow. If the issue persists, the repository maintainers may need to:

  • Verify the base branch tech/all/dt/qcs9100 has a common ancestor with the integration baseline
  • Check if the topic branch configuration in the CI workflow is correct
  • Consider using git merge --allow-unrelated-histories in the CI merge script (if appropriate for this workflow)

Reproduce locally:

# This is a CI infrastructure issue and cannot be reproduced locally
# The patch itself can be validated with:
git fetch https://github.com/qualcomm-linux/kernel-topics.git pull/1733/head:pr-1733
git checkout pr-1733
./scripts/checkpatch.pl --strict --ignore FILE_PATH_CHANGES -g HEAD

✅ tag-check (Manual Verification)

Status: PASS

Analysis:

  • Target branch: tech/all/dt/qcs9100 (NOT qcom-next or qcom-next-staging)
  • Subject-prefix check: MANDATORY for this branch
  • Commit subject: FROMLIST: arm64: dts: qcom: sa8775p: Add qref and refgen supply for PCIe PHYs
  • Prefix: FROMLIST: ✅ (valid - indicates patch posted to mailing list)

The commit correctly uses the FROMLIST: prefix and includes a valid Link: tag pointing to the lore.kernel.org posting:

Link: https://lore.kernel.org/all/20260810112735.1326807-5-ziyue.zhang@oss.qualcomm.com/

📋 Patch Quality Assessment (from pr.patch)

Since the checkers did not execute, I performed a manual review of the patch:

Commit message quality: ✅ PASS

  • Has FROMLIST: prefix
  • Has Link: tag with valid lore URL
  • Has Fixes: tags (2) referencing the commits that introduced the boards
  • Has proper Signed-off-by: tags (2)
  • Commit body is clear and explains the change

Code changes: ✅ PASS

  • DTS-only changes (4 files modified)
  • Adds vdda-qref-supply and vdda-refgen-supply properties to PCIe PHY nodes
  • Changes are consistent across all affected board files
  • No code style issues visible

Expected checker results (prediction):

  • checkpatch: Likely PASS (DTS changes, proper commit format)
  • dt-binding-check: SKIP (no binding changes)
  • dtb-check: Likely PASS (adding supply properties to existing nodes)
  • sparse-check: SKIP (no C/H files changed)
  • check-uapi-headers: SKIP (no UAPI changes)
  • check-patch-compliance: Likely PASS (has FROMLIST prefix and Link tag)

Verdict

CI infrastructure failure prevented checker execution. The patch itself appears well-formed and ready for merge once CI is fixed.

Action required:

  1. Re-trigger the CI workflow to get actual checker results
  2. If the merge failure persists, escalate to repository maintainers to fix the CI configuration for the tech/all/dt/qcs9100 branch

Patch quality: Based on manual review, the patch follows all kernel coding standards and commit message requirements. No patch changes are needed.

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.