C Specification
To determine the bind point requirements for a data graph pipeline session, call:
// Provided by VK_ARM_data_graph
VkResult vkGetDataGraphPipelineSessionBindPointRequirementsARM(
VkDevice device,
const VkDataGraphPipelineSessionBindPointRequirementsInfoARM* pInfo,
uint32_t* pBindPointRequirementCount,
VkDataGraphPipelineSessionBindPointRequirementARM* pBindPointRequirements);
Parameters
-
device
is the logical device that owns the data graph pipeline session. -
pInfo
is a pointer to a VkDataGraphPipelineSessionBindPointRequirementsInfoARM structure containing parameters for the bind point requirements query. -
pBindPointRequirementCount
is a pointer to an integer related to the number of bind point available or queried, as described below. -
pBindPointRequirements
is eitherNULL
or a pointer to an array of VkDataGraphPipelineSessionBindPointRequirementARM structures.
Description
If pBindPointRequirements
is NULL
, then the number of bind points
associated with the data graph pipeline session is returned in
pBindPointRequirementCount
.
Otherwise, pBindPointRequirementCount
must point to a variable set by
the user to the number of elements in the pBindPointRequirements
array, and on return the variable is overwritten with the number of
structures actually written to pBindPointRequirements
.
If pBindPointRequirementCount
is less than the number of bind points
associated with the data graph pipeline session, at most
pBindPointRequirementCount
structures will be written, and
VK_INCOMPLETE
will be returned instead of VK_SUCCESS
, to
indicate that not all the required bind points were returned.
Document Notes
For more information, see the Vulkan Specification
This page is extracted from the Vulkan Specification. Fixes and changes should be made to the Specification, not directly.