summaryrefslogtreecommitdiff
path: root/scripts/Makefile.thinlto
diff options
context:
space:
mode:
authorVille Syrjälä <ville.syrjala@linux.intel.com>2026-08-26 16:40:33 +0300
committerVille Syrjälä <ville.syrjala@linux.intel.com>2026-08-27 14:04:58 +0300
commit050e8067dcb8f5787be41753832d4a023d0ffe74 (patch)
tree4e2d4f5c53cb36d929fbe374f0e0d2f518be4388 /scripts/Makefile.thinlto
parent22d664affc4384cb82580d7448c0263b875e5122 (diff)
downloadlinux-next-050e8067dcb8f5787be41753832d4a023d0ffe74.tar.gz
linux-next-050e8067dcb8f5787be41753832d4a023d0ffe74.zip
drm/i915/cdclk: Hoist intel_cdclk_{pre,post}_notify() calls upwards
Now that intel_cdclk_{pre,post}_notify() are implemented via vfuncs there is no need to keep them inside the .set_cdclk() hooks. Move the calls one level up to intel_cdclk_set_cdclk(). We do need to adjust {skl,bxt}_cdclk_(un)init_hw() to call the wrapper rather than the low level implementation directly, or else they would not do the pcode notification anymore. The two slight functional changes here are: - bdw_set_cdclk() might theoretically bail out after doing the pre notification, but that codepath would only come into play if the hardware is seriously misprogrammed, so should never happen - cdclk hw readout is still done from .set_cdclk(), so that now happens before the post notify vs. previously the readout happened before it. This should not matter as the readout is not affected by the post notify (since we can't actually read out anything from pcode). Reviewed-by: Jani Nikula <jani.nikula@intel.com> Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com> Link: https://patch.msgid.link/20260826134033.13976-15-ville.syrjala@linux.intel.com
Diffstat (limited to 'scripts/Makefile.thinlto')
0 files changed, 0 insertions, 0 deletions