pan/midgard: Allow COMPUTE jobs in panfrost_bo_access_for_stage
Fixes: ada752afe4
("panfrost: Extend the panfrost_batch_add_bo() API to pass access flags")
Signed-off-by: Alyssa Rosenzweig <alyssa.rosenzweig@collabora.com>
This commit is contained in:
@@ -108,11 +108,17 @@ struct panfrost_bo {
|
|||||||
uint32_t gpu_access;
|
uint32_t gpu_access;
|
||||||
};
|
};
|
||||||
|
|
||||||
|
/* If a BO is accessed for a particular shader stage, will it be in the primary
|
||||||
|
* batch (vertex/tiler) or the secondary batch (fragment)? Anything but
|
||||||
|
* fragment will be primary, e.g. compute jobs will be considered
|
||||||
|
* "vertex/tiler" by analogy */
|
||||||
|
|
||||||
static inline uint32_t
|
static inline uint32_t
|
||||||
panfrost_bo_access_for_stage(enum pipe_shader_type stage)
|
panfrost_bo_access_for_stage(enum pipe_shader_type stage)
|
||||||
{
|
{
|
||||||
assert(stage == PIPE_SHADER_FRAGMENT ||
|
assert(stage == PIPE_SHADER_FRAGMENT ||
|
||||||
stage == PIPE_SHADER_VERTEX);
|
stage == PIPE_SHADER_VERTEX ||
|
||||||
|
stage == PIPE_SHADER_COMPUTE);
|
||||||
|
|
||||||
return stage == PIPE_SHADER_FRAGMENT ?
|
return stage == PIPE_SHADER_FRAGMENT ?
|
||||||
PAN_BO_ACCESS_FRAGMENT :
|
PAN_BO_ACCESS_FRAGMENT :
|
||||||
|
Reference in New Issue
Block a user