Skip to content

Comments

QCLINUX: qcom.config: Enable CPUidle Teo and Menu governors#707

Open
maulik-k-shah wants to merge 1 commit intoqualcomm-linux:tech/all/configfrom
maulik-k-shah:for-config
Open

QCLINUX: qcom.config: Enable CPUidle Teo and Menu governors#707
maulik-k-shah wants to merge 1 commit intoqualcomm-linux:tech/all/configfrom
maulik-k-shah:for-config

Conversation

@maulik-k-shah
Copy link
Contributor

Menu governor gets default enabled if Teo governor is not compiled in. Menu still stays as default governor when both are compiled in due to menu having higher rating than teo.

Keeping Teo available helps in evaluating power and performance without spinning builds.

Enable both menu and teo governors for CPUidle.

Menu governor gets default enabled if Teo governor is not compiled
in. Menu still stays as default governor when both are compiled in
due to menu having higher rating than teo.

Keeping Teo available helps in evaluating power and performance
without spinning builds.

Enable both menu and teo governors for CPUidle.

Signed-off-by: Maulik Shah <maulik.shah@oss.qualcomm.com>
@qcomlnxci qcomlnxci requested a review from a team February 20, 2026 05:05
@quic-bjorande
Copy link
Contributor

So, I guess the middle part of your commit message is your actual problem statement? Which is "I sometimes need to rebuild the kernel for testing with Teo governor and that takes several minutes" so the suggestion is to enable it for everyone every build even if nobody else is expected to use it?

It's possible that I'm missing the usefulness of the Teo governor, but you can solve that by describing why this should be enabled - in your commit message.

Also consider that the "most significant bit" of information in your commit message is talking about how the Kconfig and governor selection works, which seems to me to be an almost irrelevant piece of side story. Might be useful to include at the tail end to let the reviewer know that this won't affect the choice of governor...

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.

2 participants