Repository navigation
arm64: dts: exynos: google: zumapro-tegu: the main PMIC's interrupt, so the RTC alarm wakes the Pixel 9a - #236
Conversation
Tensor G4 (zumapro) latches the main PMIC's in-band interrupt in a VGPIO2AP system register block at 0x15090000, as gs201 does at 0x182f0000; the PMIC driver reads it through the google,vgpio2ap-sysreg phandle of the samsung,s2mpg14-pmic binding. Add the compatible, with no clock, as gs201's. Signed-off-by: W4HO <87742609+W4HO-ham@users.noreply.github.com>
The system registers that latch the main PMIC's in-band interrupt (GIC SPI 74 on this SoC), the way gs201.dtsi describes gs201's at 0x182f0000. The PMIC node points at it with google,vgpio2ap-sysreg. Signed-off-by: W4HO <87742609+W4HO-ham@users.noreply.github.com>
…rrupt
Without an interrupt the S2MPG14 driver supplies its rails but none of
the PMIC's events reach the host ("no interrupt, so no RTC alarm" at
boot), so rtc0 has no wake alarm: on the Pixel 9a a suspend with an RTC
alarm armed slept until a key was pressed (2026-11-09, on the published
tree). The interrupt is GIC SPI 74, latched by the VGPIO2AP sysreg, as
the gs201 boards' nodes have it; wakeup-source makes the alarm a wake
source, the first one for suspend.
Signed-off-by: W4HO <87742609+W4HO-ham@users.noreply.github.com>
|
Thank you, @W4HO-ham. This is the missing piece for timed wakes on the published tree, and it's put together the way I like to see it: binding first, then the SoC node, then the board. I checked the three values against Google's GPL tree rather than taking them from the description: Two small things, only if you push again; I won't hold the merge for them:
I'll merge this one first, then #237. |
On the published tree the Pixel 9a's main PMIC has no interrupt:
sec-pmic-acpm firmware:power-management:pmic-1: no interrupt, so no RTC alarmat boot,rtc0withoutwakealarm, and a suspend armed withrtcwake -m no -s 60slept until a key was pressed (2026-11-09,7.3.0-rc6-omamobile-push1-gf693b36e62ce, the publishedzumapro-tegu.dtb;rtcwake: set rtc wake alarm failed: Invalid argument). The owner's integration tree has had the interrupt since October, which is what every RTC-woken series in omarchy-mobile#409 woke on (pm_wakeup_irq56).Three commits, the way the gs201 boards describe theirs: the
google,zumapro-vgpio2ap-sysregcompatible in the sysreg binding (no clock, as gs201's), the VGPIO2AP syscon at 0x15090000 inzumapro.dtsi, andinterrupts = <GIC_SPI 74 IRQ_TYPE_LEVEL_HIGH>,google,vgpio2ap-sysregandwakeup-sourceonpmic-1inzumapro-tegu.dts. Thesamsung,s2mpg14-pmicbinding already allows all three. Nothing else changes; the Pixel 7 Pro's files aren't touched.Checks:
tools/kernel-pr-checkpasses;zumapro-tegu.dtbbuilds andCHECK_DTBS=yreports nothing on it.On the palmtop (2026-11-09):
omamobileatabcd6aac51cfwith these three commits and #224's two,7.3.0-rc6-omamobile-push1-g6c9420bfa77f, built with defconfig +kernel/configs/omamobile.config, its own modules installed. The boot has no "no RTC alarm" line andrtc0haswakealarm; 36 of 36systemctl suspendsleeps armed withrtcwake -m no -s 60woke on the alarm after 59.7 to 60.2 s,pm_wakeup_irq52 (the PMIC's interrupt) every time, no UFS error line. The same series is running again with Wi-Fi up (the build with omarchy-mobile#274's PHY option); details are on #224 and in SLEEP-PLAN on omarchy-mobile#409.