arch/arm64/boot/dts/qcom/glymur-crd.dtsi | 118 +++++++++++++++++++++++++++++-- 1 file changed, 112 insertions(+), 6 deletions(-)
Both Glymur and Mahua CRDs feature a WCN7850 M.2 WLAN and Bluetooth
combo card.
So describe both the 0.9V and the 3.3V regulators, then WCN7850 PMU and
the PCIe WLAN and the UART Bluetooth nodes.
Do this in the Glymur CRD generic dtsi so that both Glymur and Mahua CRDs
benefit from it towards enabling WLAN and Bluetooth functionality.
Signed-off-by: Abel Vesa <abel.vesa@oss.qualcomm.com>
---
Sending as RFT since I only tested this on Glymur CRD.
As far as I know, Mahua CRD uses the same WCN7850 board, but I do
not have (yet) access to a Mahua CRD to test on.
---
Changes in v2:
- Rebased on next-20260323.
- Address commit message issue reported by Zijun
- Dropped the vddio1p2-supply as Zijun suggested.
- Did not rework with the M.2 connector since the E Key is still
under review on the list.
- Re-worked so that it is done in the generic CRD dtsi in order
to add the same support for Mahua CRD.
- Link to v1: https://patch.msgid.link/20260309-glymur-dts-crd-enable-bt-wlan-v1-1-3badbddd5439@oss.qualcomm.com
---
arch/arm64/boot/dts/qcom/glymur-crd.dtsi | 118 +++++++++++++++++++++++++++++--
1 file changed, 112 insertions(+), 6 deletions(-)
diff --git a/arch/arm64/boot/dts/qcom/glymur-crd.dtsi b/arch/arm64/boot/dts/qcom/glymur-crd.dtsi
index abc6cc8bb0a8..2852d257ac8c 100644
--- a/arch/arm64/boot/dts/qcom/glymur-crd.dtsi
+++ b/arch/arm64/boot/dts/qcom/glymur-crd.dtsi
@@ -89,17 +89,27 @@ vreg_nvmesec: regulator-nvmesec {
regulator-boot-on;
};
- vreg_wlan: regulator-wlan {
+ vreg_wcn_0p95: regulator-wcn-0p95 {
compatible = "regulator-fixed";
- regulator-name = "VREG_WLAN_3P3";
+ regulator-name = "VREG_WCN_0P95";
+ regulator-min-microvolt = <950000>;
+ regulator-max-microvolt = <950000>;
+
+ vin-supply = <&vreg_wcn_3p3>;
+ };
+
+ vreg_wcn_3p3: regulator-wcn-3p3 {
+ compatible = "regulator-fixed";
+
+ regulator-name = "VREG_WCN_3P3";
regulator-min-microvolt = <3300000>;
regulator-max-microvolt = <3300000>;
gpio = <&tlmm 94 GPIO_ACTIVE_HIGH>;
enable-active-high;
- pinctrl-0 = <&wlan_reg_en>;
+ pinctrl-0 = <&wcn_sw_en>;
pinctrl-names = "default";
regulator-boot-on;
@@ -118,6 +128,65 @@ vreg_wwan: regulator-wwan {
pinctrl-0 = <&wwan_reg_en>;
pinctrl-names = "default";
};
+
+ wcn7850-pmu {
+ compatible = "qcom,wcn7850-pmu";
+
+ vdd-supply = <&vreg_wcn_0p95>;
+ vddio-supply = <&vreg_l15b_e0_1p8>;
+ vddaon-supply = <&vreg_l15b_e0_1p8>;
+ vdddig-supply = <&vreg_l15b_e0_1p8>;
+ vddrfa1p2-supply = <&vreg_l15b_e0_1p8>;
+ vddrfa1p8-supply = <&vreg_l15b_e0_1p8>;
+
+ wlan-enable-gpios = <&tlmm 117 GPIO_ACTIVE_HIGH>;
+ bt-enable-gpios = <&tlmm 116 GPIO_ACTIVE_HIGH>;
+
+ pinctrl-0 = <&wcn_wlan_bt_en>;
+ pinctrl-names = "default";
+
+ regulators {
+ vreg_pmu_rfa_cmn: ldo0 {
+ regulator-name = "vreg_pmu_rfa_cmn";
+ };
+
+ vreg_pmu_aon_0p59: ldo1 {
+ regulator-name = "vreg_pmu_aon_0p59";
+ };
+
+ vreg_pmu_wlcx_0p8: ldo2 {
+ regulator-name = "vreg_pmu_wlcx_0p8";
+ };
+
+ vreg_pmu_wlmx_0p85: ldo3 {
+ regulator-name = "vreg_pmu_wlmx_0p85";
+ };
+
+ vreg_pmu_btcmx_0p85: ldo4 {
+ regulator-name = "vreg_pmu_btcmx_0p85";
+ };
+
+ vreg_pmu_rfa_0p8: ldo5 {
+ regulator-name = "vreg_pmu_rfa_0p8";
+ };
+
+ vreg_pmu_rfa_1p2: ldo6 {
+ regulator-name = "vreg_pmu_rfa_1p2";
+ };
+
+ vreg_pmu_rfa_1p8: ldo7 {
+ regulator-name = "vreg_pmu_rfa_1p8";
+ };
+
+ vreg_pmu_pcie_0p9: ldo8 {
+ regulator-name = "vreg_pmu_pcie_0p9";
+ };
+
+ vreg_pmu_pcie_1p8: ldo9 {
+ regulator-name = "vreg_pmu_pcie_1p8";
+ };
+ };
+ };
};
&apps_rsc {
@@ -382,8 +451,6 @@ &pcie3b_port0 {
};
&pcie4 {
- vddpe-3v3-supply = <&vreg_wlan>;
-
pinctrl-0 = <&pcie4_default>;
pinctrl-names = "default";
@@ -400,6 +467,21 @@ &pcie4_phy {
&pcie4_port0 {
reset-gpios = <&tlmm 146 GPIO_ACTIVE_LOW>;
wake-gpios = <&tlmm 148 GPIO_ACTIVE_LOW>;
+
+ 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>;
+ };
};
&pcie5 {
@@ -575,7 +657,14 @@ wake-n-pins {
};
};
- wlan_reg_en: wlan-reg-en-state {
+ wcn_wlan_bt_en: wcn-wlan-bt-en-state {
+ pins = "gpio116", "gpio117";
+ function = "gpio";
+ drive-strength = <2>;
+ bias-disable;
+ };
+
+ wcn_sw_en: wcn-sw-en-state {
pins = "gpio94";
function = "gpio";
drive-strength = <2>;
@@ -589,3 +678,20 @@ wwan_reg_en: wwan-reg-en-state {
bias-disable;
};
};
+
+&uart14 {
+ status = "okay";
+
+ bluetooth {
+ compatible = "qcom,wcn7850-bt";
+ max-speed = <3200000>;
+
+ 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>;
+ };
+};
---
base-commit: 5138081b838d92e1bfcddc7b72b9215cca6e83f0
change-id: 20260309-glymur-dts-crd-enable-bt-wlan-db90c414ebaa
Best regards,
--
Abel Vesa <abel.vesa@oss.qualcomm.com>
On Tue, 24 Mar 2026 17:12:19 +0200, Abel Vesa wrote:
> Both Glymur and Mahua CRDs feature a WCN7850 M.2 WLAN and Bluetooth
> combo card.
>
> So describe both the 0.9V and the 3.3V regulators, then WCN7850 PMU and
> the PCIe WLAN and the UART Bluetooth nodes.
>
> Do this in the Glymur CRD generic dtsi so that both Glymur and Mahua CRDs
> benefit from it towards enabling WLAN and Bluetooth functionality.
>
> [...]
Applied, thanks!
[1/1] arm64: dts: qcom: glymur-crd: Enable WLAN and Bluetooth
commit: 151206a1c2db874d39ddca60901a77204dddf065
Best regards,
--
Bjorn Andersson <andersson@kernel.org>
On 3/24/2026 8:42 PM, Abel Vesa wrote: > Both Glymur and Mahua CRDs feature a WCN7850 M.2 WLAN and Bluetooth > combo card. > > So describe both the 0.9V and the 3.3V regulators, then WCN7850 PMU and > the PCIe WLAN and the UART Bluetooth nodes. > > Do this in the Glymur CRD generic dtsi so that both Glymur and Mahua CRDs > benefit from it towards enabling WLAN and Bluetooth functionality. > > Signed-off-by: Abel Vesa <abel.vesa@oss.qualcomm.com> > --- > Sending as RFT since I only tested this on Glymur CRD. > As far as I know, Mahua CRD uses the same WCN7850 board, but I do > not have (yet) access to a Mahua CRD to test on. Tested-by: Gopikrishna Garmidi <gopikrishna.garmidi@oss.qualcomm.com> Best regards, -- Gopikrishna Garmidi <gopikrishna.garmidi@oss.qualcomm.com>
On 3/24/2026 11:12 PM, Abel Vesa wrote: > Both Glymur and Mahua CRDs feature a WCN7850 M.2 WLAN and Bluetooth > combo card. > > So describe both the 0.9V and the 3.3V regulators, then WCN7850 PMU and > the PCIe WLAN and the UART Bluetooth nodes. > > Do this in the Glymur CRD generic dtsi so that both Glymur and Mahua CRDs > benefit from it towards enabling WLAN and Bluetooth functionality. > > Signed-off-by: Abel Vesa <abel.vesa@oss.qualcomm.com> > --- > Sending as RFT since I only tested this on Glymur CRD. > As far as I know, Mahua CRD uses the same WCN7850 board, but I do > not have (yet) access to a Mahua CRD to test on. > --- > Changes in v2: > - Rebased on next-20260323. > - Address commit message issue reported by Zijun > - Dropped the vddio1p2-supply as Zijun suggested. > - Did not rework with the M.2 connector since the E Key is still > under review on the list. > - Re-worked so that it is done in the generic CRD dtsi in order > to add the same support for Mahua CRD. > - Link to v1: https://patch.msgid.link/20260309-glymur-dts-crd-enable-bt-wlan-v1-1-3badbddd5439@oss.qualcomm.com > --- > arch/arm64/boot/dts/qcom/glymur-crd.dtsi | 118 +++++++++++++++++++++++++++++-- > 1 file changed, 112 insertions(+), 6 deletions(-) Reviewed-by: Zijun Hu <zijun.hu@oss.qualcomm.com>
On Tue, Mar 24, 2026 at 05:12:19PM +0200, Abel Vesa wrote: > Both Glymur and Mahua CRDs feature a WCN7850 M.2 WLAN and Bluetooth > combo card. > > So describe both the 0.9V and the 3.3V regulators, then WCN7850 PMU and > the PCIe WLAN and the UART Bluetooth nodes. > > Do this in the Glymur CRD generic dtsi so that both Glymur and Mahua CRDs > benefit from it towards enabling WLAN and Bluetooth functionality. > > Signed-off-by: Abel Vesa <abel.vesa@oss.qualcomm.com> > --- > Sending as RFT since I only tested this on Glymur CRD. > As far as I know, Mahua CRD uses the same WCN7850 board, but I do > not have (yet) access to a Mahua CRD to test on. > --- > Changes in v2: > - Rebased on next-20260323. > - Address commit message issue reported by Zijun > - Dropped the vddio1p2-supply as Zijun suggested. > - Did not rework with the M.2 connector since the E Key is still > under review on the list. > - Re-worked so that it is done in the generic CRD dtsi in order > to add the same support for Mahua CRD. > - Link to v1: https://patch.msgid.link/20260309-glymur-dts-crd-enable-bt-wlan-v1-1-3badbddd5439@oss.qualcomm.com > --- > arch/arm64/boot/dts/qcom/glymur-crd.dtsi | 118 +++++++++++++++++++++++++++++-- > 1 file changed, 112 insertions(+), 6 deletions(-) > Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com> -- With best wishes Dmitry
© 2016 - 2026 Red Hat, Inc.