diff options
author | Nanley Chery <nanley.g.chery@intel.com> | 2024-04-26 17:11:13 -0400 |
---|---|---|
committer | Marge Bot <emma+marge@anholt.net> | 2024-06-06 23:57:52 +0000 |
commit | 53440554c48c4a7a82d850f4ec1f607faa1acd2d (patch) | |
tree | a4104dad415f900810c1052f14e6d5d5b189c504 /src/gallium/drivers/v3d/v3dx_job.c | |
parent | 26655a137f4cb05f2d03d5aeca2dc6b5eed5f619 (diff) |
In iris, use the CCS scale down factor to calculate the impact of CCS on
TBIMR tile sizes. Even though we fall back to a seemingly less accurate
method to calculate the impact of CCS, it ends up giving the same
answer, 1bpp. Anv already uses this factor, so this patch replaces the
constant with this macro.
There are two benefits to doing this:
1) Consistency between anv and iris.
2) Preparation for a future where we no longer use ISL surfaces to
describe CCS on Xe+. In fact, in iris, we already don't create such
surfaces on ACM.
I considered using INTEL_AUX_MAP_MAIN_SIZE_SCALEDOWN for the calculation
in both drivers, but the naming is aux-map specific and the scaledown
actually exists on flat-ccs platforms as well.
So, we introduce a new macro for all Xe platforms, currently only used
for the specific use case of TBIMR calculations. We can add more such
macros for future platforms, as needed.
Reviewed-by: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
Reviewed-by: Rohan Garg <rohan.garg@intel.com>
Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/28942>
Diffstat (limited to 'src/gallium/drivers/v3d/v3dx_job.c')
0 files changed, 0 insertions, 0 deletions