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

[PATCH v2 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
- PCIe6a and its PHY
- PCIe4 and its PHY
- Reserved memory regions
- Pinctrl
- NVMe
- ADSP, CDSP
- WLAN, Bluetooth (M.2 interface)
- USB DisplayPort
- Graphics
- Audio

Signed-off-by: Yijie Yang <yijie.yang@oss.qualcomm.com>
---
Changes since V1:
- 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.

---
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      | 1313 +++++++++++++++++++++++
 arch/arm64/boot/dts/qcom/purwa-iot-som.dtsi     |  614 +++++++++++
 drivers/firmware/qcom/qcom_scm.c                |    1 +
 5 files changed, 1935 insertions(+)
---
base-commit: beff4beeeb2760405ad49de2a6a1bdab8fb1aec3
change-id: 20251113-purwa-907ec75b4959

Best regards,
--  
Yijie Yang <yijie.yang@oss.qualcomm.com>

[PATCH v2 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 v2 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.

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

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

[Dmitry Baryshkov]

On Fri, Jan 09, 2026 at 03:59:52PM +0800, YijieYang wrote:
> 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.
> 
> Signed-off-by: Yijie Yang <yijie.yang@oss.qualcomm.com>
> ---
>  drivers/firmware/qcom/qcom_scm.c | 1 +
>  1 file changed, 1 insertion(+)
> 

Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>


-- 
With best wishes
Dmitry

[PATCH v2 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.

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

Signed-off-by: Yijie Yang <yijie.yang@oss.qualcomm.com>
---
 .../dts/qcom/{hamoa-iot-som.dtsi => purwa-iot-som.dtsi}   | 8 ++------
 1 file changed, 2 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 4a69852e9176..16f11a81163e 100644
--- a/arch/arm64/boot/dts/qcom/hamoa-iot-som.dtsi
+++ b/arch/arm64/boot/dts/qcom/purwa-iot-som.dtsi
@@ -3,7 +3,7 @@
  * 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>
@@ -378,16 +378,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";
 };
 
 &pcie4 {
-- 
2.34.1

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

[Dmitry Baryshkov]

On Fri, Jan 09, 2026 at 03:59:53PM +0800, 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.
> 
> Make the following peripherals on the SOM enabled:
> - Regulators on the SOM
> - Reserved memory regions
> - PCIe6a and its PHY
> - PCIe4 and its PHY
> - USB0 through USB6 and their PHYs
> - ADSP, CDSP
> - Graphic
> 
> Signed-off-by: Yijie Yang <yijie.yang@oss.qualcomm.com>
> ---
>  .../dts/qcom/{hamoa-iot-som.dtsi => purwa-iot-som.dtsi}   | 8 ++------
>  1 file changed, 2 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 4a69852e9176..16f11a81163e 100644
> --- a/arch/arm64/boot/dts/qcom/hamoa-iot-som.dtsi
> +++ b/arch/arm64/boot/dts/qcom/purwa-iot-som.dtsi

I remember, we were told that there are PMIC differences too. Where are
they handled?

> @@ -3,7 +3,7 @@
>   * 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>

-- 
With best wishes
Dmitry

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

[Yijie Yang]

On 1/9/2026 8:10 PM, Dmitry Baryshkov wrote:
> On Fri, Jan 09, 2026 at 03:59:53PM +0800, 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.
>>
>> Make the following peripherals on the SOM enabled:
>> - Regulators on the SOM
>> - Reserved memory regions
>> - PCIe6a and its PHY
>> - PCIe4 and its PHY
>> - USB0 through USB6 and their PHYs
>> - ADSP, CDSP
>> - Graphic
>>
>> Signed-off-by: Yijie Yang <yijie.yang@oss.qualcomm.com>
>> ---
>>   .../dts/qcom/{hamoa-iot-som.dtsi => purwa-iot-som.dtsi}   | 8 ++------
>>   1 file changed, 2 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 4a69852e9176..16f11a81163e 100644
>> --- a/arch/arm64/boot/dts/qcom/hamoa-iot-som.dtsi
>> +++ b/arch/arm64/boot/dts/qcom/purwa-iot-som.dtsi
> 
> I remember, we were told that there are PMIC differences too. Where are
> they handled?

I forgot to remove the unused PMIC node from the SOM file for Purwa.

> 
>> @@ -3,7 +3,7 @@
>>    * 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>
> 

-- 
Best Regards,
Yijie

[PATCH v2 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. As a result, the glink
topology differs from that of HAMOA-IOT-EVK.

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

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}  | 223 +++++-------------
 2 files changed, 66 insertions(+), 158 deletions(-)
 copy arch/arm64/boot/dts/qcom/{hamoa-iot-evk.dts => purwa-iot-evk.dts} (87%)

diff --git a/arch/arm64/boot/dts/qcom/Makefile b/arch/arm64/boot/dts/qcom/Makefile
index 0ccd6ec16dfb..2ed1500cbaa9 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 87%
copy from arch/arm64/boot/dts/qcom/hamoa-iot-evk.dts
copy to arch/arm64/boot/dts/qcom/purwa-iot-evk.dts
index 898b92627f84..781634b45eb0 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 {
@@ -19,16 +19,6 @@ aliases {
 		serial1 = &uart14;
 	};
 
-	backlight: backlight {
-		compatible = "pwm-backlight";
-		pwms = <&pmk8550_pwm 0 5000000>;
-		enable-gpios = <&pmc8380_3_gpios 4 GPIO_ACTIVE_HIGH>;
-		power-supply = <&vreg_edp_bl>;
-
-		pinctrl-0 = <&edp_bl_en>, <&edp_bl_pwm>;
-		pinctrl-names = "default";
-	};
-
 	wcd938x: audio-codec {
 		compatible = "qcom,wcd9385-codec";
 
@@ -60,32 +50,6 @@ chosen {
 		stdout-path = "serial0:115200n8";
 	};
 
-	connector3 {
-		compatible = "usb-a-connector";
-		label = "USB-3-Type-A";
-		power-role = "source";
-
-		vbus-supply = <&regulator_usb3_vbus>;
-
-		port {
-			connector_3_in: endpoint {
-			};
-		};
-	};
-
-	connector6 {
-		compatible = "usb-a-connector";
-		label = "USB-6-Type-A";
-		power-role = "source";
-
-		vbus-supply = <&regulator_usb6_vbus>;
-
-		port {
-			connector_4_in: endpoint {
-			};
-		};
-	};
-
 	pmic-glink {
 		compatible = "qcom,x1e80100-pmic-glink",
 			     "qcom,sm8550-pmic-glink",
@@ -118,15 +82,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>;
 					};
 				};
 			};
@@ -221,22 +185,6 @@ vreg_edp_3p3: regulator-edp-3p3 {
 		regulator-boot-on;
 	};
 
-	vreg_edp_bl: regulator-edp-bl {
-		compatible = "regulator-fixed";
-
-		regulator-name = "VBL9";
-		regulator-min-microvolt = <3600000>;
-		regulator-max-microvolt = <3600000>;
-
-		gpio = <&pmc8380_3_gpios 10 GPIO_ACTIVE_HIGH>;
-		enable-active-high;
-
-		pinctrl-0 = <&edp_bl_reg_en>;
-		pinctrl-names = "default";
-
-		regulator-boot-on;
-	};
-
 	vreg_nvme: regulator-nvme {
 		compatible = "regulator-fixed";
 
@@ -398,26 +346,6 @@ vreg_rtmr2_3p3: regulator-rtmr2-3p3 {
 		regulator-boot-on;
 	};
 
-	regulator_usb3_vbus: regulator-usb3-vbus {
-		compatible = "regulator-fixed";
-		regulator-name = "USB3_VBUS";
-		gpio = <&pm8550ve_9_gpios 4 GPIO_ACTIVE_HIGH>;
-		pinctrl-0 = <&usb3_en>;
-		pinctrl-names = "default";
-		enable-active-high;
-		regulator-always-on;
-	};
-
-	regulator_usb6_vbus: regulator-usb6-vbus {
-		compatible = "regulator-fixed";
-		regulator-name = "USB6_VBUS";
-		gpio = <&pm8550ve_9_gpios 5 GPIO_ACTIVE_HIGH>;
-		pinctrl-0 = <&usb6_en>;
-		pinctrl-names = "default";
-		enable-active-high;
-		regulator-always-on;
-	};
-
 	vph_pwr: regulator-vph-pwr {
 		compatible = "regulator-fixed";
 
@@ -576,25 +504,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";
 
@@ -711,6 +620,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>;
 
@@ -894,7 +860,7 @@ aux-bus {
 		panel {
 			compatible = "edp-panel";
 
-			backlight = <&backlight>;
+			//backlight = <&backlight>;
 			power-supply = <&vreg_edp_3p3>;
 
 			port {
@@ -920,23 +886,6 @@ &mdss_dp3_phy {
 	status = "okay";
 };
 
-&pcie4_port0 {
-	wifi@0 {
-		compatible = "pci17cb,1107";
-		reg = <0x10000 0x0 0x0 0x0 0x0>;
-
-		vddaon-supply = <&vreg_pmu_aon_0p59>;
-		vddwlcx-supply = <&vreg_pmu_wlcx_0p8>;
-		vddwlmx-supply = <&vreg_pmu_wlmx_0p85>;
-		vddrfacmn-supply = <&vreg_pmu_rfa_cmn>;
-		vddrfa0p8-supply = <&vreg_pmu_rfa_0p8>;
-		vddrfa1p2-supply = <&vreg_pmu_rfa_1p2>;
-		vddrfa1p8-supply = <&vreg_pmu_rfa_1p8>;
-		vddpcie0p9-supply = <&vreg_pmu_pcie_0p9>;
-		vddpcie1p8-supply = <&vreg_pmu_pcie_1p8>;
-	};
-};
-
 &pcie6a {
 	vddpe-3v3-supply = <&vreg_nvme>;
 };
@@ -970,22 +919,6 @@ usb0_1p8_reg_en: usb0-1p8-reg-en-state {
 		input-disable;
 		output-enable;
 	};
-
-	usb3_en: usb3-en-state {
-		pins = "gpio4";
-		function = "normal";
-		qcom,drive-strength = <PMIC_GPIO_STRENGTH_HIGH>;
-		output-enable;
-		power-source = <0>;
-	};
-
-	usb6_en: usb6-en-state {
-		pins = "gpio5";
-		function = "normal";
-		qcom,drive-strength = <PMIC_GPIO_STRENGTH_HIGH>;
-		output-enable;
-		power-source = <0>;
-	};
 };
 
 &pm8550_pwm {
@@ -1010,21 +943,6 @@ led@2 {
 	};
 };
 
-&pmc8380_3_gpios {
-	edp_bl_en: edp-bl-en-state {
-		pins = "gpio4";
-		function = "normal";
-		power-source = <1>;
-		input-disable;
-		output-enable;
-	};
-
-	edp_bl_reg_en: edp-bl-reg-en-state {
-		pins = "gpio10";
-		function = "normal";
-	};
-};
-
 &pmc8380_5_gpios {
 	usb0_pwr_1p15_reg_en: usb0-pwr-1p15-reg-en-state {
 		pins = "gpio8";
@@ -1036,17 +954,6 @@ usb0_pwr_1p15_reg_en: usb0-pwr-1p15-reg-en-state {
 	};
 };
 
-&pmk8550_gpios {
-	edp_bl_pwm: edp-bl-pwm-state {
-		pins = "gpio5";
-		function = "func3";
-	};
-};
-
-&pmk8550_pwm {
-	status = "okay";
-};
-
 &smb2360_0 {
 	status = "okay";
 };
@@ -1363,7 +1270,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 v2 4/4] arm64: dts: qcom: Add base PURWA-IOT-EVK board

[Konrad Dybcio]

On 1/9/26 8:59 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.

[...]

> -	backlight: backlight {
> -		compatible = "pwm-backlight";
> -		pwms = <&pmk8550_pwm 0 5000000>;
> -		enable-gpios = <&pmc8380_3_gpios 4 GPIO_ACTIVE_HIGH>;
> -		power-supply = <&vreg_edp_bl>;
> -
> -		pinctrl-0 = <&edp_bl_en>, <&edp_bl_pwm>;
> -		pinctrl-names = "default";
> -	};

Is the backlight infra different on the Purwa IoT EVK?

> -
>  	wcd938x: audio-codec {
>  		compatible = "qcom,wcd9385-codec";
>  
> @@ -60,32 +50,6 @@ chosen {
>  		stdout-path = "serial0:115200n8";
>  	};
>  
> -	connector3 {
> -		compatible = "usb-a-connector";
> -		label = "USB-3-Type-A";
> -		power-role = "source";
> -
> -		vbus-supply = <&regulator_usb3_vbus>;
> -
> -		port {
> -			connector_3_in: endpoint {
> -			};
> -		};
> -	};
> -
> -	connector6 {
> -		compatible = "usb-a-connector";
> -		label = "USB-6-Type-A";
> -		power-role = "source";
> -
> -		vbus-supply = <&regulator_usb6_vbus>;
> -
> -		port {
> -			connector_4_in: endpoint {
> -			};
> -		};
> -	};

Are there no Type-A ports?

[...]

>  		panel {
>  			compatible = "edp-panel";
>  
> -			backlight = <&backlight>;
> +			//backlight = <&backlight>;

FWIW we can't merge dead code

>  			power-supply = <&vreg_edp_3p3>;
>  
>  			port {
> @@ -920,23 +886,6 @@ &mdss_dp3_phy {
>  	status = "okay";
>  };
>  
> -&pcie4_port0 {
> -	wifi@0 {
> -		compatible = "pci17cb,1107";
> -		reg = <0x10000 0x0 0x0 0x0 0x0>;
> -
> -		vddaon-supply = <&vreg_pmu_aon_0p59>;
> -		vddwlcx-supply = <&vreg_pmu_wlcx_0p8>;
> -		vddwlmx-supply = <&vreg_pmu_wlmx_0p85>;
> -		vddrfacmn-supply = <&vreg_pmu_rfa_cmn>;
> -		vddrfa0p8-supply = <&vreg_pmu_rfa_0p8>;
> -		vddrfa1p2-supply = <&vreg_pmu_rfa_1p2>;
> -		vddrfa1p8-supply = <&vreg_pmu_rfa_1p8>;
> -		vddpcie0p9-supply = <&vreg_pmu_pcie_0p9>;
> -		vddpcie1p8-supply = <&vreg_pmu_pcie_1p8>;
> -	};
> -};

Is the Wi-Fi solution different?

Konrad

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

[Yijie Yang]

On 1/9/2026 7:29 PM, Konrad Dybcio wrote:
> On 1/9/26 8:59 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.
> 
> [...]
> 
>> -	backlight: backlight {
>> -		compatible = "pwm-backlight";
>> -		pwms = <&pmk8550_pwm 0 5000000>;
>> -		enable-gpios = <&pmc8380_3_gpios 4 GPIO_ACTIVE_HIGH>;
>> -		power-supply = <&vreg_edp_bl>;
>> -
>> -		pinctrl-0 = <&edp_bl_en>, <&edp_bl_pwm>;
>> -		pinctrl-names = "default";
>> -	};
> 
> Is the backlight infra different on the Purwa IoT EVK?

As you can see, this Purwa file was copied from the latest 
hamoa-iot-evk.dts. However, not all nodes have been verified on Purwa. 
Therefore, I need to retain only the functions that work correctly and 
keep them aligned with the nodes from my initial version. The deleted 
nodes will be updated later by the respective authors from different 
technical areas.

> 
>> -
>>   	wcd938x: audio-codec {
>>   		compatible = "qcom,wcd9385-codec";
>>   
>> @@ -60,32 +50,6 @@ chosen {
>>   		stdout-path = "serial0:115200n8";
>>   	};
>>   
>> -	connector3 {
>> -		compatible = "usb-a-connector";
>> -		label = "USB-3-Type-A";
>> -		power-role = "source";
>> -
>> -		vbus-supply = <&regulator_usb3_vbus>;
>> -
>> -		port {
>> -			connector_3_in: endpoint {
>> -			};
>> -		};
>> -	};
>> -
>> -	connector6 {
>> -		compatible = "usb-a-connector";
>> -		label = "USB-6-Type-A";
>> -		power-role = "source";
>> -
>> -		vbus-supply = <&regulator_usb6_vbus>;
>> -
>> -		port {
>> -			connector_4_in: endpoint {
>> -			};
>> -		};
>> -	};
> 
> Are there no Type-A ports?

ditto

> 
> [...]
> 
>>   		panel {
>>   			compatible = "edp-panel";
>>   
>> -			backlight = <&backlight>;
>> +			//backlight = <&backlight>;
> 
> FWIW we can't merge dead code

I will update.

> 
>>   			power-supply = <&vreg_edp_3p3>;
>>   
>>   			port {
>> @@ -920,23 +886,6 @@ &mdss_dp3_phy {
>>   	status = "okay";
>>   };
>>   
>> -&pcie4_port0 {
>> -	wifi@0 {
>> -		compatible = "pci17cb,1107";
>> -		reg = <0x10000 0x0 0x0 0x0 0x0>;
>> -
>> -		vddaon-supply = <&vreg_pmu_aon_0p59>;
>> -		vddwlcx-supply = <&vreg_pmu_wlcx_0p8>;
>> -		vddwlmx-supply = <&vreg_pmu_wlmx_0p85>;
>> -		vddrfacmn-supply = <&vreg_pmu_rfa_cmn>;
>> -		vddrfa0p8-supply = <&vreg_pmu_rfa_0p8>;
>> -		vddrfa1p2-supply = <&vreg_pmu_rfa_1p2>;
>> -		vddrfa1p8-supply = <&vreg_pmu_rfa_1p8>;
>> -		vddpcie0p9-supply = <&vreg_pmu_pcie_0p9>;
>> -		vddpcie1p8-supply = <&vreg_pmu_pcie_1p8>;
>> -	};
>> -};
> 
> Is the Wi-Fi solution different?

ditto

> 
> Konrad

-- 
Best Regards,
Yijie

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

[Dmitry Baryshkov]

On Mon, Jan 12, 2026 at 11:12:09AM +0800, Yijie Yang wrote:
> 
> 
> On 1/9/2026 7:29 PM, Konrad Dybcio wrote:
> > On 1/9/26 8:59 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.
> > 
> > [...]
> > 
> > > -	backlight: backlight {
> > > -		compatible = "pwm-backlight";
> > > -		pwms = <&pmk8550_pwm 0 5000000>;
> > > -		enable-gpios = <&pmc8380_3_gpios 4 GPIO_ACTIVE_HIGH>;
> > > -		power-supply = <&vreg_edp_bl>;
> > > -
> > > -		pinctrl-0 = <&edp_bl_en>, <&edp_bl_pwm>;
> > > -		pinctrl-names = "default";
> > > -	};
> > 
> > Is the backlight infra different on the Purwa IoT EVK?
> 
> As you can see, this Purwa file was copied from the latest
> hamoa-iot-evk.dts. However, not all nodes have been verified on Purwa.
> Therefore, I need to retain only the functions that work correctly and keep
> them aligned with the nodes from my initial version. The deleted nodes will
> be updated later by the respective authors from different technical areas.

Please, only delete nodes which are not present on the Purwa IoT EVK.

> 
> > 
> > > -
> > >   	wcd938x: audio-codec {
> > >   		compatible = "qcom,wcd9385-codec";
> > > @@ -60,32 +50,6 @@ chosen {
> > >   		stdout-path = "serial0:115200n8";
> > >   	};
> > > -	connector3 {
> > > -		compatible = "usb-a-connector";
> > > -		label = "USB-3-Type-A";
> > > -		power-role = "source";
> > > -
> > > -		vbus-supply = <&regulator_usb3_vbus>;
> > > -
> > > -		port {
> > > -			connector_3_in: endpoint {
> > > -			};
> > > -		};
> > > -	};
> > > -
> > > -	connector6 {
> > > -		compatible = "usb-a-connector";
> > > -		label = "USB-6-Type-A";
> > > -		power-role = "source";
> > > -
> > > -		vbus-supply = <&regulator_usb6_vbus>;
> > > -
> > > -		port {
> > > -			connector_4_in: endpoint {
> > > -			};
> > > -		};
> > > -	};
> > 
> > Are there no Type-A ports?
> 
> ditto

?

> 
> > > @@ -920,23 +886,6 @@ &mdss_dp3_phy {
> > >   	status = "okay";
> > >   };
> > > -&pcie4_port0 {
> > > -	wifi@0 {
> > > -		compatible = "pci17cb,1107";
> > > -		reg = <0x10000 0x0 0x0 0x0 0x0>;
> > > -
> > > -		vddaon-supply = <&vreg_pmu_aon_0p59>;
> > > -		vddwlcx-supply = <&vreg_pmu_wlcx_0p8>;
> > > -		vddwlmx-supply = <&vreg_pmu_wlmx_0p85>;
> > > -		vddrfacmn-supply = <&vreg_pmu_rfa_cmn>;
> > > -		vddrfa0p8-supply = <&vreg_pmu_rfa_0p8>;
> > > -		vddrfa1p2-supply = <&vreg_pmu_rfa_1p2>;
> > > -		vddrfa1p8-supply = <&vreg_pmu_rfa_1p8>;
> > > -		vddpcie0p9-supply = <&vreg_pmu_pcie_0p9>;
> > > -		vddpcie1p8-supply = <&vreg_pmu_pcie_1p8>;
> > > -	};
> > > -};
> > 
> > Is the Wi-Fi solution different?
> 
> ditto

NAK

-- 
With best wishes
Dmitry

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

[Yijie Yang]

On 1/12/2026 1:00 PM, Dmitry Baryshkov wrote:
> On Mon, Jan 12, 2026 at 11:12:09AM +0800, Yijie Yang wrote:
>>
>>
>> On 1/9/2026 7:29 PM, Konrad Dybcio wrote:
>>> On 1/9/26 8:59 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.
>>>
>>> [...]
>>>
>>>> -	backlight: backlight {
>>>> -		compatible = "pwm-backlight";
>>>> -		pwms = <&pmk8550_pwm 0 5000000>;
>>>> -		enable-gpios = <&pmc8380_3_gpios 4 GPIO_ACTIVE_HIGH>;
>>>> -		power-supply = <&vreg_edp_bl>;
>>>> -
>>>> -		pinctrl-0 = <&edp_bl_en>, <&edp_bl_pwm>;
>>>> -		pinctrl-names = "default";
>>>> -	};
>>>
>>> Is the backlight infra different on the Purwa IoT EVK?
>>
>> As you can see, this Purwa file was copied from the latest
>> hamoa-iot-evk.dts. However, not all nodes have been verified on Purwa.
>> Therefore, I need to retain only the functions that work correctly and keep
>> them aligned with the nodes from my initial version. The deleted nodes will
>> be updated later by the respective authors from different technical areas.
> 
> Please, only delete nodes which are not present on the Purwa IoT EVK.

This isn’t a deletion—it’s just not ready yet. Why do we need to include 
all the nodes like a mature Hamoa platform in the initial push?

> 
>>
>>>
>>>> -
>>>>    	wcd938x: audio-codec {
>>>>    		compatible = "qcom,wcd9385-codec";
>>>> @@ -60,32 +50,6 @@ chosen {
>>>>    		stdout-path = "serial0:115200n8";
>>>>    	};
>>>> -	connector3 {
>>>> -		compatible = "usb-a-connector";
>>>> -		label = "USB-3-Type-A";
>>>> -		power-role = "source";
>>>> -
>>>> -		vbus-supply = <&regulator_usb3_vbus>;
>>>> -
>>>> -		port {
>>>> -			connector_3_in: endpoint {
>>>> -			};
>>>> -		};
>>>> -	};
>>>> -
>>>> -	connector6 {
>>>> -		compatible = "usb-a-connector";
>>>> -		label = "USB-6-Type-A";
>>>> -		power-role = "source";
>>>> -
>>>> -		vbus-supply = <&regulator_usb6_vbus>;
>>>> -
>>>> -		port {
>>>> -			connector_4_in: endpoint {
>>>> -			};
>>>> -		};
>>>> -	};
>>>
>>> Are there no Type-A ports?
>>
>> ditto
> 
> ?
> 
>>
>>>> @@ -920,23 +886,6 @@ &mdss_dp3_phy {
>>>>    	status = "okay";
>>>>    };
>>>> -&pcie4_port0 {
>>>> -	wifi@0 {
>>>> -		compatible = "pci17cb,1107";
>>>> -		reg = <0x10000 0x0 0x0 0x0 0x0>;
>>>> -
>>>> -		vddaon-supply = <&vreg_pmu_aon_0p59>;
>>>> -		vddwlcx-supply = <&vreg_pmu_wlcx_0p8>;
>>>> -		vddwlmx-supply = <&vreg_pmu_wlmx_0p85>;
>>>> -		vddrfacmn-supply = <&vreg_pmu_rfa_cmn>;
>>>> -		vddrfa0p8-supply = <&vreg_pmu_rfa_0p8>;
>>>> -		vddrfa1p2-supply = <&vreg_pmu_rfa_1p2>;
>>>> -		vddrfa1p8-supply = <&vreg_pmu_rfa_1p8>;
>>>> -		vddpcie0p9-supply = <&vreg_pmu_pcie_0p9>;
>>>> -		vddpcie1p8-supply = <&vreg_pmu_pcie_1p8>;
>>>> -	};
>>>> -};
>>>
>>> Is the Wi-Fi solution different?
>>
>> ditto
> 
> NAK
> 

-- 
Best Regards,
Yijie

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

[Dmitry Baryshkov]

On Mon, 12 Jan 2026 at 07:51, Yijie Yang <yijie.yang@oss.qualcomm.com> wrote:
>
>
>
> On 1/12/2026 1:00 PM, Dmitry Baryshkov wrote:
> > On Mon, Jan 12, 2026 at 11:12:09AM +0800, Yijie Yang wrote:
> >>
> >>
> >> On 1/9/2026 7:29 PM, Konrad Dybcio wrote:
> >>> On 1/9/26 8:59 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.
> >>>
> >>> [...]
> >>>
> >>>> -  backlight: backlight {
> >>>> -          compatible = "pwm-backlight";
> >>>> -          pwms = <&pmk8550_pwm 0 5000000>;
> >>>> -          enable-gpios = <&pmc8380_3_gpios 4 GPIO_ACTIVE_HIGH>;
> >>>> -          power-supply = <&vreg_edp_bl>;
> >>>> -
> >>>> -          pinctrl-0 = <&edp_bl_en>, <&edp_bl_pwm>;
> >>>> -          pinctrl-names = "default";
> >>>> -  };
> >>>
> >>> Is the backlight infra different on the Purwa IoT EVK?
> >>
> >> As you can see, this Purwa file was copied from the latest
> >> hamoa-iot-evk.dts. However, not all nodes have been verified on Purwa.
> >> Therefore, I need to retain only the functions that work correctly and keep
> >> them aligned with the nodes from my initial version. The deleted nodes will
> >> be updated later by the respective authors from different technical areas.
> >
> > Please, only delete nodes which are not present on the Purwa IoT EVK.
>
> This isn’t a deletion—it’s just not ready yet. Why do we need to include
> all the nodes like a mature Hamoa platform in the initial push?

Purwa seems to be mature enough. What exactly can't be enabled at this moment?

-- 
With best wishes
Dmitry

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

[Konrad Dybcio]

On 1/12/26 7:01 AM, Dmitry Baryshkov wrote:
> On Mon, 12 Jan 2026 at 07:51, Yijie Yang <yijie.yang@oss.qualcomm.com> wrote:
>>
>>
>>
>> On 1/12/2026 1:00 PM, Dmitry Baryshkov wrote:
>>> On Mon, Jan 12, 2026 at 11:12:09AM +0800, Yijie Yang wrote:
>>>>
>>>>
>>>> On 1/9/2026 7:29 PM, Konrad Dybcio wrote:
>>>>> On 1/9/26 8:59 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.
>>>>>
>>>>> [...]
>>>>>
>>>>>> -  backlight: backlight {
>>>>>> -          compatible = "pwm-backlight";
>>>>>> -          pwms = <&pmk8550_pwm 0 5000000>;
>>>>>> -          enable-gpios = <&pmc8380_3_gpios 4 GPIO_ACTIVE_HIGH>;
>>>>>> -          power-supply = <&vreg_edp_bl>;
>>>>>> -
>>>>>> -          pinctrl-0 = <&edp_bl_en>, <&edp_bl_pwm>;
>>>>>> -          pinctrl-names = "default";
>>>>>> -  };
>>>>>
>>>>> Is the backlight infra different on the Purwa IoT EVK?
>>>>
>>>> As you can see, this Purwa file was copied from the latest
>>>> hamoa-iot-evk.dts. However, not all nodes have been verified on Purwa.
>>>> Therefore, I need to retain only the functions that work correctly and keep
>>>> them aligned with the nodes from my initial version. The deleted nodes will
>>>> be updated later by the respective authors from different technical areas.
>>>
>>> Please, only delete nodes which are not present on the Purwa IoT EVK.
>>
>> This isn’t a deletion—it’s just not ready yet. Why do we need to include
>> all the nodes like a mature Hamoa platform in the initial push?
> 
> Purwa seems to be mature enough. What exactly can't be enabled at this moment?

Right, I'm in the same camp. Since you already have the board at your
disposal (because I trust you tested this patchset on hardware), why
not spend the extra 5-10 minutes verifying that e.g. the display lights
up and you can control its brightness?

Konrad

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

[Yijie Yang]

On 1/12/2026 2:01 PM, Dmitry Baryshkov wrote:
> On Mon, 12 Jan 2026 at 07:51, Yijie Yang <yijie.yang@oss.qualcomm.com> wrote:
>>
>>
>>
>> On 1/12/2026 1:00 PM, Dmitry Baryshkov wrote:
>>> On Mon, Jan 12, 2026 at 11:12:09AM +0800, Yijie Yang wrote:
>>>>
>>>>
>>>> On 1/9/2026 7:29 PM, Konrad Dybcio wrote:
>>>>> On 1/9/26 8:59 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.
>>>>>
>>>>> [...]
>>>>>
>>>>>> -  backlight: backlight {
>>>>>> -          compatible = "pwm-backlight";
>>>>>> -          pwms = <&pmk8550_pwm 0 5000000>;
>>>>>> -          enable-gpios = <&pmc8380_3_gpios 4 GPIO_ACTIVE_HIGH>;
>>>>>> -          power-supply = <&vreg_edp_bl>;
>>>>>> -
>>>>>> -          pinctrl-0 = <&edp_bl_en>, <&edp_bl_pwm>;
>>>>>> -          pinctrl-names = "default";
>>>>>> -  };
>>>>>
>>>>> Is the backlight infra different on the Purwa IoT EVK?
>>>>
>>>> As you can see, this Purwa file was copied from the latest
>>>> hamoa-iot-evk.dts. However, not all nodes have been verified on Purwa.
>>>> Therefore, I need to retain only the functions that work correctly and keep
>>>> them aligned with the nodes from my initial version. The deleted nodes will
>>>> be updated later by the respective authors from different technical areas.
>>>
>>> Please, only delete nodes which are not present on the Purwa IoT EVK.
>>
>> This isn’t a deletion—it’s just not ready yet. Why do we need to include
>> all the nodes like a mature Hamoa platform in the initial push?
> 
> Purwa seems to be mature enough. What exactly can't be enabled at this moment?
> 

There were some errors during boot when those nodes were added in my 
previous test. Anyway, I’ll fix the issues and add them all.

-- 
Best Regards,
Yijie

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

[Krzysztof Kozlowski]

On 12/01/2026 06:51, Yijie Yang wrote:
>>>>
>>>> Is the backlight infra different on the Purwa IoT EVK?
>>>
>>> As you can see, this Purwa file was copied from the latest
>>> hamoa-iot-evk.dts. However, not all nodes have been verified on Purwa.
>>> Therefore, I need to retain only the functions that work correctly and keep
>>> them aligned with the nodes from my initial version. The deleted nodes will
>>> be updated later by the respective authors from different technical areas.
>>
>> Please, only delete nodes which are not present on the Purwa IoT EVK.
> 
> This isn’t a deletion—it’s just not ready yet. Why do we need to include 
> all the nodes like a mature Hamoa platform in the initial push?


Because you said it is exactly the same module...

Best regards,
Krzysztof

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

[Krzysztof Kozlowski]

On 09/01/2026 08:59, YijieYang wrote:
> 
> Signed-off-by: Yijie Yang <yijie.yang@oss.qualcomm.com>
> ---
> Changes since V1:
> - 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.

That's a b4 patchset, so where are the links?

> 
> ---
> 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      | 1313 +++++++++++++++++++++++
>  arch/arm64/boot/dts/qcom/purwa-iot-som.dtsi     |  614 +++++++++++
>  drivers/firmware/qcom/qcom_scm.c                |    1 +
>  5 files changed, 1935 insertions(+)
> ---
> base-commit: beff4beeeb2760405ad49de2a6a1bdab8fb1aec3
> change-id: 20251113-purwa-907ec75b4959
> 


Best regards,
Krzysztof

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

[Yijie Yang]

On 1/9/2026 4:06 PM, Krzysztof Kozlowski wrote:
> On 09/01/2026 08:59, YijieYang wrote:
>>
>> Signed-off-by: Yijie Yang <yijie.yang@oss.qualcomm.com>
>> ---
>> Changes since V1:
>> - 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.
> 
> That's a b4 patchset, so where are the links?

Sorry about that. I generated the patch set using git format-patch with 
format control options for easier review, while creating the cover 
letter with b4. Since the version number does not increase 
automatically, the change list was written manually, and I missed adding 
the link to v1. I will include it in the following versions.

- Link to v1: 
https://lore.kernel.org/all/20251222-purwa-v1-0-14ab9316e5ff@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      | 1313 +++++++++++++++++++++++
>>   arch/arm64/boot/dts/qcom/purwa-iot-som.dtsi     |  614 +++++++++++
>>   drivers/firmware/qcom/qcom_scm.c                |    1 +
>>   5 files changed, 1935 insertions(+)
>> ---
>> base-commit: beff4beeeb2760405ad49de2a6a1bdab8fb1aec3
>> change-id: 20251113-purwa-907ec75b4959
>>
> 
> 
> Best regards,
> Krzysztof

-- 
Best Regards,
Yijie

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

[Krzysztof Kozlowski]

On 09/01/2026 09:26, Yijie Yang wrote:
> 
> 
> On 1/9/2026 4:06 PM, Krzysztof Kozlowski wrote:
>> On 09/01/2026 08:59, YijieYang wrote:
>>>
>>> Signed-off-by: Yijie Yang <yijie.yang@oss.qualcomm.com>
>>> ---
>>> Changes since V1:
>>> - 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.
>>
>> That's a b4 patchset, so where are the links?
> 
> Sorry about that. I generated the patch set using git format-patch with 
> format control options for easier review, while creating the cover 
> letter with b4. Since the version number does not increase 
> automatically, the change list was written manually, and I missed adding 
> the link to v1. I will include it in the following versions.
> 
> - Link to v1: 
> https://lore.kernel.org/all/20251222-purwa-v1-0-14ab9316e5ff@oss.qualcomm.com/

Ah, ok, that's fine although if you re-roll b4 managed branch, you would
still get the link added by b4.

Best regards,
Krzysztof

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

[Konrad Dybcio]

On 1/9/26 9:26 AM, Yijie Yang wrote:
> 
> 
> On 1/9/2026 4:06 PM, Krzysztof Kozlowski wrote:
>> On 09/01/2026 08:59, YijieYang wrote:
>>>
>>> Signed-off-by: Yijie Yang <yijie.yang@oss.qualcomm.com>
>>> ---
>>> Changes since V1:
>>> - 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.
>>
>> That's a b4 patchset, so where are the links?
> 
> Sorry about that. I generated the patch set using git format-patch with format control options for easier review, while creating the cover letter with b4. Since the version number does not increase automatically, the change list was written manually, and I missed adding the link to v1. I will include it in the following versions.

Adding

[diff]
        renameLimit = 999999
	algorithm = patience

to your .gitconfig should work too (perhaps comment it out after
you're done sending a largely copy-and-alter-a-big-file patchset
like this)

Konrad

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

[Yijie Yang]

On 1/9/2026 5:28 PM, Konrad Dybcio wrote:
> On 1/9/26 9:26 AM, Yijie Yang wrote:
>>
>>
>> On 1/9/2026 4:06 PM, Krzysztof Kozlowski wrote:
>>> On 09/01/2026 08:59, YijieYang wrote:
>>>>
>>>> Signed-off-by: Yijie Yang <yijie.yang@oss.qualcomm.com>
>>>> ---
>>>> Changes since V1:
>>>> - 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.
>>>
>>> That's a b4 patchset, so where are the links?
>>
>> Sorry about that. I generated the patch set using git format-patch with format control options for easier review, while creating the cover letter with b4. Since the version number does not increase automatically, the change list was written manually, and I missed adding the link to v1. I will include it in the following versions.
> 
> Adding
> 
> [diff]
>          renameLimit = 999999
> 	algorithm = patience
> 
> to your .gitconfig should work too (perhaps comment it out after
> you're done sending a largely copy-and-alter-a-big-file patchset
> like this)

That sounds like a good solution—thanks for the reminder.

> 
> Konrad

-- 
Best Regards,
Yijie