Re: [PATCH v4 0/4] Initial patch set for PURWA-IOT-EVK

From: Yijie Yang

Date: Sun Jan 18 2026 - 21:39:13 EST




On 1/16/2026 7:31 PM, Dmitry Baryshkov wrote:
On Fri, Jan 16, 2026 at 06:41:26PM +0800, YijieYang wrote:
From: Yijie Yang <yijie.yang@xxxxxxxxxxxxxxxx>

Introduce the device tree, DT bindings, and driver updates required to enable
the bring-up of the PURWA-IOT-EVK evaluation board. Focus is on two key
hardware components:

PURWA-IOT-SOM — A compact System-on-Module integrating the SoC, GPIOs, and
PMICs. Designed for modularity, it can pair with various carrier boards to
support diverse use cases.

PURWA-IOT-EVK — A carrier board tailored for IoT scenarios, providing
essential peripherals such as UART, on-board PMICs, and USB components.

Together, these components form a flexible and scalable platform. Initial
functionality is achieved through proper device tree configuration and driver
support.

The PURWA-IOT-EVK/SOM shares most of its hardware design with
HAMOA-IOT-EVK/SOM, differing primarily in the BOM. Consequently, the DTS files
are largely similar. Both platforms belong to Qualcomm’s IQ-X family. For more
details on the IQ-X series, see:
https://www.qualcomm.com/internet-of-things/products/iq-x-series

Hardware differences between HAMOA-IOT and PURWA-IOT:
- Display — PURWA uses a different number of clocks and frequency compared to
HAMOA.
- GPU — PURWA integrates a different GPU.
- USB0 — PURWA uses a PS8833 retimer, while HAMOA employs an FSUSB42 as the
SBU switch.

Features added and enabled:
- UART
- On-board regulators
- Regulators on the SOM
- PMIC GLINK
- USB0 through USB6 and their PHYs
- Embedded USB (eUSB) repeaters
- USB Type-C mux
- PCIe3, PCIe4, PCIe5, PCIe6a
- Reserved memory regions
- Pinctrl
- NVMe
- ADSP, CDSP
- WLAN, Bluetooth (M.2 interface)
- USB DisplayPort and eDP
- Graphics
- Audio
- TPM

Signed-off-by: Yijie Yang <yijie.yang@xxxxxxxxxxxxxxxx>
---
Changes in v4:
- EDITME: describe what is new in this series revision.
- EDITME: use bulletpoints and terse descriptions.

Oh no. B4 probably even warned you about not sending it out.

From this changelog I can assume that nothing has changed. Is it
correct?

This section was generated automatically by b4 and was not reviewed carefully. The actual list of changes is in the section below.


- Link to v3: https://lore.kernel.org/r/20260113-purwa-v3-0-16eefacbdce9@xxxxxxxxxxxxxxxx

Changes in v2:
- Update the GPU firmware path.
- Update the description in the cover letter.
- Reorder the patches.
- Use separate DTS files for Purwa and Hamoa.
- Update base commit.
- Link to v1: https://lore.kernel.org/all/20251222-purwa-v1-0-14ab9316e5ff@xxxxxxxxxxxxxxxx/

Changes in v3:
- Delete unused PMIC and thermal nodes.
- Add WiFi node.
- Add display backlight node.
- Add connectors and VBUS regulators for USB3 and USB6.
- Enable PCIe3 and PCIe5; add PCIe ports along with reset and wake-up GPIOs.
- Link to v2: https://lore.kernel.org/r/20260109-purwa-v2-0-f39ee10684cb@xxxxxxxxxxxxxxxx

Changes in v4:
- Enable TPM.
- Update the descriptions for video and the USB OF graph.
- Link to v3: https://lore.kernel.org/all/20260113-purwa-v3-0-16eefacbdce9@xxxxxxxxxxxxxxxx/

Here.


---
Yijie Yang (4):
dt-bindings: arm: qcom: Document PURWA-IOT-EVK board
firmware: qcom: scm: Allow QSEECOM on PURWA-IOT-EVK
arm64: dts: qcom: Add PURWA-IOT-SOM platform
arm64: dts: qcom: Add base PURWA-IOT-EVK board

Documentation/devicetree/bindings/arm/qcom.yaml | 6 +
arch/arm64/boot/dts/qcom/Makefile | 1 +
arch/arm64/boot/dts/qcom/purwa-iot-evk.dts | 1549 +++++++++++++++++++++++
arch/arm64/boot/dts/qcom/purwa-iot-som.dtsi | 685 ++++++++++
drivers/firmware/qcom/qcom_scm.c | 1 +
5 files changed, 2242 insertions(+)
---
base-commit: 377054868ffa544991cc491ecc4016589fc58565
change-id: 20251113-purwa-907ec75b4959

Best regards,
--
Yijie Yang <yijie.yang@xxxxxxxxxxxxxxxx>



--
Best Regards,
Yijie