From 30679f8a57b16ff62e11dca8c708d1ddd89c358a Mon Sep 17 00:00:00 2001 From: Alejandro Garcia Date: Wed, 28 Oct 2026 14:02:30 -0700 Subject: [PATCH 1/5] arm64: dts: exynos: google: gs201-panther: enable the GPU Enable the Mali-G710 that gs201.dtsi describes, as the Pixel 7 Pro does. Its clock is the ACPM GPU clock, which this board already gets through acpm_ipc, and as on the Pixel 7 Pro there is no mali-supply: the G3D rails follow the PMU power domain and ACPM, and the bootloader leaves the GPU powered. Tested on a Pixel 7 from slot B (7.3.0-rc6), with the device package's rule that keeps the GPU powered: panthor probes the Mali-G710 (id 0xa862, shader_present 0x1110055), boots the CSF firmware (interface v1.5.0) and registers renderD128, and Hyprland renders on it through Mesa's panfrost ("Mali-G710 MC7 (Panfrost)") with no MMU faults or GPU resets. As on the Pixel 7 Pro, probe prints "no regulator (mali)" from the OPP core. Assisted-by: Claude Opus 5.5 Signed-off-by: Alejandro Garcia --- arch/arm64/boot/dts/exynos/google/gs201-panther.dts | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/arch/arm64/boot/dts/exynos/google/gs201-panther.dts b/arch/arm64/boot/dts/exynos/google/gs201-panther.dts index d3e061a5b6..36dd97b492 100644 --- a/arch/arm64/boot/dts/exynos/google/gs201-panther.dts +++ b/arch/arm64/boot/dts/exynos/google/gs201-panther.dts @@ -4,8 +4,8 @@ * * USB (NCM + ACM), the cluster watchdogs from gs201.dtsi, a * simple-framebuffer on the buffer ABL leaves DPP0 scanning out, UFS, the - * three keys, and the touch rails on the main PMIC. The panel driver, - * touch and the GPU stay disabled. + * three keys, the touch rails on the main PMIC, and the GPU. The panel + * driver and touch stay disabled. */ /dts-v1/; @@ -149,6 +149,11 @@ }; }; +&gpu { + /* No mali-supply: the G3D rails follow the PMU power domain and ACPM. */ + status = "okay"; +}; + &usbdrd31_phy { status = "okay"; }; From 26c95e813f039ca245260756d0d9e8b79aaee36b Mon Sep 17 00:00:00 2001 From: Alejandro Garcia Date: Wed, 28 Oct 2026 14:02:55 -0700 Subject: [PATCH 2/5] arm64: dts: exynos: google: gs201-panther: add the haptics Describe the CS40L26A haptics driver at 0x43 on USI8 I2C, as on the Pixel 7 Pro: the same bus (gpp16-0/1 at 400 kHz), interrupt (gpa8-1) and reset (gpp24-3) as the Pixel 7 Pro, and the same stock boost and actuator values (peak current 2.5 A, boost 11 V, f0 145 Hz, ReDC 13 ohm), all read from the Pixel 7's live device tree. Enable the PERIC0 pin controller, USI8 and its I2C bus with it. The driver loads its RAM firmware (cs40l26.wmfw) and, if present, the wavetable (cs40l26.bin), from the phone's own vendor files; without the firmware it does not probe. Tested on a Pixel 7 from slot B (7.3.0-rc6), with the GPU enabled as well: cs40l26-vibra probes the CS40L26 (ID 0x40a260, revision A1), loads cs40l26.wmfw (v7.2.91) and cs40l26.bin, and registers cs40l26_vibra; FF_RUMBLE effects of 100-500 ms at 25-80 % play through tools/ff-rumble and are felt, with no errors from the driver. Assisted-by: Claude Opus 5.5 Signed-off-by: Alejandro Garcia --- .../boot/dts/exynos/google/gs201-panther.dts | 57 ++++++++++++++++++- 1 file changed, 55 insertions(+), 2 deletions(-) diff --git a/arch/arm64/boot/dts/exynos/google/gs201-panther.dts b/arch/arm64/boot/dts/exynos/google/gs201-panther.dts index 36dd97b492..fa2d96a760 100644 --- a/arch/arm64/boot/dts/exynos/google/gs201-panther.dts +++ b/arch/arm64/boot/dts/exynos/google/gs201-panther.dts @@ -4,13 +4,14 @@ * * USB (NCM + ACM), the cluster watchdogs from gs201.dtsi, a * simple-framebuffer on the buffer ABL leaves DPP0 scanning out, UFS, the - * three keys, the touch rails on the main PMIC, and the GPU. The panel - * driver and touch stay disabled. + * three keys, the touch rails on the main PMIC, the GPU and the haptics. + * The panel driver and touch stay disabled. */ /dts-v1/; #include +#include #include "gs201.dtsi" / { @@ -170,3 +171,55 @@ &ufs_0_phy { status = "okay"; }; + +/* + * Haptics: Cirrus Logic CS40L26A at 0x43 on PERIC0 USI8 (Google's I2C bus + * 8), INTb on gpa8-1, RESET on gpp24-3, as on the Pixel 7 Pro. Boost and + * actuator values are the stock ones, the same as the Pixel 7 Pro's + * (bst-ipk 2.5 A, bst-ctl 11 V, f0 145 Hz, ReDC 13 ohm in the live tree). + * The bus pins are on PERIC0 (gpp16-0/1). + */ +&pinctrl_far_alive { + hapt_amp_irq: hapt-amp-irq-pins { + samsung,pins = "gpa8-1"; + samsung,pin-function = ; + samsung,pin-pud = ; + samsung,pin-drv = ; + }; +}; + +&pinctrl_peric0 { + status = "okay"; +}; + +&pinctrl_peric1 { + hapt_amp_rst: hapt-amp-rst-pins { + samsung,pins = "gpp24-3"; + samsung,pin-function = ; + samsung,pin-pud = ; + samsung,pin-drv = ; + }; +}; + +&usi8 { + samsung,mode = ; + status = "okay"; +}; + +&hsi2c_8 { + clock-frequency = <400000>; + status = "okay"; + + haptics: haptic-driver@43 { + compatible = "cirrus,cs40l26a"; + reg = <0x43>; + interrupts-extended = <&gpa8 1 IRQ_TYPE_LEVEL_LOW>; + reset-gpios = <&gpp24 3 GPIO_ACTIVE_LOW>; + pinctrl-0 = <&hapt_amp_irq &hapt_amp_rst>; + pinctrl-names = "default"; + cirrus,boost-peak-microamp = <2500000>; + cirrus,boost-ctl-microvolt = <11000000>; + cirrus,lra-f0-hz = <145>; + cirrus,lra-redc-micro-ohms = <13000000>; + }; +}; From b2fe8d70fa6bea118bf9700d9c029711da981f9a Mon Sep 17 00:00:00 2001 From: Alejandro Garcia Date: Wed, 28 Oct 2026 22:28:00 -0700 Subject: [PATCH 3/5] arm64: dts: exynos: google: gs201-panther: default to suspend-to-idle The firmware advertises PSCI SYSTEM_SUSPEND, so the kernel offers deep sleep and makes it the default: /sys/power/mem_sleep reads "s2idle [deep]" on the Pixel 7. Linux has no gs201 sleep sequence yet, and the phone never wakes from deep. Pass mem_sleep_default=s2idle, as the Pixel 7 Pro does, so a suspend that names no state stays in s2idle. Tested on a Pixel 7 from slot B (7.3.0-rc6): /sys/power/mem_sleep reads "[s2idle] deep". Suggested-by: Derek Ross Assisted-by: Claude Opus 5.5 Signed-off-by: Alejandro Garcia --- arch/arm64/boot/dts/exynos/google/gs201-panther.dts | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/arm64/boot/dts/exynos/google/gs201-panther.dts b/arch/arm64/boot/dts/exynos/google/gs201-panther.dts index fa2d96a760..1c36f61120 100644 --- a/arch/arm64/boot/dts/exynos/google/gs201-panther.dts +++ b/arch/arm64/boot/dts/exynos/google/gs201-panther.dts @@ -26,7 +26,7 @@ chosen { /* ABL requires bootargs to exist; it appends its own after these. */ - bootargs = "console=tty0 panic=10 clk_ignore_unused pd_ignore_unused rdinit=/init omamobile.ufs-probe"; + bootargs = "console=tty0 panic=10 clk_ignore_unused pd_ignore_unused rdinit=/init omamobile.ufs-probe mem_sleep_default=s2idle"; #address-cells = <2>; #size-cells = <1>; ranges; From 3d9a2f384bbfc9be35994abfd2951f4d13e1af83 Mon Sep 17 00:00:00 2001 From: Alejandro Garcia Date: Wed, 28 Oct 2026 22:28:09 -0700 Subject: [PATCH 4/5] arm64: dts: exynos: google: gs201-panther: pin LDO25M at 1.8 V LDO25M is the touch controller's VDD. It has no voltage here, so the regulator core leaves it at whatever the PMIC holds. Google's common gs201-pmic.dtsi constrains it to 1.6-1.95 V, panther's gs201-panther-pmic.dtsi doesn't narrow that, and ABL leaves it at 1.8 V, which vdd-ts reads on the phone. Fix it at 1.8 V, as the Pixel Fold describes its own LDO25M, so the touch controller gets stock's voltage whatever the PMIC held before. Tested on a Pixel 7 from slot B (7.3.0-rc6): vdd-ts reads 1.8 V, with the touch controller as its only user, and the controller probes as before. Suggested-by: Derek Ross Assisted-by: Claude Opus 5.5 Signed-off-by: Alejandro Garcia --- arch/arm64/boot/dts/exynos/google/gs201-panther.dts | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/arch/arm64/boot/dts/exynos/google/gs201-panther.dts b/arch/arm64/boot/dts/exynos/google/gs201-panther.dts index 1c36f61120..27e20f56b6 100644 --- a/arch/arm64/boot/dts/exynos/google/gs201-panther.dts +++ b/arch/arm64/boot/dts/exynos/google/gs201-panther.dts @@ -131,9 +131,11 @@ status = "disabled"; regulators { - /* No voltage: the PMIC keeps the 1.8 V it holds. */ + /* Stock's 1.8 V, which ABL leaves programmed */ ldo25m: ldo25m { regulator-name = "vdd-ts"; + regulator-min-microvolt = <1800000>; + regulator-max-microvolt = <1800000>; }; /* From ace1ba57fbe7bf9b812a9f23757b6ea60ef0bc3c Mon Sep 17 00:00:00 2001 From: Alejandro Garcia Date: Wed, 28 Oct 2026 22:28:37 -0700 Subject: [PATCH 5/5] arm64: dts: exynos: google: gs201-panther: add the touchscreen Describe the FocalTech FT3658 on USI0 SPI, with the focaltech,ft3658 binding: the Pixel 7 Pro's S3908 wiring (chip select gpp20-3, interrupt gpa7-0 falling, reset gpp23-2, gs201-pinctrl.dtsi's ts_irq and ts_reset), 10 MHz, and the 1080x2400 panel. Enable the main PMIC, whose only regulators here are the controller's rails: LDO25M as VDD and LDO26M as AVDD. LDO26M's 3.0 V is Google's own value for this phone: gs201-panther-pmic.dtsi in kernel/devices/google/pantah sets regulator-max-microvolt = <3000000> on m_ldo26_reg ("Panther touch controller requires 3.0v typ"). Tested on a Pixel 7 from slot B (7.3.0-rc6), with the GPU, the haptics and the driver's pending DMA-safe buffer and fsleep() fixes: the ft3658 module loads at boot and reads chip id 0x56, firmware 0x16; vdd-ts reads 1.8 V and avdd-ts 3.0 V; touches across the panel, the four corners included, drive Hyprland and unlock the PIN screen, with no SPI or CRC errors. The GPU and the haptics keep working. Assisted-by: Claude Opus 5.5 Signed-off-by: Alejandro Garcia --- .../boot/dts/exynos/google/gs201-panther.dts | 36 +++++++++++++++++-- 1 file changed, 33 insertions(+), 3 deletions(-) diff --git a/arch/arm64/boot/dts/exynos/google/gs201-panther.dts b/arch/arm64/boot/dts/exynos/google/gs201-panther.dts index 27e20f56b6..8c42276bf2 100644 --- a/arch/arm64/boot/dts/exynos/google/gs201-panther.dts +++ b/arch/arm64/boot/dts/exynos/google/gs201-panther.dts @@ -4,8 +4,8 @@ * * USB (NCM + ACM), the cluster watchdogs from gs201.dtsi, a * simple-framebuffer on the buffer ABL leaves DPP0 scanning out, UFS, the - * three keys, the touch rails on the main PMIC, the GPU and the haptics. - * The panel driver and touch stay disabled. + * three keys, the touchscreen with its rails on the main PMIC, the GPU and + * the haptics. The panel driver stays disabled. */ /dts-v1/; @@ -128,7 +128,6 @@ interrupts = ; google,vgpio2ap-sysreg = <&sysreg_vgpio2ap>; wakeup-source; - status = "disabled"; regulators { /* Stock's 1.8 V, which ABL leaves programmed */ @@ -225,3 +224,34 @@ cirrus,lra-redc-micro-ohms = <13000000>; }; }; + +/* + * Touchscreen: a FocalTech FT3658 on USI0 SPI, wired as the Pixel 7 Pro's + * S3908 (chip select gpp20-3, interrupt gpa7-0, reset gpp23-2). + */ +&usi0 { + samsung,mode = ; + status = "okay"; +}; + +&spi_0 { + pinctrl-0 = <&spi0_bus &spi0_miso &spi0_cs_gpio>; + cs-gpios = <&gpp20 3 GPIO_ACTIVE_LOW>; + num-cs = <1>; + status = "okay"; + + touchscreen@0 { + compatible = "focaltech,ft3658"; + reg = <0>; + spi-max-frequency = <10000000>; + interrupt-parent = <&gpa7>; + interrupts = <0 IRQ_TYPE_EDGE_FALLING>; + reset-gpios = <&gpp23 2 GPIO_ACTIVE_LOW>; + vdd-supply = <&ldo25m>; + avdd-supply = <&ldo26m>; + pinctrl-0 = <&ts_irq &ts_reset>; + pinctrl-names = "default"; + touchscreen-size-x = <1080>; + touchscreen-size-y = <2400>; + }; +};