From 8b32655f593bc4e7f75a7a9c9a5c9138cc1b3a7b Mon Sep 17 00:00:00 2001 From: Alejandro Garcia Date: Tue, 27 Oct 2026 21:02:25 -0700 Subject: [PATCH 1/5] dt-bindings: arm: google: Add Pixel 7 (panther) The Pixel 7 (panther) is a gs201 (Tensor G2) board like the Pixel 7 Pro, Pixel Fold and Pixel 7a. Add its compatible to the gs201 board list. Assisted-by: Claude Opus 5.5 Signed-off-by: Alejandro Garcia --- Documentation/devicetree/bindings/arm/google.yaml | 1 + 1 file changed, 1 insertion(+) diff --git a/Documentation/devicetree/bindings/arm/google.yaml b/Documentation/devicetree/bindings/arm/google.yaml index d7b7eed970..a052732758 100644 --- a/Documentation/devicetree/bindings/arm/google.yaml +++ b/Documentation/devicetree/bindings/arm/google.yaml @@ -46,6 +46,7 @@ properties: - google,gs201-cheetah - google,gs201-felix - google,gs201-lynx + - google,gs201-panther - const: google,gs201 - description: Google Tensor G3 (zuma) boards items: From c00493acd027d73d94c259227a389ef5ef99441d Mon Sep 17 00:00:00 2001 From: Alejandro Garcia Date: Tue, 27 Oct 2026 21:03:15 -0700 Subject: [PATCH 2/5] arm64: dts: exynos: google: Add Pixel 7 (panther) first-light board Add a first-light board file for the Pixel 7: USB (NCM and ACM gadget), the cluster watchdogs from gs201.dtsi, and a simple-framebuffer on the buffer ABL leaves the panel scanning out. UFS, the panel, touch and the GPU stay disabled. panther has the standard package of gs201: stock reports ro.boot.hw.soc.pkg_mode 0 and soc_id 0x09855001 in its live tree, so this DTB matches on soc_id as cheetah's does. ABL accepted it. ABL leaves DPP0 scanning 0xfac00000 (RDMA_BASEADDR_Y8, read on the phone) for the 1080x2400 sdc-s6e3fc3 panel; the buffer is reserved and described as a simple-framebuffer. ramoops uses stock's address and layout, so a log from this kernel can be read after a warm reboot into stock on slot A. The board dtbo for ABL (board_id 0x30406, board_rev 0x10000), the display trigger and the image packing live in the omarchy-mobile repository (device/panther). Tested on a Pixel 7 (bootloader cloudripper-17.0-15902555) from slot B: the kernel boots, both watchdogs are stopped at probe, the console shows on the panel, and SSH over the USB NCM gadget works. Assisted-by: Claude Opus 5.5 Signed-off-by: Alejandro Garcia --- arch/arm64/boot/dts/exynos/google/Makefile | 2 + .../boot/dts/exynos/google/gs201-panther.dts | 78 +++++++++++++++++++ 2 files changed, 80 insertions(+) create mode 100644 arch/arm64/boot/dts/exynos/google/gs201-panther.dts diff --git a/arch/arm64/boot/dts/exynos/google/Makefile b/arch/arm64/boot/dts/exynos/google/Makefile index 0ecac5f36d..35e5867932 100644 --- a/arch/arm64/boot/dts/exynos/google/Makefile +++ b/arch/arm64/boot/dts/exynos/google/Makefile @@ -6,6 +6,7 @@ dtb-$(CONFIG_ARCH_EXYNOS) += \ gs201-cheetah.dtb \ gs201-felix.dtb \ gs201-lynx.dtb \ + gs201-panther.dtb \ zuma-husky.dtb # ABL applies board overlays, so keep symbols for labels @@ -14,4 +15,5 @@ DTC_FLAGS_gs101-raven += -@ DTC_FLAGS_gs201-cheetah += -@ DTC_FLAGS_gs201-felix += -@ DTC_FLAGS_gs201-lynx += -@ +DTC_FLAGS_gs201-panther += -@ DTC_FLAGS_zuma-husky += -@ diff --git a/arch/arm64/boot/dts/exynos/google/gs201-panther.dts b/arch/arm64/boot/dts/exynos/google/gs201-panther.dts new file mode 100644 index 0000000000..936a872410 --- /dev/null +++ b/arch/arm64/boot/dts/exynos/google/gs201-panther.dts @@ -0,0 +1,78 @@ +// SPDX-License-Identifier: GPL-2.0-only +/* + * Google Pixel 7 (panther) - first-light board file. + * + * USB (NCM + ACM), the cluster watchdogs from gs201.dtsi and a + * simple-framebuffer on the buffer ABL leaves DPP0 scanning out. The panel + * driver, touch, the GPU and UFS stay disabled. + */ + +/dts-v1/; + +#include "gs201.dtsi" + +/ { + model = "Google Pixel 7"; + compatible = "google,gs201-panther", "google,gs201"; + + /* + * ABL's base-DTB match: product id 0x09855000 | major revision (B0 is + * 1). Stock reports pkg_mode 0 and soc_id 0x09855001 in its live tree. + */ + soc_id = <0x09855001 0x0>; + + 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"; + #address-cells = <2>; + #size-cells = <1>; + ranges; + + /* + * ABL leaves DECON0 -> DSIM0 -> panel (sdc-s6e3fc3) running in + * command mode with DPP0 scanning 0xfac00000 (RDMA_BASEADDR_Y8, + * read on this phone). There is no panel driver, so no panel + * phandle; the size comes from this node. + */ + framebuffer0: framebuffer@fac00000 { + compatible = "simple-framebuffer"; + reg = <0x0 0xfac00000 (1080 * 2400 * 4)>; + memory-region = <&cont_splash_mem>; + width = <1080>; + height = <2400>; + stride = <(1080 * 4)>; + format = "a8r8g8b8"; + }; + }; + + reserved-memory { + #address-cells = <2>; + #size-cells = <1>; + ranges; + + /* + * Stock's region and layout (ramoops_mem@fd3ff000 in its live + * tree), so a log from this kernel can be read after a warm + * reboot into slot A. + */ + ramoops@fd3ff000 { + compatible = "ramoops"; + reg = <0x0 0xfd3ff000 0x400000>; + console-size = <0x200000>; + pmsg-size = <0x200000>; + }; + + cont_splash_mem: splash@fac00000 { + reg = <0x0 0xfac00000 (1080 * 2400 * 4)>; + no-map; + }; + }; +}; + +&usbdrd31_phy { + status = "okay"; +}; + +&usb_dwc3 { + status = "okay"; +}; From 952608689eb474404a579419056d6b61a40f0f46 Mon Sep 17 00:00:00 2001 From: Alejandro Garcia Date: Tue, 27 Oct 2026 21:03:34 -0700 Subject: [PATCH 3/5] arm64: dts: exynos: google: gs201-panther: enable UFS Enable the UFS host and its PHY. VCC is the fixed always-on regulator cheetah and lynx use: stock drives it from gpp0-1 (boot-on), and the bootloader leaves it on. omamobile.ufs-probe tells the omarchy-mobile initramfs to load the UFS drivers and apply its storage guard, which leaves only slot B's boot images and userdata writable. Tested on a Pixel 7 from slot B: four LUNs and 55 partitions enumerate, with the same names and numbers as stock's by-name map, and the guard leaves sda20-24 (slot B's boot images) and sda31 (userdata) read-write. The Arch root on userdata boots from it. Assisted-by: Claude Opus 5.5 Signed-off-by: Alejandro Garcia --- .../boot/dts/exynos/google/gs201-panther.dts | 29 ++++++++++++++++--- 1 file changed, 25 insertions(+), 4 deletions(-) diff --git a/arch/arm64/boot/dts/exynos/google/gs201-panther.dts b/arch/arm64/boot/dts/exynos/google/gs201-panther.dts index 936a872410..c57880a457 100644 --- a/arch/arm64/boot/dts/exynos/google/gs201-panther.dts +++ b/arch/arm64/boot/dts/exynos/google/gs201-panther.dts @@ -2,9 +2,9 @@ /* * Google Pixel 7 (panther) - first-light board file. * - * USB (NCM + ACM), the cluster watchdogs from gs201.dtsi and a - * simple-framebuffer on the buffer ABL leaves DPP0 scanning out. The panel - * driver, touch, the GPU and UFS stay disabled. + * USB (NCM + ACM), the cluster watchdogs from gs201.dtsi, a + * simple-framebuffer on the buffer ABL leaves DPP0 scanning out, and UFS. + * The panel driver, touch and the GPU stay disabled. */ /dts-v1/; @@ -23,7 +23,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"; + bootargs = "console=tty0 panic=10 clk_ignore_unused pd_ignore_unused rdinit=/init omamobile.ufs-probe"; #address-cells = <2>; #size-cells = <1>; ranges; @@ -45,6 +45,18 @@ }; }; + /* + * UFS VCC. Stock drives it from GPIO gpp0-1 (boot-on), as on + * cheetah; there is no gs201 GPIO driver yet, so describe it as + * always on, as the bootloader leaves it. + */ + ufs_0_fixed_vcc_reg: regulator-ufs-vcc { + compatible = "regulator-fixed"; + regulator-name = "ufs-vcc"; + regulator-always-on; + regulator-boot-on; + }; + reserved-memory { #address-cells = <2>; #size-cells = <1>; @@ -76,3 +88,12 @@ &usb_dwc3 { status = "okay"; }; + +&ufs_0 { + vcc-supply = <&ufs_0_fixed_vcc_reg>; + status = "okay"; +}; + +&ufs_0_phy { + status = "okay"; +}; From f48fecd8d1b9fd3b196c8b45d9e019a69cf76771 Mon Sep 17 00:00:00 2001 From: Alejandro Garcia Date: Tue, 27 Oct 2026 21:03:51 -0700 Subject: [PATCH 4/5] arm64: dts: exynos: google: gs201-panther: add the volume and power keys Add gpio-keys for volume down (gpa10-1), volume up (gpa8-5) and power (gpa10-0, the S2MPG12 PWRONB line, also wired to the SoC). The node is cheetah's, with the same pins and pin states, which Google's gs201-common.dtsi gives every gs201 board. It is added enabled, as the Pixel Fold's volume keys were, since it passed on this phone. Tested on a Pixel 7 from slot B: each key reports press and release on the gpio-keys input device, and the power key wakes the screen. Assisted-by: Claude Opus 5.5 Signed-off-by: Alejandro Garcia --- .../boot/dts/exynos/google/gs201-panther.dts | 37 ++++++++++++++++++- 1 file changed, 35 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 c57880a457..6023ee8b51 100644 --- a/arch/arm64/boot/dts/exynos/google/gs201-panther.dts +++ b/arch/arm64/boot/dts/exynos/google/gs201-panther.dts @@ -3,12 +3,13 @@ * Google Pixel 7 (panther) - first-light board file. * * USB (NCM + ACM), the cluster watchdogs from gs201.dtsi, a - * simple-framebuffer on the buffer ABL leaves DPP0 scanning out, and UFS. - * The panel driver, touch and the GPU stay disabled. + * simple-framebuffer on the buffer ABL leaves DPP0 scanning out, UFS and + * the three keys. The panel driver, touch and the GPU stay disabled. */ /dts-v1/; +#include #include "gs201.dtsi" / { @@ -45,6 +46,38 @@ }; }; + /* The same pins as cheetah's (Google's gs201-common.dtsi). */ + gpio-keys { + compatible = "gpio-keys"; + pinctrl-0 = <&key_voldown>, <&key_volup>, <&key_power>; + pinctrl-names = "default"; + + button-vol-down { + label = "KEY_VOLUMEDOWN"; + linux,code = ; + gpios = <&gpa10 1 GPIO_ACTIVE_LOW>; + wakeup-source; + }; + + button-vol-up { + label = "KEY_VOLUMEUP"; + linux,code = ; + gpios = <&gpa8 5 GPIO_ACTIVE_LOW>; + wakeup-source; + }; + + /* + * PMIC_PWRON_OD_L: the S2MPG12 PWRONB line, also wired to the + * SoC. The PMIC's own long-press reset is unaffected. + */ + button-power { + label = "KEY_POWER"; + linux,code = ; + gpios = <&gpa10 0 GPIO_ACTIVE_LOW>; + wakeup-source; + }; + }; + /* * UFS VCC. Stock drives it from GPIO gpp0-1 (boot-on), as on * cheetah; there is no gs201 GPIO driver yet, so describe it as From e7bae522b79282e8ca5583574d683a1ec3d9d456 Mon Sep 17 00:00:00 2001 From: Alejandro Garcia Date: Tue, 27 Oct 2026 21:04:27 -0700 Subject: [PATCH 5/5] arm64: dts: exynos: google: gs201-panther: describe the touch rails LDO25M and LDO26M on the main PMIC (S2MPG12) are the supplies of the FocalTech FT3658 touch controller, its VDD and AVDD; nothing else on the stock board uses them. Stock constrains them to 1.6-1.95 V and 2.5-3.0 V. Describe those two rails under pmic-1, as the Pixel Fold does. The sub-PMIC is not described. Leave the node disabled: it is switched on with the touch controller. ABL leaves both rails off, LDO25M programmed at 1.8 V and LDO26M at 3.3 V, above stock's range. LDO25M gets no voltage, so the PMIC keeps its 1.8 V. LDO26M is fixed at 3.0 V, the top of stock's range: stock's regulator core moves it there before the touch driver switches it on, and this tree's does the same while the rail is still off. Tested on a Pixel 7 from slot B, with the node enabled: the S2MPG12 regulators register; vdd-ts reads 1.8 V and avdd-ts 3.0 V, both off, and no other LDO changes. With the touch controller described as well (not in this series), both rails come up in order and the controller answers. Assisted-by: Claude Opus 5.5 Signed-off-by: Alejandro Garcia --- .../boot/dts/exynos/google/gs201-panther.dts | 39 ++++++++++++++++++- 1 file changed, 37 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 6023ee8b51..d3e061a5b6 100644 --- a/arch/arm64/boot/dts/exynos/google/gs201-panther.dts +++ b/arch/arm64/boot/dts/exynos/google/gs201-panther.dts @@ -3,8 +3,9 @@ * Google Pixel 7 (panther) - first-light board file. * * USB (NCM + ACM), the cluster watchdogs from gs201.dtsi, a - * simple-framebuffer on the buffer ABL leaves DPP0 scanning out, UFS and - * the three keys. The panel driver, touch and the GPU stay disabled. + * 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. */ /dts-v1/; @@ -114,6 +115,40 @@ }; }; +&acpm_ipc { + /* + * Main PMIC, touch rails only. LDO25M is the touch controller's VDD + * and LDO26M its AVDD; nothing else on the stock board consumes + * them. Stock constrains them to 1.6-1.95 V and 2.5-3.0 V. The sub-PMIC + * is not described. + */ + pmic-1 { + compatible = "samsung,s2mpg12-pmic"; + interrupts = ; + google,vgpio2ap-sysreg = <&sysreg_vgpio2ap>; + wakeup-source; + status = "disabled"; + + regulators { + /* No voltage: the PMIC keeps the 1.8 V it holds. */ + ldo25m: ldo25m { + regulator-name = "vdd-ts"; + }; + + /* + * ABL leaves 3.3 V programmed, above stock's range; + * stock's regulator core lowers it to 3.0 V before + * the touch driver switches it on. + */ + ldo26m: ldo26m { + regulator-name = "avdd-ts"; + regulator-min-microvolt = <3000000>; + regulator-max-microvolt = <3000000>; + }; + }; + }; +}; + &usbdrd31_phy { status = "okay"; };