drm/i915: Stop forcing clock gating init for future platforms
authorMatt Roper <matthew.d.roper@intel.com>
Wed, 6 Sep 2023 23:47:34 +0000 (16:47 -0700)
committerMatt Roper <matthew.d.roper@intel.com>
Fri, 8 Sep 2023 22:45:07 +0000 (15:45 -0700)
commit7ed888fa78129941255af09eddbf4cc51a3351d1
tree00428de5cedd54ea19ef0eecce10e3c3a658b573
parent231b1d6c9ab6ff23f7a1826835946dd2b0f57156
drm/i915: Stop forcing clock gating init for future platforms

In the early days of i915, pretty much every platform needed to
initialize _something_ in the clock gating init functions.  In some
cases the items initialized were inside the GT (and really should have
been initialized through the GT workaround infrastructure instead).
In other cases they were display programming (sometimes not even related
to "clock gating" at all!) which probably needs to move inside the
display-specific code.  The number of initialization tasks that are
truly "clock gating" and don't fall within the GT or display domains is
relatively limited.  Let's stop forcing future platforms to always
define a clock gating init hook.

Signed-off-by: Matt Roper <matthew.d.roper@intel.com>
Reviewed-by: Lucas De Marchi <lucas.demarchi@intel.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20230906234732.3728630-7-matthew.d.roper@intel.com
drivers/gpu/drm/i915/intel_clock_gating.c