Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support cpufreq for t6031 #367

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

dberlin
Copy link
Contributor

@dberlin dberlin commented Dec 1, 2023

This seems to work, and matches the info i can find.

Signed-off-by: Daniel Berlin [email protected]

This seems to work, and matches the info i can find.

Signed-off-by: Daniel Berlin <[email protected]>
@@ -262,6 +280,8 @@ const struct feat_t *cpufreq_get_features(void)
case T6021:
case T6022:
return t6020_features;
case T6031:
return t6031_features;

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

same as T6021/T6022?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For now, yes. I assume it will end up slightly different in the end, which is why i didn't reuse the struct.

@marcan
Copy link
Member

marcan commented Dec 3, 2023

I'm not comfortable merging this until we at least confirm via macOS HV trace that it does the same thing. Getting this wrong has bit us hard in the past (M2 core lockups on deep sleep) and it's a huge nightmare to debug.

We're going to need the HV for a lot of other stuff on M3 anyway, so there isn't much point in bringing up Linux cpufreq until that works.

@dberlin
Copy link
Contributor Author

dberlin commented Dec 3, 2023 via email

@dberlin
Copy link
Contributor Author

dberlin commented Dec 11, 2023

Note: I traced enough of the kext now to verify that this is at least as correct as the current other code :)

But I still agree we should basically leave it disabled until we have lots of other stuff working, just to eliminate variables.

@marcan marcan force-pushed the main branch 3 times, most recently from 4f95305 to 95d67cf Compare April 9, 2024 03:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants