tu: Don't CONCURRENT_BIN_DISABLE when there is no depth image
We have to disable CB when lrz fast-clear is disabled, but if there is no depth image at all, we can keep it enabled. This means that RP without depth won't effectively be a CB barrier. Signed-off-by: Danylo Piliaiev <dpiliaiev@igalia.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/38378>
This commit is contained in:
committed by
Marge Bot
parent
ee4f375bfd
commit
f2fb8ad422
@@ -2791,8 +2791,9 @@ tu7_emit_concurrent_binning(struct tu_cmd_buffer *cmd, struct tu_cs *cs,
|
||||
/* LRZ can only be cleared via fast clear in BV. Disable CB if we can't
|
||||
* use it.
|
||||
*/
|
||||
tu7_cb_disable_reason(!cmd->state.lrz.fast_clear, cmd,
|
||||
"LRZ fast clear disabled") ||
|
||||
tu7_cb_disable_reason(
|
||||
(!cmd->state.lrz.fast_clear && cmd->state.lrz.image_view), cmd,
|
||||
"LRZ fast clear disabled") ||
|
||||
tu7_cb_disable_reason(TU_DEBUG(NO_CONCURRENT_BINNING), cmd,
|
||||
"TU_DEBUG(NO_CONCURRENT_BINNING)")) {
|
||||
tu_cs_emit_pkt7(cs, CP_THREAD_CONTROL, 1);
|
||||
|
||||
Reference in New Issue
Block a user