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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <6e8e6583-033f-439e-bd92-b24fe432fb96@oss.qualcomm.com>
Date: Fri, 9 Jan 2026 12:29:34 +0100
From: Konrad Dybcio <konrad.dybcio@....qualcomm.com>
To: YijieYang <yijie.yang@....qualcomm.com>, andersson@...nel.org,
        konradybcio@...nel.org, robh@...nel.org, krzk+dt@...nel.org,
        conor+dt@...nel.org
Cc: linux-arm-msm@...r.kernel.org, linux-kernel@...r.kernel.org,
        devicetree@...r.kernel.org, krzysztof.kozlowski@....qualcomm.com
Subject: Re: [PATCH v2 4/4] arm64: dts: qcom: Add base PURWA-IOT-EVK board

On 1/9/26 8:59 AM, YijieYang wrote:
> From: Yijie Yang <yijie.yang@....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