Repository navigation
Conversation
|
Thank you, and sorry this sat for two days. It's a clean pair, and the order of your runs, with thermal on its own boot before anything could raise the clocks, is how I'd want it done. I checked the caps against Google's On your two questions, and one more:
One small thing: the test kernels are |
zuma.dtsi has the three clusters' CPU levels (from the ECT) and their powers, but only zuma-husky.dts points its CPUs at them, because the tables' turbo-mode marks are the Pixel 8 Pro's battery current limiter (BCL) caps. The Pixel 8a's levels and powers are the same as stock's on this phone (its pixel-em default profile), but its BCL caps all three clusters lower: 1475, 1549 and 2147 MHz on batoilo, vdroop1, vdroop2 and smpl_gm alike (Google's zuma-akita-bcl.dtsi). With no BCL driver, mark the levels above those caps turbo-mode too (1548 and 1704 MHz little, 1572 to 1945 MHz mid, 2294 MHz big), so that with boost off the tops are 1425, 1418 and 2147 MHz, and point the CPUs at the shared tables. While every 8a cap is at or below the 8 Pro's, that gives the same levels as tables of its own would, so zuma.dtsi's comment now says a board with lower caps marks its extra levels by path. Assisted-by: LLM Signed-off-by: DarekM <149845949+aninmucek@users.noreply.github.com>
The GPU's 13 levels to 890 MHz were in zuma-husky.dts. The Pixel 8a's GPU DVFS table has the same shader rates, so move the table into zuma.dtsi, next to the CPU tables, for both boards to point at, rather than keep two copies that can drift. A board whose BCL caps the GPU lower deletes the levels above its cap by path; the comment says so. The Pixel 8 Pro's DTB is the same before and after: decompiled with dtc -s, the two are identical, phandles included; only the order of the root's nodes in the blob differs. The Pixel 8a's gains the table, unused until its GPU is enabled. Assisted-by: LLM Signed-off-by: DarekM <149845949+aninmucek@users.noreply.github.com>
The Pixel 8a's Mali-G715 is the Pixel 8 Pro's, and its stock GPU DVFS table has the same shader rates. Enable CMU_G3D and the GPU as zuma-husky.dts does, with ACPM's paired "gpu" clock and zuma.dtsi's levels. Google's zuma-akita-bcl.dtsi caps the 8a's GPU at 649 MHz on batoilo, 723 on vdroop1, 580 on vdroop2 and 649 on smpl_gm, all below the 8 Pro's 890. With no BCL driver, nothing should run above stock's caps, as with the CPUs, so delete the levels above vdroop1's 723 MHz, the highest of them, and the DTB holds that limit whatever the ACPM clock's module parameter allows. That leaves ten levels, 150 to 723 MHz. gpu-thermal throttles them. Assisted-by: LLM Signed-off-by: DarekM <149845949+aninmucek@users.noreply.github.com>
1184249 to
04945d1
Compare
|
Thank you for checking the caps. You're right about the GPU: I read only the
All three use Booted on the 8a, with omarchy-mobile#832's package now at
The earlier test kernels: the GPU build's
|
The Pixel 8a's CPU frequency scaling, with its own battery-limiter caps, and its GPU. These are the board-file parts of akita's M5 (speed) in omarchy-mobile, plus the GPU table moved into
zuma.dtsifor both boards. They follow zuma-husky, on top of #158 (CPU DVFS, thermal) and #157's GPU commits.The levels: the CPUs point at
zuma.dtsi's three tables. The levels and their powers are the 8a's own: stock'spixel-emdefault profile on this phone lists the same frequencies and microwatts.The 8a's caps: as you said on Pixel 8 Pro CPU DVFS: zuma's CPU levels from the ECT and CPU thermal zones (stacked on #157) #158, its battery current limiter is lower than the 8 Pro's: 1475, 1549 and 2147 MHz on VDROOP1, VDROOP2 and the SMPL warning (Google's
zuma-akita-bcl.dtsi). So the board file addsturbo-modeto the six levels above those caps, by node path:With boost off, the tops are 1425, 1418 and 2147 MHz.
The board file can only add marks, not remove them, so this works because the 8a's caps are below the 8 Pro's on every cluster.
zuma.dtsi's comment now says so.zuma-husky.dtsintozuma.dtsi, next to the CPU tables, so both boards point at one table. The 8 Pro's DTB is the same before and after: decompiled withdtc -s, identical, phandles included; only the root's node order in the blob differs. Not booted on an 8 Pro.&cmu_g3dand&gpuas inzuma-husky.dts: ACPM's paired "gpu" clock and CMU_G3D's two gates, pointing at the shared table.zuma-akita-bcl.dtsicaps the 8a's GPU at 649 (batoilo), 723 (vdroop1), 580 (vdroop2) and 649 MHz (smpl_gm), all below 890. With no BCL driver nothing runs above stock's caps, so the board file deletes 807, 850 and 890 MHz by path, leaving ten levels from 150 to 723 MHz.Tested on a Pixel 8a from slot B (7.3.0-rc6; steps 1 to 4 on
317d87dc2with the commits as first posted, step 5 on26867fc4ewith these three), one change per boot:omamobileas it is (…g317d87dc2db0):gs101-acpm-tmu: 4 thermal zones, the first time the 8a reads its own SoC temperatures;CPU DVFS (
…g03e86b1eb814):schedutil,boost0;scaling_max_freq1425, 1418 and 2147 MHz, and the levels above them only underscaling_boost_frequencies;openssl speed sha256, against the bootloader's clocks): little +0 %, mid +33 %, big +84 %. Each cluster went to its top under load and back down within a second.All nine cores at full load for 180 s, logged every second, with a stop at 80 °C:
The GPU (
…g0b04e364a09c), with omarchy-mobile's package settingclk_acpm zuma_gpu_max_khz=890000as first posted:shader_present=0x1110055, CSF interface v2.8.0) and givesrenderD128;tools/phone-smokereads GPU ok, with 3 known error lines and 0 new.no regulator (mali)is one of them, as on the 8 Pro.The GPU at the 8a's cap (
…g9cf0719104a1, this head's tree, with omarchy-mobile#832's package atzuma_gpu_max_khz=723000):tools/phone-smokereads GPU ok, with 0 new error lines.What isn't covered:
tools/kernel-pr-check --build OUT --merge origin/omamobile, with the dtschema validator, passes everything:26867fc4e;checkpatch --strictwith no errors and no warnings;W=1and passdtbs_check, with no new warnings.🤖 Generated with Claude Code