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(+)
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 v4:
- EDITME: describe what is new in this series revision.
- EDITME: use bulletpoints and terse descriptions.
- Link to v3: https://lore.kernel.org/r/20260113-purwa-v3-0-16eefacbdce9@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/
---
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@oss.qualcomm.com>
On Fri, 16 Jan 2026 18:41:26 +0800, YijieYang wrote: > 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 v4: > - EDITME: describe what is new in this series revision. > - EDITME: use bulletpoints and terse descriptions. > - Link to v3: https://lore.kernel.org/r/20260113-purwa-v3-0-16eefacbdce9@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/ > > --- > 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@oss.qualcomm.com> > > > My bot found new DTB warnings on the .dts files added or changed in this series. Some warnings may be from an existing SoC .dtsi. Or perhaps the warnings are fixed by another series. Ultimately, it is up to the platform maintainer whether these warnings are acceptable or not. No need to reply unless the platform maintainer has comments. If you already ran DT checks and didn't see these error(s), then make sure dt-schema is up to date: pip3 install dtschema --upgrade This patch series was applied (using b4) to base: Base: 377054868ffa544991cc491ecc4016589fc58565 (use --merge-base to override) If this is not the correct base, please add 'base-commit' tag (or use b4 which does this automatically) New warnings running 'make CHECK_DTBS=y for arch/arm64/boot/dts/qcom/' for 20260116-purwa-v4-0-89b2adae9f09@oss.qualcomm.com: arch/arm64/boot/dts/qcom/purwa-iot-evk.dtb: phy@1bd4000 (qcom,x1p42100-qmp-gen4x4-pcie-phy): 'qcom,4ln-config-sel' is a required property from schema $id: http://devicetree.org/schemas/phy/qcom,sc8280xp-qmp-pcie-phy.yaml
On Fri, Jan 16, 2026 at 06:41:26PM +0800, YijieYang wrote: > 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 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? > - Link to v3: https://lore.kernel.org/r/20260113-purwa-v3-0-16eefacbdce9@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/ > > --- > 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@oss.qualcomm.com> > -- With best wishes Dmitry
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@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 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@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/ 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@oss.qualcomm.com> >> > -- Best Regards, Yijie
On Mon, Jan 19, 2026 at 10:39:04AM +0800, Yijie Yang wrote: > > > 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@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 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. But why????? Why do you ignore what was done for you and write it on your own, reversing the order, etc? And even if you decided to ignore it for any reason, why didn't you delete it? > > > > > > - Link to v3: https://lore.kernel.org/r/20260113-purwa-v3-0-16eefacbdce9@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/ > > 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@oss.qualcomm.com> > > > > > > > -- > Best Regards, > Yijie > -- With best wishes Dmitry
On 1/19/2026 2:34 PM, Dmitry Baryshkov wrote: > On Mon, Jan 19, 2026 at 10:39:04AM +0800, Yijie Yang wrote: >> >> >> 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@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 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. > > But why????? Why do you ignore what was done for you and write it on > your own, reversing the order, etc? And even if you decided to ignore it > for any reason, why didn't you delete it? The confusion was caused by mixing b4 and git format-patch to handle fine‑grained patch formatting. The Git configuration Konrad suggested did not work for me. I ran b4 prep --manual-reroll <msg-id> to allow b4 to track the upstream thread, which caused this section to be generated automatically. I did not notice this and mistakenly re‑wrote it myself. > >> >>> >>>> - Link to v3: https://lore.kernel.org/r/20260113-purwa-v3-0-16eefacbdce9@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/ >> >> 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@oss.qualcomm.com> >>>> >>> >> >> -- >> Best Regards, >> Yijie >> > -- Best Regards, Yijie
On 1/19/26 7:54 AM, Yijie Yang wrote:
>
>
> On 1/19/2026 2:34 PM, Dmitry Baryshkov wrote:
>> On Mon, Jan 19, 2026 at 10:39:04AM +0800, Yijie Yang wrote:
[...]
>>>>> 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.
>>
>> But why????? Why do you ignore what was done for you and write it on
>> your own, reversing the order, etc? And even if you decided to ignore it
>> for any reason, why didn't you delete it?
>
> The confusion was caused by mixing b4 and git format-patch to handle fine‑grained patch formatting. The Git configuration Konrad suggested did not work for me. I ran b4 prep --manual-reroll <msg-id> to allow b4 to track the upstream thread, which caused this section to be generated automatically. I did not notice this and mistakenly re‑wrote it myself.
I found that I have additional options set in my *local* gitconfig:
[diff]
renameLimit = 999999
rename = true
algorithm = histogram
renames = copies
Perhaps that was the missing piece!
Konrad
On 19/01/2026 14:35, Konrad Dybcio wrote: > On 1/19/26 7:54 AM, Yijie Yang wrote: >> >> >> On 1/19/2026 2:34 PM, Dmitry Baryshkov wrote: >>> On Mon, Jan 19, 2026 at 10:39:04AM +0800, Yijie Yang wrote: > > [...] > >>>>>> 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. >>> >>> But why????? Why do you ignore what was done for you and write it on >>> your own, reversing the order, etc? And even if you decided to ignore it >>> for any reason, why didn't you delete it? >> >> The confusion was caused by mixing b4 and git format-patch to handle fine‑grained patch formatting. The Git configuration Konrad suggested did not work for me. I ran b4 prep --manual-reroll <msg-id> to allow b4 to track the upstream thread, which caused this section to be generated automatically. I did not notice this and mistakenly re‑wrote it myself. > > I found that I have additional options set in my *local* gitconfig: > > [diff] > renameLimit = 999999 > rename = true This one does not exist. You wanted "renames" but you set it two lines below. > algorithm = histogram > renames = copies > > Perhaps that was the missing piece! > > Konrad Best regards, Krzysztof
On 1/19/26 2:51 PM, Krzysztof Kozlowski wrote: > On 19/01/2026 14:35, Konrad Dybcio wrote: >> On 1/19/26 7:54 AM, Yijie Yang wrote: >>> >>> >>> On 1/19/2026 2:34 PM, Dmitry Baryshkov wrote: >>>> On Mon, Jan 19, 2026 at 10:39:04AM +0800, Yijie Yang wrote: >> >> [...] >> >>>>>>> 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. >>>> >>>> But why????? Why do you ignore what was done for you and write it on >>>> your own, reversing the order, etc? And even if you decided to ignore it >>>> for any reason, why didn't you delete it? >>> >>> The confusion was caused by mixing b4 and git format-patch to handle fine‑grained patch formatting. The Git configuration Konrad suggested did not work for me. I ran b4 prep --manual-reroll <msg-id> to allow b4 to track the upstream thread, which caused this section to be generated automatically. I did not notice this and mistakenly re‑wrote it myself. >> >> I found that I have additional options set in my *local* gitconfig: >> >> [diff] >> renameLimit = 999999 >> rename = true > > This one does not exist. You wanted "renames" but you set it two lines > below. thanks Konrad
On 1/19/2026 9:52 PM, Konrad Dybcio wrote: > On 1/19/26 2:51 PM, Krzysztof Kozlowski wrote: >> On 19/01/2026 14:35, Konrad Dybcio wrote: >>> On 1/19/26 7:54 AM, Yijie Yang wrote: >>>> >>>> >>>> On 1/19/2026 2:34 PM, Dmitry Baryshkov wrote: >>>>> On Mon, Jan 19, 2026 at 10:39:04AM +0800, Yijie Yang wrote: >>> >>> [...] >>> >>>>>>>> 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. >>>>> >>>>> But why????? Why do you ignore what was done for you and write it on >>>>> your own, reversing the order, etc? And even if you decided to ignore it >>>>> for any reason, why didn't you delete it? >>>> >>>> The confusion was caused by mixing b4 and git format-patch to handle fine‑grained patch formatting. The Git configuration Konrad suggested did not work for me. I ran b4 prep --manual-reroll <msg-id> to allow b4 to track the upstream thread, which caused this section to be generated automatically. I did not notice this and mistakenly re‑wrote it myself. >>> >>> I found that I have additional options set in my *local* gitconfig: >>> >>> [diff] >>> renameLimit = 999999 >>> rename = true >> >> This one does not exist. You wanted "renames" but you set it two lines >> below. I tried this, but these config options cannot replace --find-copies-harder. Since hamoa-iot-evk.dts and hamoa-iot-som.dtsi are not modified in this commit, Git will not consider them unless --find-copies-harder is used. > > thanks > > Konrad -- Best Regards, Yijie
© 2016 - 2026 Red Hat, Inc.