Skip to content

tu/a7xx: Don't set FLUSH_PER_OVERLAP_AND_OVERWRITE for feedback loops

Danylo Piliaiev requested to merge Danil/mesa:turnip/feature/a7xx-no-prim-mode-for-feedback-loop into main

What does this MR do and why?

A7XX doesn't have the same issue with UBWC flag buffer coherency as A6XX has.

Though for VK_EXT_rasterization_order_attachment_access we still have to set prim mode to flushing since it allows not to explicitly synchronize between writes and reads.

Passes:

 dEQP-VK.pipeline.*feedback_loop*

Merge request reports