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

kprofiles: Enable auto kprofiles for QGKI kernels #16

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

Conversation

Forenche
Copy link

*In QGKI kernels, CONFIG_DRM_MSM=y is exported from techpack/display/config/{board}disp.conf at build time rather than being enabled via defconfig as the display stack is now out of tree i.e. techpack/display. Thus the legacy way of checking if DRM_MSM is enabled or not does not work.
*Xiaomi also uses DRM_MSM instead of MI_DRM_NOTIFIER, which they used to in older kernel versions, which lets this config be enabled on Xiaomi devices too requiring no adaptation whatsoever.

Test: Enable CONFIG_AUTO_KPROFILES_MSM_DRM and build kernel, boot and check for the node.

*In QGKI kernels, `CONFIG_DRM_MSM=y` is exported from techpack/display/config/{board}disp.conf at build time rather than being enabled via defconfig as the display stack is now out of tree i.e. techpack/display. Thus the legacy way of checking if DRM_MSM is enabled or not does not work.
*Xiaomi also uses DRM_MSM instead of MI_DRM_NOTIFIER, which they used to in older kernel versions, which lets this config be enabled on Xiaomi devices too requiring no adaptation whatsoever.

Test: Enable CONFIG_AUTO_KPROFILES_MSM_DRM and build kernel, boot and check for the node.

Signed-off-by: Forenche <[email protected]>
Copy link
Collaborator

@cyberknight777 cyberknight777 left a comment

Choose a reason for hiding this comment

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

LGTM to me.

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