Repository navigation
Conversation
With the zumapro PCIe channel-1 host and the Wi-Fi node in the device tree, the graphics start loads pcie_zumapro, waits for the BCM4383 on the link, then loads brcmfmac and waits for its interface, as hang-safe steps after NFC.
… a Wi-Fi hang keeps the display off too Review of derekross#238: the graphics start's one marker covers every step, so a hang in the Wi-Fi step leaves the GPU and the display off on the next boot as well.
…le the palmtop sleeps With PSCI core power-down allowed in s2idle, the S2MPG14 raised an event that hadn't happened about a second in and ended every sleep; with WFI only, a sleep lasts until its alarm. A sleep hook disables the cpuidle sleep states for the sleep and restores them after.
|
Withdrawn: the finding behind it was my measurement error. I took each sleep's length from With core power-down disabled, the dmesg deltas grew to the alarm time because with WFI only the s2idle loop doesn't freeze the tick, so timekeeping keeps running. That makes the sleep shallower, not fixed. So this hook would cost power for nothing, and I'm closing it. The SLEEP-PLAN paragraphs that claimed one-second sleeps (merged with #244) get a correction in #256, and the AGENTS correction you asked for isn't needed. Sorry for the noise. |
The one-second sleeps were dmesg deltas, and the kernel log's clock stops while the SoC is suspended. The RTC shows full-length sleeps, so the core power-down hook (derekross#255) is withdrawn, and S1's wake counts stand.
On the Pixel 9a, every s2idle sleep ended about a second in. This makes them last until their wake.
What was happening. With the CPUs allowed into core power-down (their only deeper cpuidle state,
cpu-*-sleep, PSCI core power-down), the S2MPG14 raised an event that hadn't happened about a second afterPM: suspend entry, and that woke the palmtop. A bring-up module read the PMIC's INT1-INT5 insuspend_noirqandresume_noirq(reads only):With an alarm set, alarm 0 latched within 60 ms whether it was due in 30 or 120 s; awake, the same alarm fires on time. With none set, a power-key release nobody made did the same. With core power-down disabled on all eight CPUs (WFI only), a 30 s sleep lasted until its alarm. Our idle states match stock's (the same
c2states andarm,psci-suspend-param = <0x10000>); stock also has Samsung'sexynos-cpupmcluster power-down and SICD, coordinated with the APM, which mainline doesn't have. That the false events come from there is my inference, not a measurement. Details are in SLEEP-PLAN S1 (#244).The change. A sleep hook,
omamobile-tegu-cpuidle, disables every*-sleepcpuidle state before the sleep and puts each back as it was afterwards (a state already off by hand stays off).test/cpuidle-hookchecks this in a scratch root, andtest/allruns it.Tested on the palmtop (
7.3.0-rc6-omamobile-tegu-s2mpg15-m1-g991042e2eff3-dirty, this branch built and installed withtools/phone-install-package): tensystemctl suspendcycles with a 60 s RTC alarm, the hook doing the switch:PM: suspend entrytoexit) and woke on IRQ 56, the alarm.suspend_statswent from 6 to 15 successes with 0 failures.Before the hook, every sleep in the same setup lasted 0.6-1.6 s.
What this doesn't settle: the screen stays lit through a sleep started with
systemctl suspend(the shell blanks it on its own sleep path), so there's no drain figure yet. The rare hang on wake (one in 21 before) also needs a longer run now that sleeps really last. This branch sits on #238 (0.2.4), so it's 0.2.5.tools/pr-checkand the package tests pass.