vulkan: Blacklist MSAA path renderer on Qualcomm drivers

Bug: skia:7758
Change-Id: I96b5c259352949d67f5e0263a7164cdce54b3269
Reviewed-on: https://skia-review.googlesource.com/117152
Reviewed-by: Derek Sollenberger <djsollen@google.com>
Reviewed-by: Greg Daniel <egdaniel@google.com>
Commit-Queue: Chris Dalton <csmartdalton@google.com>

1 files changed, 3 insertions, 0 deletions

diff --git a/src/gpu/GrCaps.cpp b/src/gpu/GrCaps.cpp
index 0507a3fdfb..933292dea8 100644
--- a/src/gpu/GrCaps.cpp
+++ b/src/gpu/GrCaps.cpp
@@ -91,6 +91,7 @@ GrCaps::GrCaps(const GrContextOptions& options) {
 #endif
     fBufferMapThreshold = options.fBufferMapThreshold;
     fBlacklistCoverageCounting = false;
+    fBlacklistMSAAPathRenderer = false;
     fAvoidStencilBuffers = false;
 
     fPreferVRAMUseOverFlushes = true;
@@ -102,6 +103,7 @@ void GrCaps::applyOptionsOverrides(const GrContextOptions& options) {
         // We always blacklist coverage counting on Vulkan currently. TODO: Either stop doing that
         // or disambiguate blacklisting from incomplete implementation.
         // SkASSERT(!fBlacklistCoverageCounting);
+        SkASSERT(!fBlacklistMSAAPathRenderer);
         SkASSERT(!fAvoidStencilBuffers);
         SkASSERT(!fAdvBlendEqBlacklist);
     }
@@ -173,6 +175,7 @@ void GrCaps::dumpJSON(SkJSONWriter* writer) const {
 
     writer->appendBool("Blacklist Coverage Counting Path Renderer [workaround]",
                        fBlacklistCoverageCounting);
+    writer->appendBool("Blacklist MSAA Path Renderer [workaround]", fBlacklistMSAAPathRenderer);
     writer->appendBool("Prefer VRAM Use over flushes [workaround]", fPreferVRAMUseOverFlushes);
     writer->appendBool("Avoid stencil buffers [workaround]", fAvoidStencilBuffers);