Alejandro Piñeiro 7059708dcd broadcom/qpu_instr: wait is not a read or write vpm instruction ... For several schedule restrictions, we are checking if the instruction is using the vpm. So far it was implemented as being a read or a write of the vpm. But VPM wait (vpmwt) is not a read or a write (it is a wait until all pending writes finishes). This is relevant to implement peripheral accesses restrictions, as for some cases where vpm read|writes are allowed, vpmwt is not. Fixes: dEQP-VK.binding_model.descriptorset_random.sets8.constant.ubolimitlow.sbolimitlow.sampledimglow.outimgtexlow.noiub.nouab.vert.noia.0 On the sim, as it was raising an assert for wrong peripheral access. v2: simplify v3d_qpu_waits_vpm (Iago) Reviewed-by: Iago Toral Quiroga <itoral@igalia.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6498>		2020-08-31 15:02:42 +02:00
..
tests	delete autotools .gitignore files	2019-04-29 21:17:19 +00:00
meson.build	meson: use gnu_symbol_visibility argument	2020-06-01 18:59:18 +00:00
qpu_disasm.c	tree-wide: replace MAYBE_UNUSED with ASSERTED	2019-07-31 09:41:05 +01:00
qpu_disasm.h
qpu_instr.c	broadcom/qpu_instr: wait is not a read or write vpm instruction	2020-08-31 15:02:42 +02:00
qpu_instr.h	broadcom/qpu_instr: wait is not a read or write vpm instruction	2020-08-31 15:02:42 +02:00
qpu_pack.c	broadcom/qpu: set VC5_QPU_RADDR_A out of the switch at _pack_branch	2020-07-07 21:40:16 +02:00
qpu_validate.c