From dff02ccde18e12886a59bac0fbca8516a8864f22 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=C3=81ngel=20Ren=C3=A9?= <17342133+angelrenefm@users.noreply.github.com> Date: Tue, 3 Nov 2026 19:35:12 +0100 Subject: [PATCH] arm64: dts: exynos: google: gs201-panther: add Wi-Fi MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The Pixel 7 has the Pixel 7 Pro's BCM4389 on the same PCIe lines: stock's panther MP overlay (board id 0x30406) puts WL_REG_ON on gph2-4, WL_DEV_WAKE on gph2-5 and WL_HOST_WAKE on gpa6-1, as cheetah's does, and keeps the PCIe rails always on. Google's own device tree agrees: in kernel/devices/google/pantah (branch android-gs-pantah-6.1-android16), gs201-panther-common.dtsi includes the same gs201-cloudripper-wlan.dtsi as the Pixel 7 Pro, and no panther file overrides those pins. Take cheetah's Wi-Fi nodes: the WL_REG_ON regulator, the restricted DMA pool and the Wi-Fi node's memory-region, PCIe GEN4A_1 and its PHY, the System MMU's DMA window and the pins, with the board type the Pixel 7's firmware names carry. Bluetooth is left to its own commit. On a Pixel 7, a kernel with these nodes and the Bluetooth ones brought up the link at Gen2 x1, found BCM4389/3 with the phone's own firmware, and connected wlp1s0 to a network. A second Pixel 7 ran omamobile with only the Bluetooth commit and this one: the link came up on the first try, and in two runs of Wi-Fi downloads alongside heavy writes to userdata every checksum matched. Assisted-by: LLM Signed-off-by: Ángel René <17342133+angelrenefm@users.noreply.github.com> --- .../boot/dts/exynos/google/gs201-panther.dts | 106 ++++++++++++++++++ 1 file changed, 106 insertions(+) diff --git a/arch/arm64/boot/dts/exynos/google/gs201-panther.dts b/arch/arm64/boot/dts/exynos/google/gs201-panther.dts index b4a13e17ae..02813bf984 100644 --- a/arch/arm64/boot/dts/exynos/google/gs201-panther.dts +++ b/arch/arm64/boot/dts/exynos/google/gs201-panther.dts @@ -104,11 +104,45 @@ regulator-boot-on; }; + /* + * WL_REG_ON of the BCM4389. Google raises it and waits 200 ms before + * training the link (WIFI_TURNON_DELAY in bcmdhd). Modelled as the + * root port's supply so the PCI pwrctrl core switches it around link + * training. With pcie_1 disabled nothing enables it, so the chip + * stays off. + */ + wlan_pwr: regulator-wlan { + compatible = "regulator-fixed"; + regulator-name = "wlan-reg-on"; + regulator-min-microvolt = <3300000>; + regulator-max-microvolt = <3300000>; + gpio = <&gph2 4 GPIO_ACTIVE_HIGH>; + enable-active-high; + startup-delay-us = <200000>; + pinctrl-0 = <&wlan_reg_on>; + pinctrl-names = "default"; + }; + reserved-memory { #address-cells = <2>; #size-cells = <1>; ranges; + /* + * All of the Wi-Fi chip's DMA buffers come from this pool. It + * keeps driver bugs and stray pointers away from the rest of + * RAM; it does not stop the chip's own firmware from reaching + * other memory (the HSI2 SysMMU and S2MPU see the PCIe and UFS + * masters on the same VID, so neither can confine it alone). + */ + wifi_dma_pool: wifi-dma-pool { + compatible = "restricted-dma-pool"; + size = <0x1000000>; + alignment = <0x0 0x200000>; + /* the chip's writes above 4 GiB are not seen */ + alloc-ranges = <0x0 0x80000000 0x80000000>; + }; + /* * Stock's region and layout (ramoops_mem@fd3ff000 in its live * tree), so a log from this kernel can be read after a warm @@ -339,6 +373,13 @@ samsung,pin-pud = ; samsung,pin-drv = ; }; + + wlan_host_wake: wlan-host-wake-pins { + samsung,pins = "gpa6-1"; + samsung,pin-function = ; + samsung,pin-pud = ; + samsung,pin-drv = ; + }; }; &pinctrl_gpio_alive { @@ -467,3 +508,68 @@ }; }; }; + +/* + * Wi-Fi: BCM4389 on PCIe GEN4A_1, one lane at Gen2 as on stock. The chip's + * DMA buffers come from wifi_dma_pool. The chip's 0.85 V and 1.8 V PCIe + * rails (S2MPG13 LDO3 and LDO18) are always on. + */ +&pcie_1 { + status = "okay"; + pinctrl-0 = <&pcie1_clkreq>, <&pcie1_perst>, <&wlan_dev_wake>, + <&wlan_host_wake>; + pinctrl-names = "default"; + + pcie@0,0 { + compatible = "pciclass,0604"; + device_type = "pci"; + reg = <0x0 0x0 0x0 0x0 0x0>; + bus-range = <0x01 0xff>; + #address-cells = <3>; + #size-cells = <2>; + ranges; + vpcie3v3-supply = <&wlan_pwr>; + + wifi@0,0 { + compatible = "pci14e4,4441"; + reg = <0x10000 0x0 0x0 0x0 0x0>; + brcm,board-type = "google,gs201-panther"; + memory-region = <&wifi_dma_pool>; + }; + }; +}; + +&pcie_1_phy { + status = "okay"; +}; + +/* + * The window for the PCIe System MMU. The node stays disabled: the PCIe and + * UFS masters share its VID 0, so it cannot confine the Wi-Fi chip without + * also confining storage. + */ +&pcie_1_sysmmu { + google,dma-window = <&wifi_dma_pool>; +}; + +&pinctrl_hsi2 { + status = "okay"; + + wlan_reg_on: wlan-reg-on-pins { + samsung,pins = "gph2-4"; + samsung,pin-function = ; + samsung,pin-pud = ; + samsung,pin-drv = ; + samsung,pin-con-pdn = ; + samsung,pin-pud-pdn = ; + }; + + wlan_dev_wake: wlan-dev-wake-pins { + samsung,pins = "gph2-5"; + samsung,pin-function = ; + samsung,pin-pud = ; + samsung,pin-drv = ; + samsung,pin-con-pdn = ; + samsung,pin-pud-pdn = ; + }; +};