Repository navigation
Pixel 8a (akita): buttons, and suspend-to-idle by default - #238
Conversation
The Pixel 8a's volume and power keys are wired as on the Pixel 8 Pro: volume down on gpa4-1, volume up on gpa6-2 and power on gpa4-0, all active low and wake sources (Google's zuma-common.dtsi; the stock phone's /proc/interrupts lists the same three gpio-keys lines). Add the same gpio-keys node as zuma-husky, with zuma-pinctrl.dtsi's key pins. Without it the power key is not an input device, so nothing on the phone can wake the screen once the lock has blanked it. Tested on a Pixel 8a from slot B (7.3.0-rc6): gpio-keys registers as an input device with the three keys; one short press of each raises its interrupt twice (press and release), and a short Power press wakes the screen through the session's lock without powering the phone off. Assisted-by: Claude Opus 5.5 Signed-off-by: DarekM <149845949+aninmucek@users.noreply.github.com>
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 8a. Linux has no zuma sleep sequence yet, so a deep suspend would not wake. Pass mem_sleep_default=s2idle, as the Pixel 7 Pro and the Pixel 7 do, so a suspend that names no state stays in s2idle. The omamobile-device-akita package already asks systemd for s2idle; this covers anything that writes "mem" directly. Tested on a Pixel 8a from slot B (7.3.0-rc6): /proc/cmdline carries mem_sleep_default=s2idle and /sys/power/mem_sleep reads "[s2idle] deep". Suggested-by: Derek Ross <derekross@gmail.com> Assisted-by: Claude Opus 5.5 Signed-off-by: DarekM <149845949+aninmucek@users.noreply.github.com>
|
Thanks, @aninmucek. Both commits are in good shape and I'll merge them. What I checked: the change is confined to Two small things:
Your touch question. Yes, I'd take
Thanks for not powering the chip at 3.3 V while this was open. That was the right call. |
The Pixel 8a's buttons, and suspend-to-idle as the default sleep, on today's
omamobile. These are the first two steps of akita's M3 (input). Touch follows once the supply question below is settled.gpa4-1,gpa6-2andgpa4-0, active low, all wake sources.zuma-common.dtsihas them, and the stock phone's/proc/interruptslists the same threegpio-keyslines.gpio-keysnode as it is, withzuma-pinctrl.dtsi's key pins.mem_sleep_default=s2idlein the bootargs, as on the 7 Pro and the 7. This is your suggestion from Pixel 8a (akita): enable UFS, as on the Pixel 8 Pro #206's review: under Arch,/sys/power/mem_sleepreads2idle [deep](BRINGUP-M2, M2.6).Tested on a Pixel 8a from slot B (7.3.0-rc6, these two commits on
253208c11):gpio-keysis an input device with all three keys./sys/power/mem_sleepreads[s2idle] deep.exynos-clkoutlines are gone from the boot log.tools/phone-smokefrom omarchy-mobile's main reads buttons ok, with 2 known error lines and 0 new.tools/kernel-pr-check --build OUT --merge origin/omamobile, with the dtschema validator, passes everything:253208c11;checkpatch --strictwith no errors. Its one warning is the bootargs line's length (229 columns). It was already 204 before this, and a bootargs string can't be wrapped;W=1and passdtbs_check, with no new warnings.A question for the next step (touch). The 8a's touchscreen is a Goodix GT9895, the 7a's chip. Its supplies are the S2MPG14's LDO25M (1.8 V) and LDO4M, and the stock phone runs LDO4M at 3.0 V. With LDO4M fixed at 3.0 V in the board file, the regulator probe fails:
touch-avdd: failed to apply 3000000-3000000uV constraint: -EINVAL.That's because the S2MPG14 LDO ops (
5e4cda3a7, from the 9a work) read the voltage selector but deliberately don't set it. A test boot with the driver's whole range, no consumer andregulator_ignore_unusedread what ABL leaves on this phone:So with today's driver, touch would get 3.3 V where stock uses 3.0 V. The 7a runs the same chip at 3.0 V, and the S2MPG12's LDO ops there have
set_voltage_sel.Would you take a small change that adds
set_voltage_sel(regulator_set_voltage_sel_regmap) to the S2MPG14 LDO ops? With fixed min = max constraints, the core would then set stock's 3.0 V before anything enables the rail. As far as I can see it changes nothing on the other boards:Or is there a reason to keep the selectors firmware-owned that I'm missing? I won't power the touch chip until this is settled.
tools/phone-smokereport (this PR's kernel, omarchy-mobile main6a9251f)phone-smoke: akita
Kernel
7.3.0-rc6-omamobile-push1-g23120efb6488, tools at6a9251f, 2026-11-10T16:07Z.Packages: hyprland 0.57.0-3.2, libcamera 0.7.2-4.23, mesa 1:26.2.4-1.4, omacam 0.3.3-1, omamessages 0.2.2-1, omamobile-apps 0.2.2-1, omamobile-device-akita 0.1.1-1, omamobile-firstboot 0.1.3-1, omamobile-keyring 20261026-1, omamobile-mirror 0.1.1-1, omamobile-omarchy 0.1.38-1, omamobile-owl-widgets 0.1.2-1, omamobile-shell 0.2.108-1, omamobile-voice 0.1.0-1, omaphone 0.2.3-1, omarchy 4.0.6-1, omatel-agent 0.2.4-2, quickshell 0.3.2.r7.g2b4501a-1
🤖 Generated with Claude Code