drm/i915: Don't use DRM_DEBUG_WARN_ON for unexpected l3bank/mslice config
authorTvrtko Ursulin <tvrtko.ursulin@intel.com>
Thu, 5 May 2022 11:00:06 +0000 (12:00 +0100)
committerTvrtko Ursulin <tvrtko.ursulin@intel.com>
Fri, 6 May 2022 07:53:25 +0000 (08:53 +0100)
commite6c2db2be986158afb9991d9fa8a38fe65a88516
tree6e991ade05170868767483aefc411b9b13d673b3
parent56ca3117f77a23a8b24e73e458bc85c11e5dea31
drm/i915: Don't use DRM_DEBUG_WARN_ON for unexpected l3bank/mslice config

DRM_DEBUG_WARN_ON should only be used when we are certain CI is guaranteed
to exercise a certain code path, so in case of values coming from MMIO
reads we cannot be sure CI will have all the possible SKUs and parts.

Use drm_warn instead and move logging to init phase while at it.

v2:
 * GEM_WARN_ON in intel_gt_get_valid_steering.

Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
Cc: Matt Roper <matthew.d.roper@intel.com>
Cc: Jani Nikula <jani.nikula@intel.com>
Reviewed-by: Matt Roper <matthew.d.roper@intel.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20220505110007.943449-1-tvrtko.ursulin@linux.intel.com
drivers/gpu/drm/i915/gt/intel_gt.c