Lines Matching full:metadata

167   **Optional: per descriptor metadata**
169   DMAengine provides two ways for metadata support.
173     The metadata buffer is allocated/provided by the client driver and it is
183     The metadata buffer is allocated/managed by the DMA driver. The client
185     the metadata and can directly update or read it.
187     Because the DMA driver manages the memory area containing the metadata,
191     metadata must not be accessed after issue_pending.
192     In other words: if the aim is to read back metadata after the transfer is
217          construct the metadata in the client's buffer
228       4. when the transfer is completed, the metadata should be available in the
237          engine's metadata area
238       3. update the metadata at the pointer
240          amount of data the client has placed into the metadata buffer
248          the pointer to the engine's metadata area
249       4. read out the metadata from the pointer
253      When DESC_METADATA_ENGINE mode is used the metadata area for the descriptor