From ab89dd3e8b83fc643741db949c8a8feb89c0237a Mon Sep 17 00:00:00 2001 From: Alejandro Garcia Date: Sat, 31 Oct 2026 14:07:18 -0700 Subject: [PATCH 1/2] arm64: dts: exynos: google: gs201-panther: pull up the touch interrupt Google's panther touch file sets a pull-up on the FT3658's interrupt pin, gpa7-0 (&ts_irq in gs201-panther-touch.dtsi, EXYNOS_PIN_PULL_UP), and the Pixel 7's live device tree has it (ts-irq, samsung,pin-pud = 3). The shared gs201 group has no pull, as the Pixel 7 Pro wants, so override it in this board file only. Touch worked without it, since the controller drives the line; this matches stock. Tested on a Pixel 7 from slot B (7.3.0-rc6), together with the next patch: the live device tree has samsung,pin-pud = 3 in ts-irq-pins, pinctrl reports gpa7-0 in that group, and the controller probes (chip id 0x56, firmware 0x16) and reports touches across the panel. Suggested-by: Derek Ross Assisted-by: Claude Opus 5.5 Signed-off-by: Alejandro Garcia --- arch/arm64/boot/dts/exynos/google/gs201-panther.dts | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/arch/arm64/boot/dts/exynos/google/gs201-panther.dts b/arch/arm64/boot/dts/exynos/google/gs201-panther.dts index 8c42276bf2..b55b871385 100644 --- a/arch/arm64/boot/dts/exynos/google/gs201-panther.dts +++ b/arch/arm64/boot/dts/exynos/google/gs201-panther.dts @@ -229,6 +229,11 @@ * 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). */ +&ts_irq { + /* Stock pulls the interrupt line up on this phone, not on the 7 Pro */ + samsung,pin-pud = ; +}; + &usi0 { samsung,mode = ; status = "okay"; From fd864fc214b5b57caf6ac6abe2195889ebaa0057 Mon Sep 17 00:00:00 2001 From: Alejandro Garcia Date: Sat, 31 Oct 2026 14:07:18 -0700 Subject: [PATCH 2/2] arm64: dts: exynos: google: gs201-panther: wait 1 us after the touch chip select Stock waits 1 us from asserting the FT3658's chip select to the first clock: cs-clock-delay = <1> in the touch node's controller-data, in Google's gs201-panther-touch.dtsi and in the Pixel 7's live device tree. Upstream spells it spi-cs-setup-delay-ns, which the SPI core applies after it drives a GPIO chip select, as this one is. Tested on a Pixel 7 from slot B (7.3.0-rc6), together with the previous patch: the touch node has spi-cs-setup-delay-ns = 1000 in the live device tree, and the controller probes (chip id 0x56, firmware 0x16) and reports touches across the panel with no CRC errors. 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, 2 insertions(+) diff --git a/arch/arm64/boot/dts/exynos/google/gs201-panther.dts b/arch/arm64/boot/dts/exynos/google/gs201-panther.dts index b55b871385..8763b7b5bb 100644 --- a/arch/arm64/boot/dts/exynos/google/gs201-panther.dts +++ b/arch/arm64/boot/dts/exynos/google/gs201-panther.dts @@ -249,6 +249,8 @@ compatible = "focaltech,ft3658"; reg = <0>; spi-max-frequency = <10000000>; + /* Stock's cs-clock-delay = <1>: 1 us from chip select to the clock */ + spi-cs-setup-delay-ns = <1000>; interrupt-parent = <&gpa7>; interrupts = <0 IRQ_TYPE_EDGE_FALLING>; reset-gpios = <&gpp23 2 GPIO_ACTIVE_LOW>;