[PATCH v3 0/3] arm64: dts: qcom: hamoa-iot-evk: Enable M.2 Key E connector
From: Wei Deng
Date: Wed Jul 29 2026 - 07:01:13 EST
Describe the PCIe M.2 Key E connector on the Hamoa IoT EVK. This is
the DTS half of [1]. The pcie-m2 sub-ID patch is sent independently
as [PATCH v2]; the W_DISABLE2# else-branch patch is dropped in favor
of Chen-Yu Tsai's series [2].
Depends on: [2]
Changes in v3:
- patch 1/3: add uart14_ep, usb_2_m2_ep and pcie4_port0_ep stub endpoints
in hamoa.dtsi, so board DTS can reference them by label directly; remove
superfluous comment (Konrad).
- patch 3/3: use &uart14_ep, &usb_2_m2_ep and &pcie4_port0_ep label
references instead of re-defining port hierarchy in board DTS (Konrad).
- Link to v2: https://lore.kernel.org/r/20260723-hamoa-m2-dts-v2-v2-0-82254ac101fb@xxxxxxxxxxxxxxxx
Changes in v2:
- Split PATCH 1/3 of [1] into two commits (Dmitry).
- Add usb_2 HS port@0 (new patch 1/3) to pair with M.2 USB port@1.
- In patch 3/3: rename pcie4port0_ep -> pcie4_port0_ep (Konrad); add
port@2 for the USB BT variant; remove unused vreg_wcn_0p95 /
vreg_wcn_1p9 (sashiko). Konrad's v1 Reviewed-by is not carried:
the new port@2 endpoint and vreg cleanup were not part of the v1
review scope.
- Drop PATCH 3/3 of [1]; use [2] instead (Mani).
Link: [1] https://lore.kernel.org/all/20260709-fix-hamoa-m2-w-disable2-v1-0-5e725091266a@xxxxxxxxxxxxxxxx/
Link: [2] https://lore.kernel.org/all/20260721065413.2306137-1-wenst@xxxxxxxxxxxx/
Signed-off-by: Wei Deng <wei.deng@xxxxxxxxxxxxxxxx>
---
Wei Deng (3):
arm64: dts: qcom: hamoa: Number usb_2 HS port and add M.2 endpoint stubs
arm64: dts: qcom: hamoa: Add compatible to the PCIe Root Port
arm64: dts: qcom: hamoa-iot-evk: Describe the PCIe M.2 Key E connector
arch/arm64/boot/dts/qcom/hamoa-iot-evk.dts | 170 ++++++++++-------------------
arch/arm64/boot/dts/qcom/hamoa.dtsi | 29 ++++-
2 files changed, 87 insertions(+), 112 deletions(-)
---
base-commit: 290aaf24a551d5a0dce037e3fab30820f9113a10
change-id: 20260723-hamoa-m2-dts-v2-2067c7421569
Best regards,
--
Wei Deng <wei.deng@xxxxxxxxxxxxxxxx>