[Mesa-dev] [Bug 106646] Support VK_IMAGE_USAGE_STORAGE_BIT for WSI swapchain surfaces

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=106646

            Bug ID: 106646
           Summary: Support VK_IMAGE_USAGE_STORAGE_BIT for WSI swapchain
                    surfaces
           Product: Mesa
           Version: git
          Hardware: Other
                OS: All
            Status: NEW
          Severity: enhancement
          Priority: medium
         Component: Drivers/Vulkan/Common
          Assignee: mesa-dev at lists.freedesktop.org
          Reporter: bugs.freedesktop at haasn.xyz
                CC: airlied at freedesktop.org, chadversary at chromium.org,
                    daniel at fooishbar.org, jason at jlekstrand.net

It would appear as though RADV (and ANV, judging by the code) on both X11 and
Wayland only support the following hard-coded list of VkImageUsageFlags:

   caps->supportedUsageFlags =
      VK_IMAGE_USAGE_TRANSFER_SRC_BIT |
      VK_IMAGE_USAGE_SAMPLED_BIT |
      VK_IMAGE_USAGE_TRANSFER_DST_BIT |
      VK_IMAGE_USAGE_COLOR_ATTACHMENT_BIT;

Could we get VK_IMAGE_USAGE_STORAGE_BIT added to this list? Other Vulkan
implementations I looked at (NVIDIA and AMDVLK) both support it, and simply
adding it to the list seems to work just fine for me. (on RADV+X11, not sure
about ANV or Wayland)

Use case: I have a rendering pipeline (mpv/vlc/libplacebo) that may involve the
use of a compute shader during the final output step, in order to do HDR peak
detection. If the swapchain image supports STORAGE_BIT then I can directly
paint to screen without needing to allocate an intermediate texture and
roundtrip through a fragment shader unnecessarily.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/mesa-dev/attachments/20180525/279321d3/attachment.html>