Skip to content

Qcom 6.18.30 GA blockers for KLMT#755

Open
sgaud-quic wants to merge 9 commits into
qualcomm-linux:qcom-6.18.30from
sgaud-quic:qcom-6.18.30-GA-Blockers
Open

Qcom 6.18.30 GA blockers for KLMT#755
sgaud-quic wants to merge 9 commits into
qualcomm-linux:qcom-6.18.30from
sgaud-quic:qcom-6.18.30-GA-Blockers

Conversation

@sgaud-quic

Copy link
Copy Markdown
Contributor

Handpicked commits from below PR's :

arm64: dts: qcom: talos: Add GMSL deserializer and sensor (#643)
misc: fastrpc: map ADSP remote heap into remoteproc IOMMU domain (#732)
qcom.config: Enable Intel IXGBE driver (#730)
net: stmmac: dwmac-qcom-ethqos: Restore nominal clk_ptp_ref frequency (#619)
Revert "FROMLIST: arm64: dts: qcom: monaco: fix wrong connection for the replicator" (#716)
Add pcie qref regulator for Hamoa IOT EVK platform (#648)
PCI: qcom: Set max OPP before DBI access during resume (#647)
arm64: dts: qcom: monaco-evk-emmc: Remove explicit UFS disablement (#704)

mchunara007 and others added 9 commits June 22, 2026 19:47
…blement

The eMMC overlay currently explicitly disables the UFS host controller
and overrides the vreg_l8a voltage. This causes unnecessary UFS
disablement in scenarios where UFS is the boot medium and eMMC is used
as secondary storage.

Since UFS and eMMC share a common VDD rail, their mutual exclusivity is
now managed dynamically via DT-fixup logic. Remove these static entries
from the overlay to allow flexible storage configurations.

Link: https://lore.kernel.org/all/20260616130347.3096034-1-monish.chunara@oss.qualcomm.com/

Signed-off-by: Monish Chunara <monish.chunara@oss.qualcomm.com>
During resume, qcom_pcie_icc_opp_update() may access DBI registers before
the OPP votes are restored, which can trigger NoC errors.

Set the PCIe controller to the maximum OPP first in resume_noirq(), then
proceed with link/DBI accesses. The OPP is later updated again based on
the actual link bandwidth requirements.

Also introduce a small helper to reuse the max-OPP setup path shared with
probe.

Fixes: 5b6272e ("PCI: qcom: Add OPP support to scale performance")
Link: https://lore.kernel.org/all/20260416-setmaxopp-v1-1-6a74e2d945a0@oss.qualcomm.com/
Signed-off-by: Qiang Yu <qiang.yu@oss.qualcomm.com>
Signed-off-by: Ziyue Zhang <ziyue.zhang@oss.qualcomm.com>
All PCIe PHYs on the X1E80100 SOC require the vdda-qref, which feeds QREF
clocks provided by the TCSR device.

Hence, restore the vdda-qref request for the 6th and the 3th PCIe instance
by reverting commit 031b46b ("phy: qcom: qmp-pcie: drop bogus x1e80100
qref supplies") and commit eb7a22f("phy: qcom: qmp-pcie: drop bogus
x1e80100 qref supply"). For the 4th PCIe instance (Gen3 x2), add a new
driver data entry, namely x1e80100_qmp_gen3x2_pciephy_cfg, which is a copy
of sm8550_qmp_gen3x2_pciephy_cfg but uses sm8550_qmp_phy_vreg_l instead.

Workaround will be reverted once the vote qref regulator for PCIe available in upstream.

Fixes: eb7a22f ("phy: qcom: qmp-pcie: drop bogus x1e80100 qref supplies")
Fixes: 031b46b ("phy: qcom: qmp-pcie: drop bogus x1e80100 qref supplies")
Fixes: 606060c ("phy: qcom-qmp-pcie: Add support for X1E80100 g3x2 and g4x2 PCIE")
Cc: Johan Hovold <johan+linaro@kernel.org>
Cc: Abel Vesa <abel.vesa@linaro.org>
Signed-off-by: Wenbin Yao <quic_wenbyao@quicinc.com>
Signed-off-by: Qiang Yu <qiang.yu@oss.qualcomm.com>
Signed-off-by: Ziyue Zhang <ziyue.zhang@oss.qualcomm.com>
All PCIe PHYs on X1E80100 require vdda-qref power supplies, but this is
missing in the current PHY device tree node. The PCIe port can still
function because the regulator L3J, which vdda-qref consumes, is voted by
other components.

Since the device tree should accurately describe the hardware, add the
vdda-qref power supply explicitly in all PCIe PHY device nodes.

Workaround will be reverted once the vote qref regulator for PCIe available in upstream.

Signed-off-by: Qiang Yu <qiang.yu@oss.qualcomm.com>
Signed-off-by: Ziyue Zhang <ziyue.zhang@oss.qualcomm.com>
…the replicator"

This reverts commit 99beb1d. This is a corrective
patch for a mistake that causes an ETR connection issue; it needs to be reverted.
This patch aims to fix a mistake issue made by maintainer on upstream, but the
issue does not exist on qli2.0.

Signed-off-by: Jie Gan <jie.gan@oss.qualcomm.com>
…_ref"

This reverts commit db845b9.

Reason: this change causes the PTP clock to always be in Turbo mode
which can cause power KPI regression.

Signed-off-by: Kiran Patchala <pkiran@qti.qualcomm.com>
Enable the IXGBE and IXGBEVF drivers to support the Intel X550 T2 NIC on
QLI boards with SR-IOV support.

Signed-off-by: Hariprasad kelam <kelam@qti.qualcomm.com>
…omain

When the remoteproc has an IOMMU (kernel running at EL2 without a
separate hypervisor), memory carveouts must be explicitly mapped into
the remoteproc's IOMMU domain so the DSP can access them.  Without
this mapping the DSP triggers an SMMU translation fault when accessing
the remote heap carveout used for audio PD static process creation.

Add has_iommu to fastrpc_channel_ctx, set from the "iommus" property
of the remoteproc DT node.  When set, map the ADSP remote heap
carveout into the remoteproc's IOMMU domain using an identity mapping
(IOVA == PA) via iommu_map(), and skip qcom_scm_assign_mem() which is
only needed when a separate hypervisor manages inter-VM memory access
control.

Introduce fastrpc_remote_heap_map() and fastrpc_remote_heap_unmap()
helpers to encapsulate the IOMMU domain lookup and map/unmap.

Link: https://lore.kernel.org/all/20260618-audio_fix_clean_v3-v1-1-ec1ee66fe455@oss.qualcomm.com/
Signed-off-by: Anandu Krishnan E <anandu.e@oss.qualcomm.com>
Adds deserializer and camera sensor nodes to the Talos device tree.
Talos features a single GMSL deserializer and exposes
a single GMSL camera.

Signed-off-by: Milen Mitkov <mmitkov@qti.qualcomm.com>
@qcomlnxci

Copy link
Copy Markdown

Test Matrix

Test Case *

@qlijarvis

Copy link
Copy Markdown

🔨 Build Failure Analysis — PR #755

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

Verdict

No compilation errors found. Both kernel builds (standard and RT) completed successfully. The workflow failure was caused by a CI artifact handling issue in the comment job, not by any compilation problems introduced by this PR.

Build Status:

  • ✅ Standard kernel build: SUCCESS
  • ✅ RT kernel build: SUCCESS
  • ❌ Comment job: FAILED (artifact collection issue - cat: 'artifacts/*/*.md': No such file or directory)

Root Cause: The workflow's comment job expected markdown artifacts that were not generated or uploaded by previous jobs, causing the comment aggregation step to fail. This is a CI pipeline configuration issue, not a code compilation issue.

PR Changes Summary:
This PR contains 9 patches modifying:

  • Device tree files (monaco, hamoa, talos)
  • PCI controller driver (pcie-qcom.c)
  • PHY driver (phy-qcom-qmp-pcie.c)
  • Network driver (dwmac-qcom-ethqos.c)
  • Kernel config (qcom.config)
  • FastRPC driver (fastrpc.c)

All changes compiled cleanly without errors or warnings-as-errors.

📎 Detailed analysis: Full report

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.

9 participants