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

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

[YijieYang]

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>

[PATCH v4 1/4] dt-bindings: arm: qcom: Document PURWA-IOT-EVK board

[YijieYang]

From: Yijie Yang <yijie.yang@oss.qualcomm.com>

Document the device tree bindings for the PURWA-IOT-EVK board, which
uses the Qualcomm X1P42100 SoC.

Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
Signed-off-by: Yijie Yang <yijie.yang@oss.qualcomm.com>
---
 Documentation/devicetree/bindings/arm/qcom.yaml | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/Documentation/devicetree/bindings/arm/qcom.yaml b/Documentation/devicetree/bindings/arm/qcom.yaml
index d48c625d3fc4..59b8a4267c14 100644
--- a/Documentation/devicetree/bindings/arm/qcom.yaml
+++ b/Documentation/devicetree/bindings/arm/qcom.yaml
@@ -1122,6 +1122,12 @@ properties:
           - const: microsoft,denali
           - const: qcom,x1e80100
 
+      - items:
+          - enum:
+              - qcom,purwa-iot-evk
+          - const: qcom,purwa-iot-som
+          - const: qcom,x1p42100
+
       - items:
           - enum:
               - asus,zenbook-a14-ux3407qa-lcd
-- 
2.34.1

[PATCH v4 2/4] firmware: qcom: scm: Allow QSEECOM on PURWA-IOT-EVK

[YijieYang]

From: Yijie Yang <yijie.yang@oss.qualcomm.com>

Add the Purwa-IoT-EVK board to the list to enable access to EFI variables.

Guarantee that subsystems relying on SCM services can access secure-world
features. This change improves reliability and prevents missing
functionality or boot-time issues by making service availability explicit.

Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Signed-off-by: Yijie Yang <yijie.yang@oss.qualcomm.com>
---
 drivers/firmware/qcom/qcom_scm.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/drivers/firmware/qcom/qcom_scm.c b/drivers/firmware/qcom/qcom_scm.c
index 1ced6022c716..9a046b09275d 100644
--- a/drivers/firmware/qcom/qcom_scm.c
+++ b/drivers/firmware/qcom/qcom_scm.c
@@ -2022,6 +2022,7 @@ static const struct of_device_id qcom_scm_qseecom_allowlist[] __maybe_unused = {
 	{ .compatible = "microsoft,romulus13", },
 	{ .compatible = "microsoft,romulus15", },
 	{ .compatible = "qcom,hamoa-iot-evk" },
+	{ .compatible = "qcom,purwa-iot-evk" },
 	{ .compatible = "qcom,sc8180x-primus" },
 	{ .compatible = "qcom,x1e001de-devkit" },
 	{ .compatible = "qcom,x1e80100-crd" },
-- 
2.34.1

[PATCH v4 3/4] arm64: dts: qcom: Add PURWA-IOT-SOM platform

[YijieYang]

From: Yijie Yang <yijie.yang@oss.qualcomm.com>

The PURWA-IOT-SOM is a compact computing module that integrates a System
on Chip (SoC) — specifically the x1p42100 — along with essential
components optimized for IoT applications. It is designed to be mounted on
carrier boards, enabling the development of complete embedded systems.

Purwa uses a slightly different Iris HW revision (8.1.2 on Hamoa, 8.1.11 on
Purwa). Support will be added later.

Make the following peripherals on the SOM enabled:
- Regulators on the SOM
- Reserved memory regions
- PCIe3, PCIe4, PCIe5, PCIe6a
- USB0 through USB6 and their PHYs
- ADSP, CDSP
- Graphic

Signed-off-by: Yijie Yang <yijie.yang@oss.qualcomm.com>
---
 .../qcom/{hamoa-iot-som.dtsi => purwa-iot-som.dtsi}   | 11 +++++------
 1 file changed, 5 insertions(+), 6 deletions(-)
 copy arch/arm64/boot/dts/qcom/{hamoa-iot-som.dtsi => purwa-iot-som.dtsi} (99%)

diff --git a/arch/arm64/boot/dts/qcom/hamoa-iot-som.dtsi b/arch/arm64/boot/dts/qcom/purwa-iot-som.dtsi
similarity index 99%
copy from arch/arm64/boot/dts/qcom/hamoa-iot-som.dtsi
copy to arch/arm64/boot/dts/qcom/purwa-iot-som.dtsi
index b8e3e04a6fbd..fb90beb1096f 100644
--- a/arch/arm64/boot/dts/qcom/hamoa-iot-som.dtsi
+++ b/arch/arm64/boot/dts/qcom/purwa-iot-som.dtsi
@@ -3,11 +3,14 @@
  * Copyright (c) Qualcomm Technologies, Inc. and/or its subsidiaries.
  */
 
-#include "hamoa.dtsi"
+#include "purwa.dtsi"
 #include "hamoa-pmics.dtsi"
 #include <dt-bindings/gpio/gpio.h>
 #include <dt-bindings/regulator/qcom,rpmh-regulator.h>
 
+/delete-node/ &pmc8380_6;
+/delete-node/ &pmc8380_6_thermal;
+
 / {
 	reserved-memory {
 		linux,cma {
@@ -378,16 +381,12 @@ vreg_l3j_0p8: ldo3 {
 	};
 };
 
-&iris {
-	status = "okay";
-};
-
 &gpu {
 	status = "okay";
 };
 
 &gpu_zap_shader {
-	firmware-name = "qcom/x1e80100/gen70500_zap.mbn";
+	firmware-name = "qcom/x1p42100/gen71500_zap.mbn";
 };
 
 &pcie3 {
-- 
2.34.1

Re: [PATCH v4 3/4] arm64: dts: qcom: Add PURWA-IOT-SOM platform

[Konrad Dybcio]

On 1/16/26 11:41 AM, YijieYang wrote:
> From: Yijie Yang <yijie.yang@oss.qualcomm.com>
> 
> The PURWA-IOT-SOM is a compact computing module that integrates a System
> on Chip (SoC) — specifically the x1p42100 — along with essential
> components optimized for IoT applications. It is designed to be mounted on
> carrier boards, enabling the development of complete embedded systems.
> 
> Purwa uses a slightly different Iris HW revision (8.1.2 on Hamoa, 8.1.11 on
> Purwa). Support will be added later.
> 
> Make the following peripherals on the SOM enabled:
> - Regulators on the SOM
> - Reserved memory regions
> - PCIe3, PCIe4, PCIe5, PCIe6a
> - USB0 through USB6 and their PHYs
> - ADSP, CDSP
> - Graphic
> 
> Signed-off-by: Yijie Yang <yijie.yang@oss.qualcomm.com>
> ---

Reviewed-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>

Konrad

[PATCH v4 4/4] arm64: dts: qcom: Add base PURWA-IOT-EVK board

[YijieYang]

From: Yijie Yang <yijie.yang@oss.qualcomm.com>

The PURWA-IOT-EVK is an evaluation platform for IoT products, composed of
the Purwa IoT SoM and a carrier board. Together, they form a complete
embedded system capable of booting to UART.

PURWA-IOT-EVK uses the PS8833 as a retimer for USB0, unlike HAMOA-IOT-EVK.
Meanwhile, USB0 bypasses the SBU selector FSUSB42.

Make the following peripherals on the carrier board enabled:
- UART
- On-board regulators
- USB Type-C mux
- Pinctrl
- Embedded USB (EUSB) repeaters
- NVMe
- pmic-glink
- USB DisplayPorts
- Bluetooth
- WLAN
- Audio
- PCIe ports for PCIe3 through PCIe6a
- TPM

Signed-off-by: Yijie Yang <yijie.yang@oss.qualcomm.com>
---
 arch/arm64/boot/dts/qcom/Makefile             |   1 +
 .../{hamoa-iot-evk.dts => purwa-iot-evk.dts}  | 112 ++++++++++++------
 2 files changed, 75 insertions(+), 38 deletions(-)
 copy arch/arm64/boot/dts/qcom/{hamoa-iot-evk.dts => purwa-iot-evk.dts} (95%)

diff --git a/arch/arm64/boot/dts/qcom/Makefile b/arch/arm64/boot/dts/qcom/Makefile
index a5d6f451f85c..d276b3cf14ee 100644
--- a/arch/arm64/boot/dts/qcom/Makefile
+++ b/arch/arm64/boot/dts/qcom/Makefile
@@ -126,6 +126,7 @@ dtb-$(CONFIG_ARCH_QCOM)	+= msm8998-sony-xperia-yoshino-lilac.dtb
 dtb-$(CONFIG_ARCH_QCOM)	+= msm8998-sony-xperia-yoshino-maple.dtb
 dtb-$(CONFIG_ARCH_QCOM)	+= msm8998-sony-xperia-yoshino-poplar.dtb
 dtb-$(CONFIG_ARCH_QCOM)	+= msm8998-xiaomi-sagit.dtb
+dtb-$(CONFIG_ARCH_QCOM)	+= purwa-iot-evk.dtb
 dtb-$(CONFIG_ARCH_QCOM)	+= qcm6490-fairphone-fp5.dtb
 dtb-$(CONFIG_ARCH_QCOM)	+= qcm6490-idp.dtb
 dtb-$(CONFIG_ARCH_QCOM)	+= qcm6490-particle-tachyon.dtb
diff --git a/arch/arm64/boot/dts/qcom/hamoa-iot-evk.dts b/arch/arm64/boot/dts/qcom/purwa-iot-evk.dts
similarity index 95%
copy from arch/arm64/boot/dts/qcom/hamoa-iot-evk.dts
copy to arch/arm64/boot/dts/qcom/purwa-iot-evk.dts
index 2390648a248f..2a2cbcd9eace 100644
--- a/arch/arm64/boot/dts/qcom/hamoa-iot-evk.dts
+++ b/arch/arm64/boot/dts/qcom/purwa-iot-evk.dts
@@ -6,12 +6,12 @@
 /dts-v1/;
 
 #include <dt-bindings/leds/common.h>
-#include "hamoa-iot-som.dtsi"
+#include "purwa-iot-som.dtsi"
 #include <dt-bindings/pinctrl/qcom,pmic-gpio.h>
 
 / {
-	model = "Qualcomm Technologies, Inc. Hamoa IoT EVK";
-	compatible = "qcom,hamoa-iot-evk", "qcom,hamoa-iot-som", "qcom,x1e80100";
+	model = "Qualcomm Technologies, Inc. Purwa IoT EVK";
+	compatible = "qcom,purwa-iot-evk", "qcom,purwa-iot-som", "qcom,x1p42100";
 	chassis-type = "embedded";
 
 	aliases {
@@ -118,15 +118,15 @@ port@1 {
 					reg = <1>;
 
 					pmic_glink_ss0_ss_in: endpoint {
-						remote-endpoint = <&usb_1_ss0_qmpphy_out>;
+						remote-endpoint = <&retimer_ss0_ss_out>;
 					};
 				};
 
 				port@2 {
 					reg = <2>;
 
-					pmic_glink_ss0_sbu: endpoint {
-						remote-endpoint = <&usb_1_ss0_sbu_mux>;
+					pmic_glink_ss0_con_sbu_in: endpoint {
+						remote-endpoint = <&retimer_ss0_con_sbu_out>;
 					};
 				};
 			};
@@ -618,25 +618,6 @@ platform {
 		};
 	};
 
-	usb-1-ss0-sbu-mux {
-		compatible = "onnn,fsusb42", "gpio-sbu-mux";
-
-		enable-gpios = <&tlmm 168 GPIO_ACTIVE_LOW>;
-		select-gpios = <&tlmm 167 GPIO_ACTIVE_HIGH>;
-
-		pinctrl-0 = <&usb_1_ss0_sbu_default>;
-		pinctrl-names = "default";
-
-		mode-switch;
-		orientation-switch;
-
-		port {
-			usb_1_ss0_sbu_mux: endpoint {
-				remote-endpoint = <&pmic_glink_ss0_sbu>;
-			};
-		};
-	};
-
 	wcn7850-pmu {
 		compatible = "qcom,wcn7850-pmu";
 
@@ -753,6 +734,63 @@ retimer_ss2_con_sbu_out: endpoint {
 	};
 };
 
+&i2c3 {
+	clock-frequency = <400000>;
+
+	status = "okay";
+
+	typec-mux@8 {
+		compatible = "parade,ps8830";
+		reg = <0x8>;
+
+		clocks = <&rpmhcc RPMH_RF_CLK4>;
+
+		vdd-supply = <&vreg_rtmr0_1p15>;
+		vdd33-supply = <&vreg_rtmr0_3p3>;
+		vdd33-cap-supply = <&vreg_rtmr0_3p3>;
+		vddar-supply = <&vreg_rtmr0_1p15>;
+		vddat-supply = <&vreg_rtmr0_1p15>;
+		vddio-supply = <&vreg_rtmr0_1p8>;
+
+		reset-gpios = <&pm8550_gpios 10 GPIO_ACTIVE_LOW>;
+
+		pinctrl-0 = <&rtmr0_default>;
+		pinctrl-names = "default";
+
+		retimer-switch;
+		orientation-switch;
+
+		ports {
+			#address-cells = <1>;
+			#size-cells = <0>;
+
+			port@0 {
+				reg = <0>;
+
+				retimer_ss0_ss_out: endpoint {
+					remote-endpoint = <&pmic_glink_ss0_ss_in>;
+				};
+			};
+
+			port@1 {
+				reg = <1>;
+
+				retimer_ss0_ss_in: endpoint {
+					remote-endpoint = <&usb_1_ss0_qmpphy_out>;
+				};
+			};
+
+			port@2 {
+				reg = <2>;
+
+				retimer_ss0_con_sbu_out: endpoint {
+					remote-endpoint = <&pmic_glink_ss0_con_sbu_in>;
+				};
+			};
+		};
+	};
+};
+
 &i2c5 {
 	clock-frequency = <400000>;
 
@@ -1102,9 +1140,7 @@ edp_bl_reg_en: edp-bl-reg-en-state {
 		pins = "gpio10";
 		function = "normal";
 	};
-};
 
-&pmc8380_3_gpios {
 	pm_sde7_aux_3p3_en: pcie-aux-3p3-default-state {
 		pins = "gpio8";
 		function = "normal";
@@ -1144,6 +1180,16 @@ &pmk8550_pwm {
 	status = "okay";
 };
 
+&spi11 {
+	status = "okay";
+
+	tpm@0 {
+		compatible = "st,st33htpm-spi", "tcg,tpm_tis-spi";
+		reg = <0>;
+		spi-max-frequency = <20000000>;
+	};
+};
+
 &smb2360_0 {
 	status = "okay";
 };
@@ -1171,16 +1217,6 @@ &smb2360_2_eusb2_repeater {
 	vdd3-supply = <&vreg_l8b_3p0>;
 };
 
-&spi11 {
-	status = "okay";
-
-	tpm@0 {
-		compatible = "st,st33htpm-spi", "tcg,tpm_tis-spi";
-		reg = <0>;
-		spi-max-frequency = <20000000>;
-	};
-};
-
 &swr0 {
 	status = "okay";
 
@@ -1470,7 +1506,7 @@ &usb_1_ss0_hsphy {
 };
 
 &usb_1_ss0_qmpphy_out {
-	remote-endpoint = <&pmic_glink_ss0_ss_in>;
+	remote-endpoint = <&retimer_ss0_ss_in>;
 };
 
 &usb_1_ss1_dwc3_hs {
-- 
2.34.1

Re: [PATCH v4 4/4] arm64: dts: qcom: Add base PURWA-IOT-EVK board

[Krzysztof Kozlowski]

On 16/01/2026 11:41, YijieYang wrote:
> From: Yijie Yang <yijie.yang@oss.qualcomm.com>
> 
> The PURWA-IOT-EVK is an evaluation platform for IoT products, composed of
> the Purwa IoT SoM and a carrier board. Together, they form a complete
> embedded system capable of booting to UART.
> 
> PURWA-IOT-EVK uses the PS8833 as a retimer for USB0, unlike HAMOA-IOT-EVK.
> Meanwhile, USB0 bypasses the SBU selector FSUSB42.
> 

NAK.

Warnings were reported at v3. Did you address them? No, you completely
ignored them, so warnings are reported again at v4.

What do you think these emails are for?

Best regards,
Krzysztof

Re: [PATCH v4 4/4] arm64: dts: qcom: Add base PURWA-IOT-EVK board

[Yijie Yang]

On 1/17/2026 12:19 AM, Krzysztof Kozlowski wrote:
> On 16/01/2026 11:41, YijieYang wrote:
>> From: Yijie Yang <yijie.yang@oss.qualcomm.com>
>>
>> The PURWA-IOT-EVK is an evaluation platform for IoT products, composed of
>> the Purwa IoT SoM and a carrier board. Together, they form a complete
>> embedded system capable of booting to UART.
>>
>> PURWA-IOT-EVK uses the PS8833 as a retimer for USB0, unlike HAMOA-IOT-EVK.
>> Meanwhile, USB0 bypasses the SBU selector FSUSB42.
>>
> 
> NAK.
> 
> Warnings were reported at v3. Did you address them? No, you completely
> ignored them, so warnings are reported again at v4.
> 
> What do you think these emails are for?

This warning is caused by the pcie3_phy node in purwa.dtsi, which is not 
introduced by this patch set. Since it does not impact functionality, 
would it be appropriate to fix it in a separate patch?

> 
> Best regards,
> Krzysztof

-- 
Best Regards,
Yijie

Re: [PATCH v4 4/4] arm64: dts: qcom: Add base PURWA-IOT-EVK board

[Dmitry Baryshkov]

On Mon, Jan 19, 2026 at 11:13:29AM +0800, Yijie Yang wrote:
> 
> 
> On 1/17/2026 12:19 AM, Krzysztof Kozlowski wrote:
> > On 16/01/2026 11:41, YijieYang wrote:
> > > From: Yijie Yang <yijie.yang@oss.qualcomm.com>
> > > 
> > > The PURWA-IOT-EVK is an evaluation platform for IoT products, composed of
> > > the Purwa IoT SoM and a carrier board. Together, they form a complete
> > > embedded system capable of booting to UART.
> > > 
> > > PURWA-IOT-EVK uses the PS8833 as a retimer for USB0, unlike HAMOA-IOT-EVK.
> > > Meanwhile, USB0 bypasses the SBU selector FSUSB42.
> > > 
> > 
> > NAK.
> > 
> > Warnings were reported at v3. Did you address them? No, you completely
> > ignored them, so warnings are reported again at v4.
> > 
> > What do you think these emails are for?
> 
> This warning is caused by the pcie3_phy node in purwa.dtsi, which is not
> introduced by this patch set. Since it does not impact functionality, would
> it be appropriate to fix it in a separate patch?

Why can't it be fixed as a part of this patchset?

> 
> > 
> > Best regards,
> > Krzysztof
> 
> -- 
> Best Regards,
> Yijie
> 

-- 
With best wishes
Dmitry

Re: [PATCH v4 4/4] arm64: dts: qcom: Add base PURWA-IOT-EVK board

[Yijie Yang]

On 1/19/2026 2:33 PM, Dmitry Baryshkov wrote:
> On Mon, Jan 19, 2026 at 11:13:29AM +0800, Yijie Yang wrote:
>>
>>
>> On 1/17/2026 12:19 AM, Krzysztof Kozlowski wrote:
>>> On 16/01/2026 11:41, YijieYang wrote:
>>>> From: Yijie Yang <yijie.yang@oss.qualcomm.com>
>>>>
>>>> The PURWA-IOT-EVK is an evaluation platform for IoT products, composed of
>>>> the Purwa IoT SoM and a carrier board. Together, they form a complete
>>>> embedded system capable of booting to UART.
>>>>
>>>> PURWA-IOT-EVK uses the PS8833 as a retimer for USB0, unlike HAMOA-IOT-EVK.
>>>> Meanwhile, USB0 bypasses the SBU selector FSUSB42.
>>>>
>>>
>>> NAK.
>>>
>>> Warnings were reported at v3. Did you address them? No, you completely
>>> ignored them, so warnings are reported again at v4.
>>>
>>> What do you think these emails are for?
>>
>> This warning is caused by the pcie3_phy node in purwa.dtsi, which is not
>> introduced by this patch set. Since it does not impact functionality, would
>> it be appropriate to fix it in a separate patch?
> 
> Why can't it be fixed as a part of this patchset?

I will fix this after evaluating the impact of this feature.

> 
>>
>>>
>>> Best regards,
>>> Krzysztof
>>
>> -- 
>> Best Regards,
>> Yijie
>>
> 

-- 
Best Regards,
Yijie

Re: [PATCH v4 4/4] arm64: dts: qcom: Add base PURWA-IOT-EVK board

[Yijie Yang]

On 1/19/2026 2:33 PM, Dmitry Baryshkov wrote:
> On Mon, Jan 19, 2026 at 11:13:29AM +0800, Yijie Yang wrote:
>>
>>
>> On 1/17/2026 12:19 AM, Krzysztof Kozlowski wrote:
>>> On 16/01/2026 11:41, YijieYang wrote:
>>>> From: Yijie Yang <yijie.yang@oss.qualcomm.com>
>>>>
>>>> The PURWA-IOT-EVK is an evaluation platform for IoT products, composed of
>>>> the Purwa IoT SoM and a carrier board. Together, they form a complete
>>>> embedded system capable of booting to UART.
>>>>
>>>> PURWA-IOT-EVK uses the PS8833 as a retimer for USB0, unlike HAMOA-IOT-EVK.
>>>> Meanwhile, USB0 bypasses the SBU selector FSUSB42.
>>>>
>>>
>>> NAK.
>>>
>>> Warnings were reported at v3. Did you address them? No, you completely
>>> ignored them, so warnings are reported again at v4.
>>>
>>> What do you think these emails are for?
>>
>> This warning is caused by the pcie3_phy node in purwa.dtsi, which is not
>> introduced by this patch set. Since it does not impact functionality, would
>> it be appropriate to fix it in a separate patch?
> 
> Why can't it be fixed as a part of this patchset?

'qcom,4ln-config-sel' is a property related to bifurcated PHY support, 
which Purwa’s PCIe3 does not provide. Therefore, introducing a new 
compatible with a corresponding binding would be more appropriate than 
simply adding this property. Is it acceptable to address this within the 
current patch set?

> 
>>
>>>
>>> Best regards,
>>> Krzysztof
>>
>> -- 
>> Best Regards,
>> Yijie
>>
> 

-- 
Best Regards,
Yijie

Re: [PATCH v4 4/4] arm64: dts: qcom: Add base PURWA-IOT-EVK board

[Dmitry Baryshkov]

On Mon, Jan 19, 2026 at 04:48:20PM +0800, Yijie Yang wrote:
> 
> 
> On 1/19/2026 2:33 PM, Dmitry Baryshkov wrote:
> > On Mon, Jan 19, 2026 at 11:13:29AM +0800, Yijie Yang wrote:
> > > 
> > > 
> > > On 1/17/2026 12:19 AM, Krzysztof Kozlowski wrote:
> > > > On 16/01/2026 11:41, YijieYang wrote:
> > > > > From: Yijie Yang <yijie.yang@oss.qualcomm.com>
> > > > > 
> > > > > The PURWA-IOT-EVK is an evaluation platform for IoT products, composed of
> > > > > the Purwa IoT SoM and a carrier board. Together, they form a complete
> > > > > embedded system capable of booting to UART.
> > > > > 
> > > > > PURWA-IOT-EVK uses the PS8833 as a retimer for USB0, unlike HAMOA-IOT-EVK.
> > > > > Meanwhile, USB0 bypasses the SBU selector FSUSB42.
> > > > > 
> > > > 
> > > > NAK.
> > > > 
> > > > Warnings were reported at v3. Did you address them? No, you completely
> > > > ignored them, so warnings are reported again at v4.
> > > > 
> > > > What do you think these emails are for?
> > > 
> > > This warning is caused by the pcie3_phy node in purwa.dtsi, which is not
> > > introduced by this patch set. Since it does not impact functionality, would
> > > it be appropriate to fix it in a separate patch?
> > 
> > Why can't it be fixed as a part of this patchset?
> 
> 'qcom,4ln-config-sel' is a property related to bifurcated PHY support, which
> Purwa’s PCIe3 does not provide. Therefore, introducing a new compatible with
> a corresponding binding would be more appropriate than simply adding this
> property. Is it acceptable to address this within the current patch set?

Within this or in the separate patchset, but it needs to be fixed before
this patch can go in. Otherwise we are enabling broken PCIe3.

> 
> > 
> > > 
> > > > 
> > > > Best regards,
> > > > Krzysztof
> > > 
> > > -- 
> > > Best Regards,
> > > Yijie
> > > 
> > 
> 
> -- 
> Best Regards,
> Yijie
> 

-- 
With best wishes
Dmitry

Re: [PATCH v4 4/4] arm64: dts: qcom: Add base PURWA-IOT-EVK board

[Yijie Yang]

On 1/19/2026 5:46 PM, Dmitry Baryshkov wrote:
> On Mon, Jan 19, 2026 at 04:48:20PM +0800, Yijie Yang wrote:
>>
>>
>> On 1/19/2026 2:33 PM, Dmitry Baryshkov wrote:
>>> On Mon, Jan 19, 2026 at 11:13:29AM +0800, Yijie Yang wrote:
>>>>
>>>>
>>>> On 1/17/2026 12:19 AM, Krzysztof Kozlowski wrote:
>>>>> On 16/01/2026 11:41, YijieYang wrote:
>>>>>> From: Yijie Yang <yijie.yang@oss.qualcomm.com>
>>>>>>
>>>>>> The PURWA-IOT-EVK is an evaluation platform for IoT products, composed of
>>>>>> the Purwa IoT SoM and a carrier board. Together, they form a complete
>>>>>> embedded system capable of booting to UART.
>>>>>>
>>>>>> PURWA-IOT-EVK uses the PS8833 as a retimer for USB0, unlike HAMOA-IOT-EVK.
>>>>>> Meanwhile, USB0 bypasses the SBU selector FSUSB42.
>>>>>>
>>>>>
>>>>> NAK.
>>>>>
>>>>> Warnings were reported at v3. Did you address them? No, you completely
>>>>> ignored them, so warnings are reported again at v4.
>>>>>
>>>>> What do you think these emails are for?
>>>>
>>>> This warning is caused by the pcie3_phy node in purwa.dtsi, which is not
>>>> introduced by this patch set. Since it does not impact functionality, would
>>>> it be appropriate to fix it in a separate patch?
>>>
>>> Why can't it be fixed as a part of this patchset?
>>
>> 'qcom,4ln-config-sel' is a property related to bifurcated PHY support, which
>> Purwa’s PCIe3 does not provide. Therefore, introducing a new compatible with
>> a corresponding binding would be more appropriate than simply adding this
>> property. Is it acceptable to address this within the current patch set?
> 
> Within this or in the separate patchset, but it needs to be fixed before
> this patch can go in. Otherwise we are enabling broken PCIe3.

OK, will fix.


> 
>>
>>>
>>>>
>>>>>
>>>>> Best regards,
>>>>> Krzysztof
>>>>
>>>> -- 
>>>> Best Regards,
>>>> Yijie
>>>>
>>>
>>
>> -- 
>> Best Regards,
>> Yijie
>>
> 

-- 
Best Regards,
Yijie

Re: [PATCH v4 4/4] arm64: dts: qcom: Add base PURWA-IOT-EVK board

[Konrad Dybcio]

On 1/19/26 10:46 AM, Dmitry Baryshkov wrote:
> On Mon, Jan 19, 2026 at 04:48:20PM +0800, Yijie Yang wrote:
>>
>>
>> On 1/19/2026 2:33 PM, Dmitry Baryshkov wrote:
>>> On Mon, Jan 19, 2026 at 11:13:29AM +0800, Yijie Yang wrote:
>>>>
>>>>
>>>> On 1/17/2026 12:19 AM, Krzysztof Kozlowski wrote:
>>>>> On 16/01/2026 11:41, YijieYang wrote:
>>>>>> From: Yijie Yang <yijie.yang@oss.qualcomm.com>
>>>>>>
>>>>>> The PURWA-IOT-EVK is an evaluation platform for IoT products, composed of
>>>>>> the Purwa IoT SoM and a carrier board. Together, they form a complete
>>>>>> embedded system capable of booting to UART.
>>>>>>
>>>>>> PURWA-IOT-EVK uses the PS8833 as a retimer for USB0, unlike HAMOA-IOT-EVK.
>>>>>> Meanwhile, USB0 bypasses the SBU selector FSUSB42.
>>>>>>
>>>>>
>>>>> NAK.
>>>>>
>>>>> Warnings were reported at v3. Did you address them? No, you completely
>>>>> ignored them, so warnings are reported again at v4.
>>>>>
>>>>> What do you think these emails are for?
>>>>
>>>> This warning is caused by the pcie3_phy node in purwa.dtsi, which is not
>>>> introduced by this patch set. Since it does not impact functionality, would
>>>> it be appropriate to fix it in a separate patch?
>>>
>>> Why can't it be fixed as a part of this patchset?
>>
>> 'qcom,4ln-config-sel' is a property related to bifurcated PHY support, which
>> Purwa’s PCIe3 does not provide. Therefore, introducing a new compatible with
>> a corresponding binding would be more appropriate than simply adding this
>> property. Is it acceptable to address this within the current patch set?
> 
> Within this or in the separate patchset, but it needs to be fixed before
> this patch can go in. Otherwise we are enabling broken PCIe3.

https://lore.kernel.org/linux-arm-msm/20260119-topic-purwa_phy_shutup_warning-v1-1-997a692b31c6@oss.qualcomm.com/T/#u

Konrad

Re: [PATCH v4 4/4] arm64: dts: qcom: Add base PURWA-IOT-EVK board

[Yijie Yang]

On 1/19/2026 9:31 PM, Konrad Dybcio wrote:
> On 1/19/26 10:46 AM, Dmitry Baryshkov wrote:
>> On Mon, Jan 19, 2026 at 04:48:20PM +0800, Yijie Yang wrote:
>>>
>>>
>>> On 1/19/2026 2:33 PM, Dmitry Baryshkov wrote:
>>>> On Mon, Jan 19, 2026 at 11:13:29AM +0800, Yijie Yang wrote:
>>>>>
>>>>>
>>>>> On 1/17/2026 12:19 AM, Krzysztof Kozlowski wrote:
>>>>>> On 16/01/2026 11:41, YijieYang wrote:
>>>>>>> From: Yijie Yang <yijie.yang@oss.qualcomm.com>
>>>>>>>
>>>>>>> The PURWA-IOT-EVK is an evaluation platform for IoT products, composed of
>>>>>>> the Purwa IoT SoM and a carrier board. Together, they form a complete
>>>>>>> embedded system capable of booting to UART.
>>>>>>>
>>>>>>> PURWA-IOT-EVK uses the PS8833 as a retimer for USB0, unlike HAMOA-IOT-EVK.
>>>>>>> Meanwhile, USB0 bypasses the SBU selector FSUSB42.
>>>>>>>
>>>>>>
>>>>>> NAK.
>>>>>>
>>>>>> Warnings were reported at v3. Did you address them? No, you completely
>>>>>> ignored them, so warnings are reported again at v4.
>>>>>>
>>>>>> What do you think these emails are for?
>>>>>
>>>>> This warning is caused by the pcie3_phy node in purwa.dtsi, which is not
>>>>> introduced by this patch set. Since it does not impact functionality, would
>>>>> it be appropriate to fix it in a separate patch?
>>>>
>>>> Why can't it be fixed as a part of this patchset?
>>>
>>> 'qcom,4ln-config-sel' is a property related to bifurcated PHY support, which
>>> Purwa’s PCIe3 does not provide. Therefore, introducing a new compatible with
>>> a corresponding binding would be more appropriate than simply adding this
>>> property. Is it acceptable to address this within the current patch set?
>>
>> Within this or in the separate patchset, but it needs to be fixed before
>> this patch can go in. Otherwise we are enabling broken PCIe3.
> 
> https://lore.kernel.org/linux-arm-msm/20260119-topic-purwa_phy_shutup_warning-v1-1-997a692b31c6@oss.qualcomm.com/T/#u

Thanks, I can add this as a dependency.

> 
> Konrad

-- 
Best Regards,
Yijie

Re: [PATCH v4 4/4] arm64: dts: qcom: Add base PURWA-IOT-EVK board

[Krzysztof Kozlowski]

On 19/01/2026 04:13, Yijie Yang wrote:
> 
> 
> On 1/17/2026 12:19 AM, Krzysztof Kozlowski wrote:
>> On 16/01/2026 11:41, YijieYang wrote:
>>> From: Yijie Yang <yijie.yang@oss.qualcomm.com>
>>>
>>> The PURWA-IOT-EVK is an evaluation platform for IoT products, composed of
>>> the Purwa IoT SoM and a carrier board. Together, they form a complete
>>> embedded system capable of booting to UART.
>>>
>>> PURWA-IOT-EVK uses the PS8833 as a retimer for USB0, unlike HAMOA-IOT-EVK.
>>> Meanwhile, USB0 bypasses the SBU selector FSUSB42.
>>>
>>
>> NAK.
>>
>> Warnings were reported at v3. Did you address them? No, you completely
>> ignored them, so warnings are reported again at v4.
>>
>> What do you think these emails are for?
> 
> This warning is caused by the pcie3_phy node in purwa.dtsi, which is not 
> introduced by this patch set. Since it does not impact functionality, 

Your patchset introduces that warning. There was no such warning before.

My NAK still stays, such patchset must not be merged.

Best regards,
Krzysztof

Re: [PATCH v4 4/4] arm64: dts: qcom: Add base PURWA-IOT-EVK board

[Yijie Yang]

On 1/19/2026 3:05 PM, Krzysztof Kozlowski wrote:
> On 19/01/2026 04:13, Yijie Yang wrote:
>>
>>
>> On 1/17/2026 12:19 AM, Krzysztof Kozlowski wrote:
>>> On 16/01/2026 11:41, YijieYang wrote:
>>>> From: Yijie Yang <yijie.yang@oss.qualcomm.com>
>>>>
>>>> The PURWA-IOT-EVK is an evaluation platform for IoT products, composed of
>>>> the Purwa IoT SoM and a carrier board. Together, they form a complete
>>>> embedded system capable of booting to UART.
>>>>
>>>> PURWA-IOT-EVK uses the PS8833 as a retimer for USB0, unlike HAMOA-IOT-EVK.
>>>> Meanwhile, USB0 bypasses the SBU selector FSUSB42.
>>>>
>>>
>>> NAK.
>>>
>>> Warnings were reported at v3. Did you address them? No, you completely
>>> ignored them, so warnings are reported again at v4.
>>>
>>> What do you think these emails are for?
>>
>> This warning is caused by the pcie3_phy node in purwa.dtsi, which is not
>> introduced by this patch set. Since it does not impact functionality,
> 
> Your patchset introduces that warning. There was no such warning before.
> 
> My NAK still stays, such patchset must not be merged.

This patch series can continue to be reviewed with the dependency noted, 
right?
https://lore.kernel.org/linux-arm-msm/20260119-topic-purwa_phy_shutup_warning-v1-1-997a692b31c6@oss.qualcomm.com/T/#u

> 
> Best regards,
> Krzysztof

-- 
Best Regards,
Yijie

Re: [PATCH v4 4/4] arm64: dts: qcom: Add base PURWA-IOT-EVK board

[Krzysztof Kozlowski]

On 20/01/2026 07:49, Yijie Yang wrote:
> 
> 
> On 1/19/2026 3:05 PM, Krzysztof Kozlowski wrote:
>> On 19/01/2026 04:13, Yijie Yang wrote:
>>>
>>>
>>> On 1/17/2026 12:19 AM, Krzysztof Kozlowski wrote:
>>>> On 16/01/2026 11:41, YijieYang wrote:
>>>>> From: Yijie Yang <yijie.yang@oss.qualcomm.com>
>>>>>
>>>>> The PURWA-IOT-EVK is an evaluation platform for IoT products, composed of
>>>>> the Purwa IoT SoM and a carrier board. Together, they form a complete
>>>>> embedded system capable of booting to UART.
>>>>>
>>>>> PURWA-IOT-EVK uses the PS8833 as a retimer for USB0, unlike HAMOA-IOT-EVK.
>>>>> Meanwhile, USB0 bypasses the SBU selector FSUSB42.
>>>>>
>>>>
>>>> NAK.
>>>>
>>>> Warnings were reported at v3. Did you address them? No, you completely
>>>> ignored them, so warnings are reported again at v4.
>>>>
>>>> What do you think these emails are for?
>>>
>>> This warning is caused by the pcie3_phy node in purwa.dtsi, which is not
>>> introduced by this patch set. Since it does not impact functionality,
>>
>> Your patchset introduces that warning. There was no such warning before.
>>
>> My NAK still stays, such patchset must not be merged.
> 
> This patch series can continue to be reviewed with the dependency noted, 
> right?
> https://lore.kernel.org/linux-arm-msm/20260119-topic-purwa_phy_shutup_warning-v1-1-997a692b31c6@oss.qualcomm.com/T/#u

It's not a dependency. You only need to mention where the bindings are
addressing the issue, preferably in patch changelog.

Best regards,
Krzysztof

Re: [PATCH v4 4/4] arm64: dts: qcom: Add base PURWA-IOT-EVK board

[Yijie Yang]

On 1/20/2026 3:17 PM, Krzysztof Kozlowski wrote:
> On 20/01/2026 07:49, Yijie Yang wrote:
>>
>>
>> On 1/19/2026 3:05 PM, Krzysztof Kozlowski wrote:
>>> On 19/01/2026 04:13, Yijie Yang wrote:
>>>>
>>>>
>>>> On 1/17/2026 12:19 AM, Krzysztof Kozlowski wrote:
>>>>> On 16/01/2026 11:41, YijieYang wrote:
>>>>>> From: Yijie Yang <yijie.yang@oss.qualcomm.com>
>>>>>>
>>>>>> The PURWA-IOT-EVK is an evaluation platform for IoT products, composed of
>>>>>> the Purwa IoT SoM and a carrier board. Together, they form a complete
>>>>>> embedded system capable of booting to UART.
>>>>>>
>>>>>> PURWA-IOT-EVK uses the PS8833 as a retimer for USB0, unlike HAMOA-IOT-EVK.
>>>>>> Meanwhile, USB0 bypasses the SBU selector FSUSB42.
>>>>>>
>>>>>
>>>>> NAK.
>>>>>
>>>>> Warnings were reported at v3. Did you address them? No, you completely
>>>>> ignored them, so warnings are reported again at v4.
>>>>>
>>>>> What do you think these emails are for?
>>>>
>>>> This warning is caused by the pcie3_phy node in purwa.dtsi, which is not
>>>> introduced by this patch set. Since it does not impact functionality,
>>>
>>> Your patchset introduces that warning. There was no such warning before.
>>>
>>> My NAK still stays, such patchset must not be merged.
>>
>> This patch series can continue to be reviewed with the dependency noted,
>> right?
>> https://lore.kernel.org/linux-arm-msm/20260119-topic-purwa_phy_shutup_warning-v1-1-997a692b31c6@oss.qualcomm.com/T/#u
> 
> It's not a dependency. You only need to mention where the bindings are
> addressing the issue, preferably in patch changelog.

Sure, will update.

> 
> Best regards,
> Krzysztof

-- 
Best Regards,
Yijie

Re: [PATCH v4 4/4] arm64: dts: qcom: Add base PURWA-IOT-EVK board

[Konrad Dybcio]

On 1/16/26 11:41 AM, YijieYang wrote:
> From: Yijie Yang <yijie.yang@oss.qualcomm.com>
> 
> The PURWA-IOT-EVK is an evaluation platform for IoT products, composed of
> the Purwa IoT SoM and a carrier board. Together, they form a complete
> embedded system capable of booting to UART.
> 
> PURWA-IOT-EVK uses the PS8833 as a retimer for USB0, unlike HAMOA-IOT-EVK.
> Meanwhile, USB0 bypasses the SBU selector FSUSB42.
> 
> Make the following peripherals on the carrier board enabled:
> - UART
> - On-board regulators
> - USB Type-C mux
> - Pinctrl
> - Embedded USB (EUSB) repeaters
> - NVMe
> - pmic-glink
> - USB DisplayPorts
> - Bluetooth
> - WLAN
> - Audio
> - PCIe ports for PCIe3 through PCIe6a
> - TPM
> 
> Signed-off-by: Yijie Yang <yijie.yang@oss.qualcomm.com>
> ---

[...]


> +&spi11 {
> +	status = "okay";
> +
> +	tpm@0 {
> +		compatible = "st,st33htpm-spi", "tcg,tpm_tis-spi";
> +		reg = <0>;
> +		spi-max-frequency = <20000000>;
> +	};
> +};
> +
>  &smb2360_0 {
>  	status = "okay";
>  };
> @@ -1171,16 +1217,6 @@ &smb2360_2_eusb2_repeater {
>  	vdd3-supply = <&vreg_l8b_3p0>;
>  };
>  
> -&spi11 {
> -	status = "okay";
> -
> -	tpm@0 {
> -		compatible = "st,st33htpm-spi", "tcg,tpm_tis-spi";
> -		reg = <0>;
> -		spi-max-frequency = <20000000>;
> -	};
> -};

Not sure if anyone commented on this already, please keep it where
it was (it was properly sorted in the original file), then we're just
left with the USB changes

Konrad

Re: [PATCH v4 4/4] arm64: dts: qcom: Add base PURWA-IOT-EVK board

[Yijie Yang]

On 1/19/2026 9:53 PM, Konrad Dybcio wrote:
> On 1/16/26 11:41 AM, YijieYang wrote:
>> From: Yijie Yang <yijie.yang@oss.qualcomm.com>
>>
>> The PURWA-IOT-EVK is an evaluation platform for IoT products, composed of
>> the Purwa IoT SoM and a carrier board. Together, they form a complete
>> embedded system capable of booting to UART.
>>
>> PURWA-IOT-EVK uses the PS8833 as a retimer for USB0, unlike HAMOA-IOT-EVK.
>> Meanwhile, USB0 bypasses the SBU selector FSUSB42.
>>
>> Make the following peripherals on the carrier board enabled:
>> - UART
>> - On-board regulators
>> - USB Type-C mux
>> - Pinctrl
>> - Embedded USB (EUSB) repeaters
>> - NVMe
>> - pmic-glink
>> - USB DisplayPorts
>> - Bluetooth
>> - WLAN
>> - Audio
>> - PCIe ports for PCIe3 through PCIe6a
>> - TPM
>>
>> Signed-off-by: Yijie Yang <yijie.yang@oss.qualcomm.com>
>> ---
> 
> [...]
> 
> 
>> +&spi11 {
>> +	status = "okay";
>> +
>> +	tpm@0 {
>> +		compatible = "st,st33htpm-spi", "tcg,tpm_tis-spi";
>> +		reg = <0>;
>> +		spi-max-frequency = <20000000>;
>> +	};
>> +};
>> +
>>   &smb2360_0 {
>>   	status = "okay";
>>   };
>> @@ -1171,16 +1217,6 @@ &smb2360_2_eusb2_repeater {
>>   	vdd3-supply = <&vreg_l8b_3p0>;
>>   };
>>   
>> -&spi11 {
>> -	status = "okay";
>> -
>> -	tpm@0 {
>> -		compatible = "st,st33htpm-spi", "tcg,tpm_tis-spi";
>> -		reg = <0>;
>> -		spi-max-frequency = <20000000>;
>> -	};
>> -};
> 
> Not sure if anyone commented on this already, please keep it where
> it was (it was properly sorted in the original file), then we're just
> left with the USB changes
> 

Will update.


> Konrad

-- 
Best Regards,
Yijie

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

[Dmitry Baryshkov]

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

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

[Yijie Yang]

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

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

[Dmitry Baryshkov]

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

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

[Yijie Yang]

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

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

[Konrad Dybcio]

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

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

[Krzysztof Kozlowski]

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

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

[Konrad Dybcio]

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

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

[Yijie Yang]

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

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

[Rob Herring]

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