mirrors/pipewire
1
0
Fork 0
mirror of https://gitlab.freedesktop.org/pipewire/pipewire.git synced 2025-12-14 08:56:37 -05:00
Code Issues Projects Releases Packages Wiki Activity Actions

doc: Clarify size properties wrt DMA-BUFs

Browse source
This commit is contained in:
columbarius 2022-03-08 23:45:26 +01:00
parent ca5e0e5837
commit 8dccfbce4c
1 changed files with 9 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

9
doc/dma-buf.dox
View file

@ -138,6 +138,15 @@ because of the following issues:
using a proper graphics API (such as EGL, Vulkan or VA-API) to process the using a proper graphics API (such as EGL, Vulkan or VA-API) to process the
DMA-BUFs. DMA-BUFs.
# Size of DMA-BUFs
When importing a DMA-BUF with a proper graphics API the size of a single buffer plane
is no relevant property since it will be derived by the driver from the other properties.
Therefore consumers should ignore the field `maxsize` of a `spa_data` and the field
`size` of a `spa_chunk` struct. Producers are allowed to set both to 0.
In cases where mapping a single plane is required the size should be obtained locally
via the filedescriptor.
# v4l2 # v4l2
Another use case for streaming via DMA-BUFs are exporting a camera feed from v4l2 Another use case for streaming via DMA-BUFs are exporting a camera feed from v4l2