Repository navigation
cpufreq: apple: Add T6050 profile with explicit thermal ownership - #249
Closed
DjDeveloperr wants to merge 1 commit into
Closed
DjDeveloperr wants to merge 1 commit into
DjDeveloperr wants to merge 1 commit into
Conversation
Port the command-state profile without replacing newer transition and thermal protections. Require a boot-producer assertion that retained firmware thermal control is qualified for every published OPP. Keep voltage, PLL and firmware throttling configuration inherited. Do not invent a safe frequency ceiling or add the assertion during generic DT migration. Hardware transition qualification remains pending. Signed-off-by: Dj <hey@djdev.me>
Contributor
Author
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.
Add the private T6050 command-state DVFS profile while preserving the newer public transition verification, failed-transition poisoning and thermal policies on existing SoCs. The profile supports five-bit OPP IDs supplied by DT and a conservative 2000 us transaction bound; command readback is not measured frequency.
Require
apple,firmware-managed-thermalon the matched cluster. The boot producer must retain active firmware thermal control and qualify it for every published OPP, including after PMP reinitialization. The driver refuses registration without that contract. This does not invent a safe frequency ceiling, program voltage/PLL controls, or assert that current M5 hardware is qualified. The guest-DT migration tool deliberately does not add the assertion.Validation: native arm64 driver object, binding validation and whitespace checks passed. Frequency transitions and firmware thermal ownership require hardware qualification before enabling this profile on a boot tree. No GPU changes.
Stacked on #248 for review ordering; DVFS has no display-driver dependency.