]> git.ipfire.org Git - thirdparty/linux.git/commit
drm/i915/uncore: Do GT FIFO checks in early sanitize and forcewake get
authorVille Syrjälä <ville.syrjala@linux.intel.com>
Mon, 23 Mar 2026 10:16:09 +0000 (12:16 +0200)
committerVille Syrjälä <ville.syrjala@linux.intel.com>
Fri, 27 Mar 2026 11:08:32 +0000 (13:08 +0200)
commite012fa31f90de0928d85ab22d9cc5fc8fe84c5b0
treece0aa136c160f3432ab8570f5648403a1036ebd1
parentfde38b106d50f59f904c72544aa34e41adb14fcb
drm/i915/uncore: Do GT FIFO checks in early sanitize and forcewake get

We're mixing up the GT FIFO debug checks (overflows and such)
with RMbus unclaimed register checks. The two are quite different
things as RMbus is only relevant for display registers, and the
GT FIFO only relevant for GT registers.

Split the GT FIFO debugs out from the unclaimed register logic
and just do the checks during forcewake_get() and early init.
That is still sufficient to detect if any errors have happened.

Any errors would anyway be caused by overflowing the FIFO
rather than accessing specific registers, so trying to figure
out exactly when the error happened isn't particularly useful.
To fix such issues we'd rather have to do something to slow down
the rate at which registers are accessed (eg. increase
GT_FIFO_NUM_RESERVED_ENTRIES or something).

Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
Link: https://patch.msgid.link/20260323101609.8391-3-ville.syrjala@linux.intel.com
Reviewed-by: Jani Nikula <jani.nikula@intel.com>
drivers/gpu/drm/i915/intel_uncore.c