drm/i915: Make shadow tables range-based

Browse source

Rather than defining our shadow tables as a list of individual
registers, provide them as a list of register ranges; we'll have some
ranges of multiple registers being added soon (and we already have a
couple adjacent registers that we can squash into a single range now).

This change also defines the table with hex literal values rather than
symbolic register names; since that's how the tables are defined in the
bspec, this change will make it easier to review the tables overall.

v2:
 - Force signed comparison on range overlap sanity check

Signed-off-by: Matt Roper <matthew.d.roper@intel.com>
Reviewed-by: Caz Yokoyama <caz.yokoyama@intel.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20210729152158.2646246-1-matthew.d.roper@intel.com

...

This commit is contained in:

Matt Roper 2021-07-29 08:21:58 -07:00

parent 39afa4104b

commit f9d56cd64e

4 changed files with 108 additions and 103 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

13

drivers/gpu/drm/i915/gt/intel_workarounds.c

View file

160

drivers/gpu/drm/i915/intel_uncore.c

View file

6

drivers/gpu/drm/i915/intel_uncore.h

View file

34

drivers/gpu/drm/i915/selftests/intel_uncore.c

View file