Documentation/devicetree/bindings/arm/qcom.yaml | 6 + arch/arm64/boot/dts/qcom/Makefile | 1 + arch/arm64/boot/dts/qcom/hamoa-iot-evk.dts | 1188 +---------------------- arch/arm64/boot/dts/qcom/hamoa-iot-som.dtsi | 607 +----------- arch/arm64/boot/dts/qcom/iq-x-iot-evk.dtsi | 1174 ++++++++++++++++++++++ arch/arm64/boot/dts/qcom/iq-x-iot-som.dtsi | 609 ++++++++++++ arch/arm64/boot/dts/qcom/purwa-iot-evk.dts | 100 ++ arch/arm64/boot/dts/qcom/purwa-iot-som.dtsi | 11 + drivers/firmware/qcom/qcom_scm.c | 1 + 9 files changed, 1920 insertions(+), 1777 deletions(-)
From: Yijie Yang <yijie.yang@oss.qualcomm.com>
Introduce the device tree, DT bindings, and driver modifications required
to bring up the PURWA-IOT-EVK evaluation board.
Purwa and Hamoa are IoT variants of x1p42100 and x1e80100, both based on
the IQ-X SoC series. Consequently, the two common files in this series are
prefixed with 'iq-x-iot' to reflect this relationship.
PURWA-IOT-EVK shares almost the same hardware design with HAMOA-IOT-EVK,
except for differences in the BOM. As a result, most of the DTS can be
shared between them.
The changes focus on two key hardware components: the PURWA-IOT-SOM and
the PURWA-IOT-EVK carrier board.
Hardware delta between Hamoa and Purwa:
- Display: Purwa’s display uses a different number of clocks, and its
frequency differs from Hamoa.
- GPU: Purwa requires a separate firmware compared to Hamoa.
- USB0: Purwa uses a PS8833 retimer, while Hamoa uses an FSUSB42 as the
SBU switch.
The PURWA-IOT-SOM is a compact System on Module that integrates the SoC,
GPIOs, and PMICs. It is designed to be modular and can be paired with
various carrier boards to support different use cases.
The PURWA-IOT-EVK is one such carrier board, designed for IoT scenarios.
It provides essential peripherals such as UART, on-board PMICs, and
USB-related components. Together, these components form a flexible and
scalable platform, and the changes enable their initial bring-up through
proper device tree configuration and driver support.
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
- PCIe6a and its PHY
- PCIe4 and its PHY
- Reserved memory regions
- Pinctrl
- NVMe
- ADSP, CDSP
- WLAN, Bluetooth (M.2 interface)
- USB DisplayPort
- Graphics
- Audio
Signed-off-by: Yijie Yang <yijie.yang@oss.qualcomm.com>
---
Yijie Yang (4):
firmware: qcom: scm: Allow QSEECOM on PURWA-IOT-EVK
dt-bindings: arm: qcom: Document PURWA-IOT-EVK board
arm64: dts: qcom: Commonize IQ-X-IOT DTSI
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/hamoa-iot-evk.dts | 1188 +----------------------
arch/arm64/boot/dts/qcom/hamoa-iot-som.dtsi | 607 +-----------
arch/arm64/boot/dts/qcom/iq-x-iot-evk.dtsi | 1174 ++++++++++++++++++++++
arch/arm64/boot/dts/qcom/iq-x-iot-som.dtsi | 609 ++++++++++++
arch/arm64/boot/dts/qcom/purwa-iot-evk.dts | 100 ++
arch/arm64/boot/dts/qcom/purwa-iot-som.dtsi | 11 +
drivers/firmware/qcom/qcom_scm.c | 1 +
9 files changed, 1920 insertions(+), 1777 deletions(-)
---
base-commit: bdedd93e9fe243f01c8277f81314560e352eeca8
change-id: 20251113-purwa-907ec75b4959
Best regards,
--
Yijie Yang <yijie.yang@oss.qualcomm.com>
On Mon, Dec 22, 2025 at 02:03:25PM +0800, YijieYang wrote: > From: Yijie Yang <yijie.yang@oss.qualcomm.com> > > Introduce the device tree, DT bindings, and driver modifications required > to bring up the PURWA-IOT-EVK evaluation board. > > Purwa and Hamoa are IoT variants of x1p42100 and x1e80100, both based on > the IQ-X SoC series. Consequently, the two common files in this series are > prefixed with 'iq-x-iot' to reflect this relationship. > > PURWA-IOT-EVK shares almost the same hardware design with HAMOA-IOT-EVK, > except for differences in the BOM. As a result, most of the DTS can be > shared between them. > > The changes focus on two key hardware components: the PURWA-IOT-SOM and > the PURWA-IOT-EVK carrier board. > > Hardware delta between Hamoa and Purwa: > - Display: Purwa’s display uses a different number of clocks, and its > frequency differs from Hamoa. > - GPU: Purwa requires a separate firmware compared to Hamoa. Is it just a separate firmware, or does it use a different _GPU_? > - USB0: Purwa uses a PS8833 retimer, while Hamoa uses an FSUSB42 as the > SBU switch. > -- With best wishes Dmitry
On 12/22/2025 5:18 PM, Dmitry Baryshkov wrote: > On Mon, Dec 22, 2025 at 02:03:25PM +0800, YijieYang wrote: >> From: Yijie Yang <yijie.yang@oss.qualcomm.com> >> >> Introduce the device tree, DT bindings, and driver modifications required >> to bring up the PURWA-IOT-EVK evaluation board. >> >> Purwa and Hamoa are IoT variants of x1p42100 and x1e80100, both based on >> the IQ-X SoC series. Consequently, the two common files in this series are >> prefixed with 'iq-x-iot' to reflect this relationship. >> >> PURWA-IOT-EVK shares almost the same hardware design with HAMOA-IOT-EVK, >> except for differences in the BOM. As a result, most of the DTS can be >> shared between them. >> >> The changes focus on two key hardware components: the PURWA-IOT-SOM and >> the PURWA-IOT-EVK carrier board. >> >> Hardware delta between Hamoa and Purwa: >> - Display: Purwa’s display uses a different number of clocks, and its >> frequency differs from Hamoa. >> - GPU: Purwa requires a separate firmware compared to Hamoa. > > Is it just a separate firmware, or does it use a different _GPU_? It uses a different GPU. > >> - USB0: Purwa uses a PS8833 retimer, while Hamoa uses an FSUSB42 as the >> SBU switch. >> > -- Best Regards, Yijie
On 12/23/25 3:12 AM, Yijie Yang wrote: > > > On 12/22/2025 5:18 PM, Dmitry Baryshkov wrote: >> On Mon, Dec 22, 2025 at 02:03:25PM +0800, YijieYang wrote: >>> From: Yijie Yang <yijie.yang@oss.qualcomm.com> >>> >>> Introduce the device tree, DT bindings, and driver modifications required >>> to bring up the PURWA-IOT-EVK evaluation board. >>> >>> Purwa and Hamoa are IoT variants of x1p42100 and x1e80100, both based on >>> the IQ-X SoC series. Consequently, the two common files in this series are >>> prefixed with 'iq-x-iot' to reflect this relationship. >>> >>> PURWA-IOT-EVK shares almost the same hardware design with HAMOA-IOT-EVK, >>> except for differences in the BOM. As a result, most of the DTS can be >>> shared between them. >>> >>> The changes focus on two key hardware components: the PURWA-IOT-SOM and >>> the PURWA-IOT-EVK carrier board. >>> >>> Hardware delta between Hamoa and Purwa: >>> - Display: Purwa’s display uses a different number of clocks, and its >>> frequency differs from Hamoa. >>> - GPU: Purwa requires a separate firmware compared to Hamoa. >> >> Is it just a separate firmware, or does it use a different _GPU_? > > It uses a different GPU. I think it would be useful to call this paragraph "Hardware delta between Hamoa-IoT-SoM/EVK and Purwa-IoT-whatever - because now Dmitry is asking about differences between Hamoa-the-SoC and Purwa-the-SoC which we expressed in purwa.dtsi Konrad > >> >>> - USB0: Purwa uses a PS8833 retimer, while Hamoa uses an FSUSB42 as the >>> SBU switch. >>> >> >
On 12/24/2025 1:27 AM, Konrad Dybcio wrote: > On 12/23/25 3:12 AM, Yijie Yang wrote: >> >> >> On 12/22/2025 5:18 PM, Dmitry Baryshkov wrote: >>> On Mon, Dec 22, 2025 at 02:03:25PM +0800, YijieYang wrote: >>>> From: Yijie Yang <yijie.yang@oss.qualcomm.com> >>>> >>>> Introduce the device tree, DT bindings, and driver modifications required >>>> to bring up the PURWA-IOT-EVK evaluation board. >>>> >>>> Purwa and Hamoa are IoT variants of x1p42100 and x1e80100, both based on >>>> the IQ-X SoC series. Consequently, the two common files in this series are >>>> prefixed with 'iq-x-iot' to reflect this relationship. >>>> >>>> PURWA-IOT-EVK shares almost the same hardware design with HAMOA-IOT-EVK, >>>> except for differences in the BOM. As a result, most of the DTS can be >>>> shared between them. >>>> >>>> The changes focus on two key hardware components: the PURWA-IOT-SOM and >>>> the PURWA-IOT-EVK carrier board. >>>> >>>> Hardware delta between Hamoa and Purwa: >>>> - Display: Purwa’s display uses a different number of clocks, and its >>>> frequency differs from Hamoa. >>>> - GPU: Purwa requires a separate firmware compared to Hamoa. >>> >>> Is it just a separate firmware, or does it use a different _GPU_? >> >> It uses a different GPU. > > I think it would be useful to call this paragraph "Hardware delta between > Hamoa-IoT-SoM/EVK and Purwa-IoT-whatever - because now Dmitry is asking > about differences between Hamoa-the-SoC and Purwa-the-SoC which we > expressed in purwa.dtsi I want to provide readers with a comprehensive comparison of the two boards, Hamoa-IoT-EVK and Purwa-IoT-EVK, covering all differences in both the SOM and the carrier board. > > Konrad > >> >>> >>>> - USB0: Purwa uses a PS8833 retimer, while Hamoa uses an FSUSB42 as the >>>> SBU switch. >>>> >>> >> -- Best Regards, Yijie
On 12/24/25 3:02 AM, Yijie Yang wrote: > > > On 12/24/2025 1:27 AM, Konrad Dybcio wrote: >> On 12/23/25 3:12 AM, Yijie Yang wrote: >>> >>> >>> On 12/22/2025 5:18 PM, Dmitry Baryshkov wrote: >>>> On Mon, Dec 22, 2025 at 02:03:25PM +0800, YijieYang wrote: >>>>> From: Yijie Yang <yijie.yang@oss.qualcomm.com> >>>>> >>>>> Introduce the device tree, DT bindings, and driver modifications required >>>>> to bring up the PURWA-IOT-EVK evaluation board. >>>>> >>>>> Purwa and Hamoa are IoT variants of x1p42100 and x1e80100, both based on >>>>> the IQ-X SoC series. Consequently, the two common files in this series are >>>>> prefixed with 'iq-x-iot' to reflect this relationship. >>>>> >>>>> PURWA-IOT-EVK shares almost the same hardware design with HAMOA-IOT-EVK, >>>>> except for differences in the BOM. As a result, most of the DTS can be >>>>> shared between them. >>>>> >>>>> The changes focus on two key hardware components: the PURWA-IOT-SOM and >>>>> the PURWA-IOT-EVK carrier board. >>>>> >>>>> Hardware delta between Hamoa and Purwa: >>>>> - Display: Purwa’s display uses a different number of clocks, and its >>>>> frequency differs from Hamoa. >>>>> - GPU: Purwa requires a separate firmware compared to Hamoa. >>>> >>>> Is it just a separate firmware, or does it use a different _GPU_? >>> >>> It uses a different GPU. >> >> I think it would be useful to call this paragraph "Hardware delta between >> Hamoa-IoT-SoM/EVK and Purwa-IoT-whatever - because now Dmitry is asking >> about differences between Hamoa-the-SoC and Purwa-the-SoC which we >> expressed in purwa.dtsi > > I want to provide readers with a comprehensive comparison of the two boards, Hamoa-IoT-EVK and Purwa-IoT-EVK, covering all differences in both the SOM and the carrier board. Of course - my comment points out that the specific wording of "delta between Hamoa and Purwa" may be easily misinterpreted as not what you're saying above Konrad
On 12/29/2025 8:18 PM, Konrad Dybcio wrote: > On 12/24/25 3:02 AM, Yijie Yang wrote: >> >> >> On 12/24/2025 1:27 AM, Konrad Dybcio wrote: >>> On 12/23/25 3:12 AM, Yijie Yang wrote: >>>> >>>> >>>> On 12/22/2025 5:18 PM, Dmitry Baryshkov wrote: >>>>> On Mon, Dec 22, 2025 at 02:03:25PM +0800, YijieYang wrote: >>>>>> From: Yijie Yang <yijie.yang@oss.qualcomm.com> >>>>>> >>>>>> Introduce the device tree, DT bindings, and driver modifications required >>>>>> to bring up the PURWA-IOT-EVK evaluation board. >>>>>> >>>>>> Purwa and Hamoa are IoT variants of x1p42100 and x1e80100, both based on >>>>>> the IQ-X SoC series. Consequently, the two common files in this series are >>>>>> prefixed with 'iq-x-iot' to reflect this relationship. >>>>>> >>>>>> PURWA-IOT-EVK shares almost the same hardware design with HAMOA-IOT-EVK, >>>>>> except for differences in the BOM. As a result, most of the DTS can be >>>>>> shared between them. >>>>>> >>>>>> The changes focus on two key hardware components: the PURWA-IOT-SOM and >>>>>> the PURWA-IOT-EVK carrier board. >>>>>> >>>>>> Hardware delta between Hamoa and Purwa: >>>>>> - Display: Purwa’s display uses a different number of clocks, and its >>>>>> frequency differs from Hamoa. >>>>>> - GPU: Purwa requires a separate firmware compared to Hamoa. >>>>> >>>>> Is it just a separate firmware, or does it use a different _GPU_? >>>> >>>> It uses a different GPU. >>> >>> I think it would be useful to call this paragraph "Hardware delta between >>> Hamoa-IoT-SoM/EVK and Purwa-IoT-whatever - because now Dmitry is asking >>> about differences between Hamoa-the-SoC and Purwa-the-SoC which we >>> expressed in purwa.dtsi >> >> I want to provide readers with a comprehensive comparison of the two boards, Hamoa-IoT-EVK and Purwa-IoT-EVK, covering all differences in both the SOM and the carrier board. > > Of course - my comment points out that the specific wording of "delta > between Hamoa and Purwa" may be easily misinterpreted as not what you're > saying above Okay, I’ll update it. > > Konrad -- Best Regards, Yijie
On Tue, Dec 23, 2025 at 06:27:05PM +0100, Konrad Dybcio wrote: > On 12/23/25 3:12 AM, Yijie Yang wrote: > > > > > > On 12/22/2025 5:18 PM, Dmitry Baryshkov wrote: > >> On Mon, Dec 22, 2025 at 02:03:25PM +0800, YijieYang wrote: > >>> From: Yijie Yang <yijie.yang@oss.qualcomm.com> > >>> > >>> Introduce the device tree, DT bindings, and driver modifications required > >>> to bring up the PURWA-IOT-EVK evaluation board. > >>> > >>> Purwa and Hamoa are IoT variants of x1p42100 and x1e80100, both based on > >>> the IQ-X SoC series. Consequently, the two common files in this series are > >>> prefixed with 'iq-x-iot' to reflect this relationship. > >>> > >>> PURWA-IOT-EVK shares almost the same hardware design with HAMOA-IOT-EVK, > >>> except for differences in the BOM. As a result, most of the DTS can be > >>> shared between them. > >>> > >>> The changes focus on two key hardware components: the PURWA-IOT-SOM and > >>> the PURWA-IOT-EVK carrier board. > >>> > >>> Hardware delta between Hamoa and Purwa: > >>> - Display: Purwa’s display uses a different number of clocks, and its > >>> frequency differs from Hamoa. > >>> - GPU: Purwa requires a separate firmware compared to Hamoa. > >> > >> Is it just a separate firmware, or does it use a different _GPU_? > > > > It uses a different GPU. > > I think it would be useful to call this paragraph "Hardware delta between > Hamoa-IoT-SoM/EVK and Purwa-IoT-whatever - because now Dmitry is asking > about differences between Hamoa-the-SoC and Purwa-the-SoC which we > expressed in purwa.dtsi Nah, I pointed out that the letter is incorrect. It's not just a different firmware for the _same_ GPU. It's a different GPU revision. -- With best wishes Dmitry
On 12/24/2025 3:09 AM, Dmitry Baryshkov wrote: > On Tue, Dec 23, 2025 at 06:27:05PM +0100, Konrad Dybcio wrote: >> On 12/23/25 3:12 AM, Yijie Yang wrote: >>> >>> >>> On 12/22/2025 5:18 PM, Dmitry Baryshkov wrote: >>>> On Mon, Dec 22, 2025 at 02:03:25PM +0800, YijieYang wrote: >>>>> From: Yijie Yang <yijie.yang@oss.qualcomm.com> >>>>> >>>>> Introduce the device tree, DT bindings, and driver modifications required >>>>> to bring up the PURWA-IOT-EVK evaluation board. >>>>> >>>>> Purwa and Hamoa are IoT variants of x1p42100 and x1e80100, both based on >>>>> the IQ-X SoC series. Consequently, the two common files in this series are >>>>> prefixed with 'iq-x-iot' to reflect this relationship. >>>>> >>>>> PURWA-IOT-EVK shares almost the same hardware design with HAMOA-IOT-EVK, >>>>> except for differences in the BOM. As a result, most of the DTS can be >>>>> shared between them. >>>>> >>>>> The changes focus on two key hardware components: the PURWA-IOT-SOM and >>>>> the PURWA-IOT-EVK carrier board. >>>>> >>>>> Hardware delta between Hamoa and Purwa: >>>>> - Display: Purwa’s display uses a different number of clocks, and its >>>>> frequency differs from Hamoa. >>>>> - GPU: Purwa requires a separate firmware compared to Hamoa. >>>> >>>> Is it just a separate firmware, or does it use a different _GPU_? >>> >>> It uses a different GPU. >> >> I think it would be useful to call this paragraph "Hardware delta between >> Hamoa-IoT-SoM/EVK and Purwa-IoT-whatever - because now Dmitry is asking >> about differences between Hamoa-the-SoC and Purwa-the-SoC which we >> expressed in purwa.dtsi > > Nah, I pointed out that the letter is incorrect. It's not just a > different firmware for the _same_ GPU. It's a different GPU revision. I’ll update the description here. > -- Best Regards, Yijie
© 2016 - 2026 Red Hat, Inc.