diff options
author | Matt Roper <matthew.d.roper@intel.com> | 2023-02-09 15:22:28 -0800 |
---|---|---|
committer | Matt Roper <matthew.d.roper@intel.com> | 2023-02-10 12:08:58 -0800 |
commit | 4583d6beb04976dff3440b1efd2c5956997fd839 (patch) | |
tree | ce43f1e441366bc89807e35c74695f92f4989b3e /drivers/ptp | |
parent | a13af50d75bc266bc746a2ac2b38d597f08f4201 (diff) | |
download | linux-stable-4583d6beb04976dff3440b1efd2c5956997fd839.tar.gz linux-stable-4583d6beb04976dff3440b1efd2c5956997fd839.tar.bz2 linux-stable-4583d6beb04976dff3440b1efd2c5956997fd839.zip |
drm/i915/xehp: LNCF/LBCF workarounds should be on the GT list
Although registers in the L3 bank/node configuration ranges are marked
as having "DEV" reset characteristics in the bspec, this appears to be a
hold-over from pre-Xe_HP platforms. In reality, these registers
maintain their values across engine resets, meaning that workarounds
and tuning settings targeting them should be placed on the GT
workaround list rather than an engine workaround list.
Note that an extra clue here is that these registers moved from the
RENDER forcewake domain to the GT forcewake domain in Xe_HP; generally
RCS/CCS engine resets should not lead to the reset of a register that
lives outside the RENDER domain.
Re-applying these registers on engine resets wouldn't actually hurt
anything, but is unnecessary and just makes it more confusing to anyone
trying to decipher how these registers really work.
v2:
- Also move DG2's Wa_14010648519 to the GT list. (Gustavo)
Cc: Gustavo Sousa <gustavo.sousa@intel.com>
Signed-off-by: Matt Roper <matthew.d.roper@intel.com>
Reviewed-by: Gustavo Sousa <gustavo.sousa@intel.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20230209232228.859317-1-matthew.d.roper@intel.com
Diffstat (limited to 'drivers/ptp')
0 files changed, 0 insertions, 0 deletions