From 1267286d613b4dc9e336966be4b98829c5b90b17 Mon Sep 17 00:00:00 2001 From: W4HO <87742609+W4HO-ham@users.noreply.github.com> Date: Sat, 31 Oct 2026 15:35:22 -0647 Subject: [PATCH] arm64: dts: exynos: google: zumapro-tegu: Add the fingerprint sensor Describe the Pixel 9a's Goodix under-display fingerprint sensor as Google's GPL zumapro-tegu-udfps.dtsi has it: the event line on gpa7-6 (EINT, rising edge) and the reset on gpp1-0 (active low, its previous state kept in power-down). Its SPI bus belongs to the secure world, so the node is on no bus. The pin state touches only gpp1-0; the touchscreen's reset is gpp1-1 in the same bank. Its 3.3 V, S2MPG15 LDO15S, is always on, as on stock. It is off at hand-off, and until it is on the trusted app reads chip id 0. This adds the sub-PMIC and gpa7's interrupts (GIC SPI 36-43, as stock). LDO15S's selector is firmware-owned (the S2MPG15 LDOs have no voltage setting) and reads stock's 3.3 V (1.8 V + 60 x 25 mV) at hand-off, so min = max writes nothing: it records stock's value, and the core refuses the rail if it ever reads anything else. gpp1-0's drive is stock's X1 (0). Tested on the 9a with this tree (7.3.0-rc6-omamobile-push1-gb533af3f1cbc, before the 3.3 V constraint and the drive line): goodix-fp binds from the device tree on gpa7-6 with /dev/goodix_fp, and touch, keys and haptics are unaffected. Matching through the trusted app ran on the integration tree, which has the same node, and with no voltage constraint there the rail reads 3300000 uV. Signed-off-by: W4HO <87742609+W4HO-ham@users.noreply.github.com> --- .../boot/dts/exynos/google/zumapro-tegu.dts | 55 ++++++++++++++++++- 1 file changed, 53 insertions(+), 2 deletions(-) diff --git a/arch/arm64/boot/dts/exynos/google/zumapro-tegu.dts b/arch/arm64/boot/dts/exynos/google/zumapro-tegu.dts index f66e006084..742e7ff231 100644 --- a/arch/arm64/boot/dts/exynos/google/zumapro-tegu.dts +++ b/arch/arm64/boot/dts/exynos/google/zumapro-tegu.dts @@ -53,6 +53,23 @@ }; }; + /* + * The Goodix under-display fingerprint sensor. Its SPI bus belongs to + * the secure world (the trusted app drives it), so the node sits on + * no bus and describes only the lines the AP drives: the event line + * on gpa7-6 and the reset on gpp1-0, as Google's GPL + * zumapro-tegu-udfps.dtsi. Its 3.3 V, S2MPG15 LDO15S, is always on, so + * the node has no supply. + */ + fingerprint { + compatible = "goodix,g7-udfps"; + interrupt-parent = <&gpa7>; + interrupts = <6 IRQ_TYPE_EDGE_RISING>; + reset-gpios = <&gpp1 0 GPIO_ACTIVE_LOW>; + pinctrl-names = "default"; + pinctrl-0 = <&fp_irq &fp_rst>; + }; + gpio-keys { compatible = "gpio-keys"; @@ -196,7 +213,7 @@ }; }; - pmic-2 { + pmic_sub: pmic-2 { compatible = "samsung,s2mpg15-pmic"; regulators { @@ -207,6 +224,21 @@ sensor_1v8: ldo7s { regulator-name = "sensor-1v8"; }; + + /* + * The fingerprint sensor's 3.3 V, always on as on stock + * (Google's GPL zumapro-tegu-udfps.dtsi). Off at hand-off: + * the trusted app reads chip id 0 until it is on. The + * selector is firmware-owned and reads 3.3 V at hand-off; + * min = max records stock's value, and makes the core + * refuse the rail if it ever reads anything else. + */ + udfps_3v3: ldo15s { + regulator-name = "udfps-3v3"; + regulator-min-microvolt = <3300000>; + regulator-max-microvolt = <3300000>; + regulator-always-on; + }; }; }; }; @@ -362,7 +394,10 @@ ; }; -/* The NFC controller's interrupt (gpa7-5). */ +/* + * The NFC controller's interrupt (gpa7-5) and the fingerprint sensor's + * event line (gpa7-6). + */ &gpa7 { interrupt-controller; #interrupt-cells = <2>; @@ -539,6 +574,11 @@ &pinctrl_alive { status = "okay"; + fp_irq: fp-irq-pins { + samsung,pins = "gpa7-6"; + samsung,pin-function = ; + }; + usb_pd_irq: usb-pd-irq-pins { samsung,pins = "gpa8-3"; samsung,pin-function = ; @@ -590,6 +630,17 @@ &pinctrl_peric0 { status = "okay"; + /* Only pin 0: the touchscreen's reset is gpp1-1 in the same bank. */ + fp_rst: fp-rst-pins { + samsung,pins = "gpp1-0"; + samsung,pin-function = ; + samsung,pin-pud = ; + samsung,pin-con-pdn = ; + samsung,pin-pud-pdn = ; + /* ZUMA_PIN_DRV_X1 in Google's header: 0 in stock's built DTBO */ + samsung,pin-drv = <0>; + }; + hsi2c4_bus: hsi2c4-bus-pins { samsung,pins = "gpp8-0", "gpp8-1"; samsung,pin-function = ;