Repository navigation
soc: apple: clpc: T6041 Low Power mode - #1727
Merged
DjDeveloperr merged 1 commit intoNov 12, 2026
Merged
DjDeveloperr merged 1 commit into
DjDeveloperr merged 1 commit into
Conversation
Offer the M4 Max the low-power platform profile T6050 has. Its ADT carries macOS's Low Power mode CPU ceiling, cpu-low-power-frequency-max = 2808 MHz, the same value as T6050's: in low-power every cluster stays at or below the first table frequency at or above it (2868 MHz on the P clusters; the E cluster tops out below it). macOS's package power target in that mode is not measured on this SoC, so the profile has no power target here, and with no apple,smc phandle it reads no package power. The M4 Pro shares this CLPC table and compatible, and its value is not checked, so the ceiling is gated on the machine compatible, as the ANE cluster floor already is. Signed-off-by: AxxzyWasTaken <axxzytte@gmail.com>
DjDeveloperr
merged commit Nov 12, 2026
b822815
into
aurora-silicon:integration/aurora
7 checks passed
RyanTheTide
approved these changes
Nov 12, 2026
RyanTheTide
left a comment
Contributor
There was a problem hiding this comment.
Checked the probe gate and every low_power_khz use. Boards other than T6041 keep their old values, and T6050 is unchanged. Thanks for the power numbers.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Gives the M4 Max (T6041) the low-power platform profile that T6050 got in #1656: macOS's Low Power mode as
low-power, next tobalancedandperformance. power-profiles-daemon picks it up aspower-saver.What it does
cpu-low-power-frequency-max = 2808(MHz), the same value as T6050's. Inlow-powerevery cluster stays at or below the first table frequency at or above it: 2868 MHz on both P clusters. The E cluster tops out at 2592 MHz, below the ceiling, so it is unchanged.low_power_mwstays 0. The node has noapple,smcphandle either, so the profile is the ceiling only.apple,t6041-clpccompatible, and I haven't checked its ADT value. So the ceiling is gated on the machine compatible (newlow_power_machinefield,"apple,t6041"), the way the ANE cluster floor is gated on"apple,t6040". The M4 Pro gets no profile from this.Tested
J616c (MacBook Pro 16" M4 Max), 26.6.2 firmware, at EL2 through aura, 12 Nov, on my daily kernel (this commit on
integration/aurorac6e08489with #1664 and #1369):/sys/class/platform-profile/platform-profile-0: nameapple-clpc, choiceslow-power balanced performance;powerprofilesctllistspower-saver.low-power,scaling_max_freqis 2868000 / 2592000 / 2868000; back to 4512000 / 2592000 / 4512000 inbalanced.Idle is 5.2 W either way.
On this branch (the commit alone on current
integration/aurora028d7624):clpc.obuilds with LLVM=1 W=1 with no warnings, andtools/asahi/clpc-gpu-demand-tests.pypasses. Not booted alone, and not tested on a J614c or an M4 Pro.