Lines Matching defs:clear
74 * The LRZ fast-clear buffer is initialized to zeroes and read/written
76 * '0' means block has original depth clear value, and '1' means that the
79 * LRZ fast-clear conservatively clears LRZ buffer, at the point where LRZ is
80 * written the LRZ block which corresponds to a single fast-clear bit is cleared:
84 * This way it's always valid to fast-clear. On the other hand we disable
85 * fast-clear if depth clear value is not 0.0 or 1.0 because it may be worse
87 * actual depth clear value.
94 * This especially rises questions in context of fast-clear, if fast-clear
100 * and nothing special should be done for such depth clear values.
121 * - Cache for fast-clear buffer;
217 /* Be optimistic and unconditionally enable fast-clear in
253 * the normal case and enable fast clear even if the depth image doesn't
285 VkClearValue clear = clear_values[a];
286 cmd->state.lrz.depth_clear_value = clear;
288 (clear.depthStencil.depth == 0.f ||
289 clear.depthStencil.depth == 1.f);
322 /* We need a valid LRZ fast-clear base, in case the render pass contents
398 /* LRZ_CLEAR.fc_enable + LRZ_CLEAR - clears fast-clear buffer;
408 /* Even though we disable fast-clear we still have to dirty
409 * fast-clear buffer because both secondary cmdbufs and following
410 * renderpasses won't know that fast-clear is disabled.
432 /* Enable flushing of LRZ fast-clear and of direction buffer */
452 * reason to do such clear.
525 * so we just pick the first one with depth cleared and clear the LRZ.