intel/fs: Re-order logical surface arguments
It makes more sense to start at the surface then move on to the address and then the data. Also, this is a really good test of whether or not we got all the places that use the sources by explicit integer number. Reviewed-by: Caio Marcelo de Oliveira Filho <caio.oliveira@intel.com>
This commit is contained in:
parent
94f8fd9a0c
commit
494a0543e6
|
@ -852,12 +852,12 @@ enum tex_logical_srcs {
|
|||
};
|
||||
|
||||
enum surface_logical_srcs {
|
||||
/** Surface binding table index */
|
||||
SURFACE_LOGICAL_SRC_SURFACE,
|
||||
/** Surface address; could be multi-dimensional for typed opcodes */
|
||||
SURFACE_LOGICAL_SRC_ADDRESS,
|
||||
/** Data to be written or used in an atomic op */
|
||||
SURFACE_LOGICAL_SRC_DATA,
|
||||
/** Surface binding table index */
|
||||
SURFACE_LOGICAL_SRC_SURFACE,
|
||||
/** Surface number of dimensions. Affects the size of ADDRESS */
|
||||
SURFACE_LOGICAL_SRC_IMM_DIMS,
|
||||
/** Per-opcode immediate argument. For atomics, this is the atomic opcode */
|
||||
|
|
Loading…
Reference in New Issue