summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/bin
diff options
context:
space:
mode:
authorMatt Roper <matthew.d.roper@intel.com>2026-09-24 14:08:42 -0700
committerMatt Roper <matthew.d.roper@intel.com>2026-09-25 08:16:21 -0700
commit923bab365da28fdae995d08e67fbc2aa3eff1c6c (patch)
tree7e18dd63721cc05a70c6b3a5b72c40db5f5b0bfe /tools/perf/scripts/python/bin
parentd5b0bf3f37f152583a884c696cf6caa152aa7ed5 (diff)
downloadlinux-923bab365da28fdae995d08e67fbc2aa3eff1c6c.tar.gz
linux-923bab365da28fdae995d08e67fbc2aa3eff1c6c.zip
Revert "drm/xe: Set mask bits for CCS_MODE register"
This reverts commit 23ea2c7572d4735ef66beb1e4feb8ae510b78247. A recent bspec update dropped the details about CCS_MODE being a masked register (i.e., bits [15:0] are only updated by register writes when the corresponding bit in [31:16] mask is also set by the write) on Xe2 and later. Apparently the documented mask bits were never actually implemented in hardware, so all register writes will update all bits of [15:0], just as the register behaved on Xe1 platforms. Setting the non-existent mask bits in Xe didn't have any negative impact since none of our existing code was trying to use the mask to limit which bits were updated. However this could have caused problems in the future if we ever rework this code in a way that tried to rely on the masking behavior. Update the register definition and drop the use of the mask to align with the new bspec definition and avoid potential mistakes in the future. Bspec: 55887 Cc: Balasubramani Vivekanandan <balasubramani.vivekanandan@intel.com> Reviewed-by: Daniel Charles <daniel.charles@intel.com> Link: https://patch.msgid.link/20260924-ccs_mode_drop_mask-v1-1-5b2b35708b83@intel.com Signed-off-by: Matt Roper <matthew.d.roper@intel.com>
Diffstat (limited to 'tools/perf/scripts/python/bin')
0 files changed, 0 insertions, 0 deletions