From: YijieYang <yijie.yang@oss.qualcomm.com>
To: andersson@kernel.org, konradybcio@kernel.org, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org
Cc: linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, yijie.yang@oss.qualcomm.com,
Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>,
Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Subject: [PATCH v5 0/4] Initial patch set for PURWA-IOT-EVK
Date: Mon, 2 Feb 2026 15:35:44 +0800 [thread overview]
Message-ID: <20260202-purwa-v5-0-1f5a93578802@oss.qualcomm.com> (raw)
From: Yijie Yang <yijie.yang@oss.qualcomm.com>
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@oss.qualcomm.com>
---
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@oss.qualcomm.com/
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@oss.qualcomm.com
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@oss.qualcomm.com/
Changes in v5:
- Reorder nodes in purwa-iot-evk.dts.
- Update base commit.
- The DT binding change that fixes the DT warning for pcie3_phy is located at: https://lore.kernel.org/linux-arm-msm/20260119-topic-purwa_phy_shutup_warning-v1-1-997a692b31c6@oss.qualcomm.com/T/#u
- Link to v4: https://lore.kernel.org/r/20260116-purwa-v4-0-89b2adae9f09@oss.qualcomm.com
---
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: 6267b2da1b2d04847a1a8f441e138bc4a89435ee
change-id: 20251113-purwa-907ec75b4959
Best regards,
--
Yijie Yang <yijie.yang@oss.qualcomm.com>
next reply other threads:[~2026-02-02 7:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-02 7:35 YijieYang [this message]
2026-02-02 7:35 ` [PATCH v5 1/4] dt-bindings: arm: qcom: Document PURWA-IOT-EVK board YijieYang
2026-02-02 7:35 ` [PATCH v5 2/4] firmware: qcom: scm: Allow QSEECOM on PURWA-IOT-EVK YijieYang
2026-02-02 15:25 ` Abel Vesa
2026-02-02 7:35 ` [PATCH v5 3/4] arm64: dts: qcom: Add PURWA-IOT-SOM platform YijieYang
2026-02-02 15:24 ` Abel Vesa
2026-02-02 7:35 ` [PATCH v5 4/4] arm64: dts: qcom: Add base PURWA-IOT-EVK board YijieYang
2026-02-02 15:02 ` Konrad Dybcio
2026-02-02 15:24 ` Abel Vesa
2026-02-03 17:37 ` [PATCH v5 0/4] Initial patch set for PURWA-IOT-EVK Rob Herring
2026-02-04 1:42 ` Yijie Yang
2026-02-04 2:38 ` Dmitry Baryshkov
2026-02-04 2:52 ` Yijie Yang
2026-03-03 3:09 ` Jie Gan
2026-03-10 2:45 ` (subset) " Bjorn Andersson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260202-purwa-v5-0-1f5a93578802@oss.qualcomm.com \
--to=yijie.yang@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski@oss.qualcomm.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®