mesa assume that all object is created inside mesa, but for
VK_OBJECT_TYPE_SWAPCHAIN_KHR type, when we use vulkan_wsi_layer,
the object structure is different from mesa object, so don't use
mesa original object logic.
Change-Id: Iaea7f18e094b1bd1d2c7a4f4e7ecea0b81d9866a
Signed-Off-by: Xuelian Bai <xuelian.bai@samsung.com>
*/
enum vk_queue_submit_mode submit_mode;
-#ifdef ANDROID
+#if defined(ANDROID) || defined(HAVE_TIZEN_PLATFORM)
mtx_t swapchain_private_mtx;
struct hash_table *swapchain_private;
#endif
vk_free2(&device->alloc, pAllocator, slot);
}
-#ifdef ANDROID
+#if defined(ANDROID) || defined(HAVE_TIZEN_PLATFORM)
static VkResult
get_swapchain_private_data_locked(struct vk_device *device,
uint64_t objectHandle,
{
VK_FROM_HANDLE(vk_private_data_slot, slot, privateDataSlot);
-#ifdef ANDROID
+#if defined(ANDROID) || defined(HAVE_TIZEN_PLATFORM)
/* There is an annoying spec corner here on Android. Because WSI is
* implemented in the Vulkan loader which doesn't know about the
* VK_EXT_private_data extension, we have to handle VkSwapchainKHR in the