Lines Matching refs:allocation

180 described as having a height of 1080, with the memory allocation for each buffer
233 buffer-allocation interface available at either kernel or userspace level, the
234 client makes an arbitrary choice of allocation interface such as Vulkan, GBM, or
237 Each allocation request must take, at a minimum: the pixel format, a list of
239 this set of properties in different ways, such as allowing allocation in more
244 allocation, any padding required, and further properties of the underlying
250 After allocation, the client must query the allocator to determine the actual
272 memory. For this reason, each import and allocation API must provide a separate
314 In the latter case, the allocation is as discussed above, being provided with a
343   - during allocation, a user may supply ``DRM_FORMAT_MOD_INVALID``, either as the
346     used, or as part of a larger list to declare that an allocation using implicit
348   - in a post-allocation query, an implementation may return
365 allocation using implicit modifiers, or allocate the buffer for media use
376 ``DRM_FORMAT_MOD_LINEAR`` for their allocation, as this is the universal baseline