kprofiles: Enable auto kprofiles for QGKI kernels #16
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.
*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 ofMI_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.