dma_fence_array_create(9)

๐Ÿ“ฆ version 7.3.1, in nixpkgs unstable

๐ŸŒธ NAME ๐ŸŒธ

okay so bestie, this is dma_fence_array_create(9) from the Kernel API Manual โ€” and it's literally all about creating a custom fence array ๐Ÿ’…โœจ

dma_fence_array_create - Create a custom fence array ๐ŸŽ€

โœจ SYNOPSIS โœจ

the exact call, no cap:

struct dma_fence_array * dma_fence_array_create (int num_fences , struct
       dma_fence **fences , u64 context , unsigned seqno );

๐ŸŽ€ ARGUMENTS ๐ŸŽ€

  • num_fences [in] โ€” number of fences to add in the array ๐Ÿงฎ
  • fences [in] โ€” array containing the fences ๐Ÿฆ‹
  • context [in] โ€” fence context to use ๐ŸŽฏ
  • seqno [in] โ€” sequence number to use ๐Ÿ”ข

๐Ÿ’– DESCRIPTION ๐Ÿ’–

so the glow-up is: allocate a dma_fence_array object and initialize the base fence with dma_fence_init โœจ in case of error it returns NULL ๐Ÿ˜ญ

the caller should allocate the fences array with num_fences size and fill it with the fences it wants to add to the object. ownership of this array is taken, and dma_fence_put is used on each fence on release ๐Ÿซถ

and yes: if signal_on_any is true, the fence array signals if any fence in the array signals; otherwise it signals when all fences in the array signal ๐Ÿ‘‘ periodt.

๐ŸŒˆ SEE ALSO ๐ŸŒˆ


signed, sealed, slayed from the ./drivers/dma-buf source/version โ€” October 2026 โ€” for dma_fence_array_create(9) ๐Ÿ’–๐ŸŽ€โœจ

๐Ÿ“ฆ where this page comes from