From a768da0a2f13548f159775cfaa9c3dbc44772a23 Mon Sep 17 00:00:00 2001 From: DarekM <149845949+aninmucek@users.noreply.github.com> Date: Wed, 18 Nov 2026 19:47:33 +0000 Subject: [PATCH 1/3] arm64: dts: exynos: google: zuma-akita: Add CPU DVFS with the 8a's caps 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> --- .../boot/dts/exynos/google/zuma-akita.dts | 69 +++++++++++++++++++ arch/arm64/boot/dts/exynos/google/zuma.dtsi | 4 +- 2 files changed, 71 insertions(+), 2 deletions(-) diff --git a/arch/arm64/boot/dts/exynos/google/zuma-akita.dts b/arch/arm64/boot/dts/exynos/google/zuma-akita.dts index 039eadf76c..2f1de22ab4 100644 --- a/arch/arm64/boot/dts/exynos/google/zuma-akita.dts +++ b/arch/arm64/boot/dts/exynos/google/zuma-akita.dts @@ -191,6 +191,75 @@ status = "okay"; }; +/* + * The CPU levels are zuma.dtsi's, the same as stock's on this phone, but + * the Pixel 8a's battery current limiter caps all three clusters lower + * than the Pixel 8 Pro's: 1475, 1549 and 2147 MHz on every droop and + * SMPL event (Google's zuma-akita-bcl.dtsi). There is no BCL driver here, + * so the levels above those caps are turbo-mode as well, off until boost + * is enabled: 1548 and 1704 MHz on the little cluster, 1572 to 1945 MHz + * on the mid one and 2294 MHz on the big one, on top of the 8 Pro's marks. + */ +&cpu0 { + operating-points-v2 = <&cpucl0_opp>; +}; + +&cpu1 { + operating-points-v2 = <&cpucl0_opp>; +}; + +&cpu2 { + operating-points-v2 = <&cpucl0_opp>; +}; + +&cpu3 { + operating-points-v2 = <&cpucl0_opp>; +}; + +&cpu4 { + operating-points-v2 = <&cpucl1_opp>; +}; + +&cpu5 { + operating-points-v2 = <&cpucl1_opp>; +}; + +&cpu6 { + operating-points-v2 = <&cpucl1_opp>; +}; + +&cpu7 { + operating-points-v2 = <&cpucl1_opp>; +}; + +&cpu8 { + operating-points-v2 = <&cpucl2_opp>; +}; + +&{/opp-table-cpucl0/opp-1548000000} { + turbo-mode; +}; + +&{/opp-table-cpucl0/opp-1704000000} { + turbo-mode; +}; + +&{/opp-table-cpucl1/opp-1572000000} { + turbo-mode; +}; + +&{/opp-table-cpucl1/opp-1836000000} { + turbo-mode; +}; + +&{/opp-table-cpucl1/opp-1945000000} { + turbo-mode; +}; + +&{/opp-table-cpucl2/opp-2294000000} { + turbo-mode; +}; + /* * The battery pack's EEPROM, as on the Pixel 8 Pro: an at,24c08 at 0x50 * (Google's zuma-akita-battery.dtsi, pack_bee). Byte 0x17 is the battery diff --git a/arch/arm64/boot/dts/exynos/google/zuma.dtsi b/arch/arm64/boot/dts/exynos/google/zuma.dtsi index 610a8901c8..da52fa5393 100644 --- a/arch/arm64/boot/dts/exynos/google/zuma.dtsi +++ b/arch/arm64/boot/dts/exynos/google/zuma.dtsi @@ -194,8 +194,8 @@ * (/sys/devices/system/cpu/cpufreq/boost). * * Those turbo-mode marks are the Pixel 8 Pro's caps, so the CPUs get - * operating-points-v2 in the board file. A board whose BCL caps are - * lower needs tables of its own. + * operating-points-v2 in the board file. A board whose caps are lower + * marks its extra levels turbo-mode by path, as zuma-akita.dts does. */ cpucl0_opp: opp-table-cpucl0 { compatible = "operating-points-v2"; From 15d3101ce27eec1c2293365aca9ec80e5240fd42 Mon Sep 17 00:00:00 2001 From: DarekM <149845949+aninmucek@users.noreply.github.com> Date: Wed, 18 Nov 2026 19:48:14 +0000 Subject: [PATCH 2/3] arm64: dts: exynos: google: zuma: Share the GPU's levels 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> --- .../boot/dts/exynos/google/zuma-husky.dts | 61 ------------------ arch/arm64/boot/dts/exynos/google/zuma.dtsi | 63 +++++++++++++++++++ 2 files changed, 63 insertions(+), 61 deletions(-) diff --git a/arch/arm64/boot/dts/exynos/google/zuma-husky.dts b/arch/arm64/boot/dts/exynos/google/zuma-husky.dts index 6f1c0d8417..daab4bfe84 100644 --- a/arch/arm64/boot/dts/exynos/google/zuma-husky.dts +++ b/arch/arm64/boot/dts/exynos/google/zuma-husky.dts @@ -161,67 +161,6 @@ constant-charge-current-max-microamp = <1485000>; }; - /* - * The GPU's levels: the shader rates of the Pixel 8 Pro's GPU DVFS - * table, each with its paired L2 rate through the ACPM "gpu" clock, - * up to stock's 890 MHz. gpu-thermal throttles them. - */ - gpu_opp: opp-table-gpu { - compatible = "operating-points-v2"; - - opp-150000000 { - opp-hz = /bits/ 64 <150000000>; - }; - - opp-302000000 { - opp-hz = /bits/ 64 <302000000>; - }; - - opp-337000000 { - opp-hz = /bits/ 64 <337000000>; - }; - - opp-376000000 { - opp-hz = /bits/ 64 <376000000>; - }; - - opp-419000000 { - opp-hz = /bits/ 64 <419000000>; - }; - - opp-467000000 { - opp-hz = /bits/ 64 <467000000>; - }; - - opp-521000000 { - opp-hz = /bits/ 64 <521000000>; - }; - - opp-580000000 { - opp-hz = /bits/ 64 <580000000>; - }; - - opp-649000000 { - opp-hz = /bits/ 64 <649000000>; - }; - - opp-723000000 { - opp-hz = /bits/ 64 <723000000>; - }; - - opp-807000000 { - opp-hz = /bits/ 64 <807000000>; - }; - - opp-850000000 { - opp-hz = /bits/ 64 <850000000>; - }; - - opp-890000000 { - opp-hz = /bits/ 64 <890000000>; - }; - }; - reserved-memory { #address-cells = <2>; #size-cells = <1>; diff --git a/arch/arm64/boot/dts/exynos/google/zuma.dtsi b/arch/arm64/boot/dts/exynos/google/zuma.dtsi index da52fa5393..c29ee69675 100644 --- a/arch/arm64/boot/dts/exynos/google/zuma.dtsi +++ b/arch/arm64/boot/dts/exynos/google/zuma.dtsi @@ -426,6 +426,69 @@ /* 2943, 2970 and 3015 MHz stay off, as on stock. */ }; + /* + * The GPU's levels: the shader rates of the Pixel 8 Pro's GPU DVFS + * table, each with its paired L2 rate through the ACPM "gpu" clock, + * up to stock's 890 MHz, its BCL cap on VDROOP1. gpu-thermal throttles + * them. A board whose caps are lower deletes its extra levels by path, + * as zuma-akita.dts does. + */ + gpu_opp: opp-table-gpu { + compatible = "operating-points-v2"; + + opp-150000000 { + opp-hz = /bits/ 64 <150000000>; + }; + + opp-302000000 { + opp-hz = /bits/ 64 <302000000>; + }; + + opp-337000000 { + opp-hz = /bits/ 64 <337000000>; + }; + + opp-376000000 { + opp-hz = /bits/ 64 <376000000>; + }; + + opp-419000000 { + opp-hz = /bits/ 64 <419000000>; + }; + + opp-467000000 { + opp-hz = /bits/ 64 <467000000>; + }; + + opp-521000000 { + opp-hz = /bits/ 64 <521000000>; + }; + + opp-580000000 { + opp-hz = /bits/ 64 <580000000>; + }; + + opp-649000000 { + opp-hz = /bits/ 64 <649000000>; + }; + + opp-723000000 { + opp-hz = /bits/ 64 <723000000>; + }; + + opp-807000000 { + opp-hz = /bits/ 64 <807000000>; + }; + + opp-850000000 { + opp-hz = /bits/ 64 <850000000>; + }; + + opp-890000000 { + opp-hz = /bits/ 64 <890000000>; + }; + }; + firmware { acpm_ipc: power-management { compatible = "google,zuma-acpm-ipc"; From 04945d17b80c9c0dd9016cf20ea0eb14102a7b9d Mon Sep 17 00:00:00 2001 From: DarekM <149845949+aninmucek@users.noreply.github.com> Date: Wed, 18 Nov 2026 19:48:35 +0000 Subject: [PATCH 3/3] arm64: dts: exynos: google: zuma-akita: Enable the GPU to 723 MHz 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> --- .../boot/dts/exynos/google/zuma-akita.dts | 28 +++++++++++++++++++ 1 file changed, 28 insertions(+) diff --git a/arch/arm64/boot/dts/exynos/google/zuma-akita.dts b/arch/arm64/boot/dts/exynos/google/zuma-akita.dts index 2f1de22ab4..3b5976eed4 100644 --- a/arch/arm64/boot/dts/exynos/google/zuma-akita.dts +++ b/arch/arm64/boot/dts/exynos/google/zuma-akita.dts @@ -187,6 +187,10 @@ }; }; +&cmu_g3d { + status = "okay"; +}; + &cmu_peric1 { status = "okay"; }; @@ -260,6 +264,30 @@ turbo-mode; }; +/* + * The GPU's levels are zuma.dtsi's, the same shader rates as stock's on + * this phone, but the Pixel 8a's BCL caps the GPU at 649 (batoilo), 723 + * (vdroop1), 580 (vdroop2) and 649 MHz (smpl_gm), below the 8 Pro's 890. + * With no BCL driver nothing runs above stock's caps, so the levels above + * the highest of them, vdroop1's 723 MHz, are deleted here. + */ +/delete-node/ &{/opp-table-gpu/opp-807000000}; +/delete-node/ &{/opp-table-gpu/opp-850000000}; +/delete-node/ &{/opp-table-gpu/opp-890000000}; + +/* + * The GPU's core clock is ACPM's paired "gpu" clock, which sets the shader + * (G3D) and L2 (G3DL2) domains together; coregroup and stacks stay on + * CMU_G3D's gates, as on the Pixel 8 Pro. + */ +&gpu { + clocks = <&acpm_ipc ZUMA_CLK_ACPM_GPU>, + <&cmu_g3d CLK_GOUT_G3D_COREGROUP>, + <&cmu_g3d CLK_GOUT_G3D_STACKS>; + operating-points-v2 = <&gpu_opp>; + status = "okay"; +}; + /* * The battery pack's EEPROM, as on the Pixel 8 Pro: an at,24c08 at 0x50 * (Google's zuma-akita-battery.dtsi, pack_bee). Byte 0x17 is the battery