tree 530a6e5f38e9d19734be0cd534ae041f25abb96a
parent 232d005adfa10f758ea3cfdca63b758d49080291
author Sandeep Shinde <sashinde@nvidia.com> 1562660262 +0530
committer Lenny Komow <lenny@lunarg.com> 1562865667 -0600

loader: Fix VK_KHR_surface_protected_capabilities

Loader is exposing VK_KHR_surface_protected_capabilities instance
extension support if one of the ICDs supports it.

An ICD, not supporting this extension, will not know about
VkSurfaceProtectedCapabilitiesKHR being passed as additional structure
to VkPhysicalDeviceSurfaceInfo2KHR in vulkan API
vkGetPhysicalDeviceSurfaceCapabilities2KHR().

Reset VkSurfaceProtectedCapabilitiesKHR.supportsProtected to false
always before calling vkGetPhysicalDeviceSurfaceCapabilities2KHR(). If
a particular ICD supports protected surfaces then it will set it
true.

An application will always receive either 1/0 in supportsProtected as
expected.

The issue got exposed through below CTS test failure on a Optimus windows
system with different ICDs versions, one supporting this extension and
another not supporting it.

- dEQP-VK.wsi.win32.surface.query_protected_capabilities