diff options
| author | Alyssa Rosenzweig <[email protected]> | 2019-10-12 11:30:52 -0400 |
|---|---|---|
| committer | Alyssa Rosenzweig <[email protected]> | 2019-10-16 08:17:56 -0400 |
| commit | 01a78dbbabb5be3aef2d3856a8d06f524b5b4cfc (patch) | |
| tree | 718f849b9edf4c13733381e3de24fa05b3fab976 /src/gallium/drivers/panfrost | |
| parent | fd2216e1fda76b2274bac3c3bce6c5af2dea5fc1 (diff) | |
pan/midgard: Allow COMPUTE jobs in panfrost_bo_access_for_stage
Fixes: ada752afe40 ("panfrost: Extend the panfrost_batch_add_bo() API to pass access flags")
Signed-off-by: Alyssa Rosenzweig <[email protected]>
Diffstat (limited to 'src/gallium/drivers/panfrost')
| -rw-r--r-- | src/gallium/drivers/panfrost/pan_bo.h | 8 |
1 files changed, 7 insertions, 1 deletions
diff --git a/src/gallium/drivers/panfrost/pan_bo.h b/src/gallium/drivers/panfrost/pan_bo.h index 022a56d9ca3..78e9b7526e0 100644 --- a/src/gallium/drivers/panfrost/pan_bo.h +++ b/src/gallium/drivers/panfrost/pan_bo.h @@ -108,11 +108,17 @@ struct panfrost_bo { 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 panfrost_bo_access_for_stage(enum pipe_shader_type stage) { assert(stage == PIPE_SHADER_FRAGMENT || - stage == PIPE_SHADER_VERTEX); + stage == PIPE_SHADER_VERTEX || + stage == PIPE_SHADER_COMPUTE); return stage == PIPE_SHADER_FRAGMENT ? PAN_BO_ACCESS_FRAGMENT : |