linux-kernel - Re: [PATCH] arm64: dts: qcom: hamoa-iot-evk: Add WLAN node for hamoa 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 for Android: free password hash cracker in your pocket

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

Message-ID: <gah6rlxl6morhezm5dyknb7dg2uaqdd2uk3y5cvzsznpywal7k@xzfxc3kuvds4>
Date: Tue, 9 Dec 2025 17:14:07 +0200
From: Dmitry Baryshkov <dmitry.baryshkov@....qualcomm.com>
To: Yingying Tang <yingying.tang@....qualcomm.com>
Cc: andersson@...nel.org, konradybcio@...nel.org,
        linux-arm-msm@...r.kernel.org, devicetree@...r.kernel.org,
        linux-kernel@...r.kernel.org, tingweiz@....qualcomm.com,
        yijiyang@....qualcomm.com
Subject: Re: [PATCH] arm64: dts: qcom: hamoa-iot-evk: Add WLAN node for hamoa
 iot evk board

On Tue, Dec 09, 2025 at 07:59:24PM +0800, Yingying Tang wrote:
> WLAN card is connected to PCIe4 on hamoa iot evk board. Add WLAN node

IoT, EVK (the same applies to the subject).

> to support power sequence for this WLAN card.
> 
> Signed-off-by: Yingying Tang <yingying.tang@....qualcomm.com>
> ---
>  arch/arm64/boot/dts/qcom/hamoa-iot-evk.dts | 26 +++++++++++++++++++++-
>  1 file changed, 25 insertions(+), 1 deletion(-)
> 
> diff --git a/arch/arm64/boot/dts/qcom/hamoa-iot-evk.dts b/arch/arm64/boot/dts/qcom/hamoa-iot-evk.dts
> index 36dd6599402b..d66d337292ef 100644
> --- a/arch/arm64/boot/dts/qcom/hamoa-iot-evk.dts
> +++ b/arch/arm64/boot/dts/qcom/hamoa-iot-evk.dts
> @@ -534,7 +534,7 @@ wcn7850-pmu {
>  		bt-enable-gpios = <&tlmm 116 GPIO_ACTIVE_HIGH>;
>  		wlan-enable-gpios = <&tlmm 117 GPIO_ACTIVE_HIGH>;
>  
> -		pinctrl-0 = <&wcn_bt_en>;
> +		pinctrl-0 = <&wcn_bt_en>, <&wcn_wlan_en>;

So, it was specified, but it wasn't a part of the pinctrl?

>  		pinctrl-names = "default";
>  
>  		regulators {
> @@ -844,6 +844,23 @@ &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>;
>  };
> @@ -1143,6 +1160,13 @@ wcn_bt_en: wcn-bt-en-state {
>  		bias-disable;
>  	};
>  
> +	wcn_wlan_en: wcn-wlan-en-state {
> +		pins = "gpio117";
> +		function = "gpio";
> +		drive-strength = <2>;
> +		bias-disable;
> +	};
> +
>  	wwan_sw_en: wwan-sw-en-state {
>  		pins = "gpio221";
>  		function = "gpio";
> -- 
> 2.25.1
> 

-- 
With best wishes
Dmitry