Repository navigation
Conversation
The T8132 PMP thermal driver runs one policy on every M4 Mac on the
firmware path: the die guard (cooling from 106 C, target 110 C, full
protection 115 C, shutdown after three samples at 120 C) plus the
fanless MacBook Air's measured-rail energy budget, a 600 J burst at up
to 20 W, then 8 W regulated toward an 85 C filtered die with a 4 W
floor.
On the J604 (MacBook Pro 14-inch, M4) that budget defeats the fan,
whose speed the SMC appears to set from the heat the SoC makes. With
ten busy loops for 180 s on Aurora's linux-aurora 7.3.0.aurora1-37
package, the burst ran out after 53 s, the P and E rails (PP0b + PPbb)
fell from up to 22.7 W to 5-12 W, the heatpipe power (PHPC) from up to
28 W to 8-17 W, and 19 s later the SMC set the fan target to 0 for the
rest of the load. macOS 27.2 on the same Mac, same load: the fan ramps
from 2500 rpm to its 6550 rpm maximum and never stops.
The J604's ADT gives the J713's die sensors and limits (temp-sensor: a
110 C target and a 125 C maximum on Ta000m, Te000m, Te001m, Tp000m,
Tp001m, Tp002m), so the die guard applies as it is. Keep it and drop
the budget on the J604: the rails are still read and reported, a rail
fault or a telemetry gap still selects full protection and recovers
one step per second, but sustained power no longer restricts. The Airs
keep the budget unchanged.
Tested on a J604 whose Linux stub runs the 26.6.2 OS firmware, AC,
power profile performance, the same load; stock is Aurora's
linux-aurora 7.3.0.aurora1-37 package, "this commit" is
integration/aurora of 2026-11-14 plus this commit:
stock this commit
P+E rails, 60-180 s 7.7 W mean 16.4 W mean
fan target 0 from 72 s never 0 once started;
3710 rpm at 120 s, 4460
at 170 s
die, 60-180 s (1 Hz) mean 80 C mean 104 C, max 109.5 C
Over 15 minutes of the same load the fan reached about 5600 rpm at
6 min and 5900 at 15 min, the P and E rails about 17.6 W, the die a
102 C mean (highest sample in the driver log 110.25 C). At idle the
fan is off. The CPU is now held by the die guard, not by power.
Assisted-by: LLM
Signed-off-by: Friedrich <261542475+aeries0x@users.noreply.github.com>
|
Tested on a second J604: the Mac from #1931, with OS firmware 26.6.2 like yours. With this PR the fan runs for the whole load, and P+E holds about 13.7 W where the stock budget allowed 7.7 W. Method as yours: ten shell busy loops after 120 s idle, held for 180 s, sampled at about 1 Hz from sysfs and the
This fixes what I reported in #1931 on this Mac. I'll close that issue once this lands. Disclosure: an LLM (Claude) ran these boots and measurements on my Mac and drafted this. I reviewed it and am responsible for it. Assisted-by: LLM |
|
Thanks for the clear write-up and the J604 measurements. In this tree we select behaviour by a hardware property rather than a machine list. The new policy is chosen by Could the "unbudgeted" policy be selected from the device tree instead? For example, it could apply when the SMC hwmon node describes a fan (the J604 one-fan description in #1953 adds exactly that), or when a small If it helps, we can run thermal rows on our fan-cooled M1 Pro and M4 Pro to check that the shared policy code is unchanged there. |
|
The two J604 rows here, yours and the one from #1931, show the budget is what stops the fan. With this PR P+E holds 13.7 W where it was 7.7 W, and the fan keeps running. One request on how the policy is chosen. The reason for dropping the budget is that the machine has a fan the SMC runs on the SoC's heat. That is a property of the hardware, and the device tree already describes it: the fan node under
That keeps the policy tied to what the board has, so it does not grow into a board list as more fan machines run on this driver. The KUnit case does not need to change. |
On the J604 (MacBook Pro 14-inch, M4),
apple-pmp-thermalapplies the fanless Airs' energy budget: a 600 J burst at up to 20 W, then 8 W regulated toward an 85 °C filtered die, with a 4 W floor. The SMC appears to set the fan speed from the heat the SoC makes, so under a sustained all-core load the budget starves the fan: it stops during the load and the CPU stays at 5-9 W (7.7 W mean). #1931 reports the same on another J604.This PR drops the budget on the J604 and keeps the die guard as it is. The Airs and the other fan Macs (J773g, J623, J624) are unchanged (question 1).
Changes, on
apple,j604only:apple_pmp_power_init_unbudgeted(): the rails are still read and reported (power_statusshowsbudget=0, the hwmon sum channel is labelled "CPU/GPU rail sum"). A rail fault or a telemetry gap still selects full protection and recovers one step per second; sustained power never restricts.temp-sensorhas the J713's limits: 110 °C target and 125 °C maximum on Ta000m, Te000m, Te001m and Tp000m-Tp002m.apple_pmp_power_release(), shared by both paths; the Airs run the same arithmetic as before.Tested
J604 (Mac16,1, Linux stub on the 26.6.2 OS firmware), AC, power profile performance. Kernel:
integration/aurorabe8d4cd plus this commit, with #1888 (the J604 speaker enable) reverted locally so the test kernel keeps the speakers off; Stage 2: aura 1.0.0b12.1 + U-Boot aurora11. Stock: Aurora'slinux-aurora7.3.0.aurora1-37 package with aura 1.0.0b13.1 (same budget logic as this base). Load: ten shell busy loops after two minutes idle, sampled at about 1 Hz from sysfs. No SMC writes. "P+E" is PP0b + PPbb, without the GPU rail.compute.heavy, depth 8) for 180 s: P+E 12.7 W, GPU 5.4 W, die mean 104 °C, max 109.5 °C, fan 2550 -> 4790 rpm, never 0; no GPU or other new error in the kernel log.--strictand a W=1 LLVM build of both changed files: clean. Aurora's host tests: same results as the base. The KUnit case builds; it was not run on a kernel.Without the budget, the die guard sets the limit. It steps both clusters together and its 108 °C backstop reacts to short peaks, so under this load P runs at about 3.47 GHz and E at 2.17 GHz. In one trial with the J604 guard 2 °C higher (not part of this PR), the same 180 s load gave 17.3 W P+E and 6200 rpm at 170 s, with a hottest sample of 110.75 °C.
Questions
!apple_t8132_air()or a helper int8132.h), or stay on the budget until someone measures them?pmp-power-policy.h(burst, sustainable power, regulation target) over a flag, if more boards will need a budget with different numbers?Assisted-by: LLM