Lines Matching full:metadata

156   **Optional: per descriptor metadata**
158   DMAengine provides two ways for metadata support.
162     The metadata buffer is allocated/provided by the client driver and it is
172     The metadata buffer is allocated/managed by the DMA driver. The client
174     the metadata and can directly update or read it.
176     Becasue the DMA driver manages the memory area containing the metadata,
180     metadata must not be accessed after issue_pending.
181     In other words: if the aim is to read back metadata after the transfer is
206          construct the metadata in the client's buffer
217       4. when the transfer is completed, the metadata should be available in the
226          engine's metadata area
227       3. update the metadata at the pointer
229          amount of data the client has placed into the metadata buffer
237          the pointer to the engine's metadata area
238       4. read out the metadata from the pointer
242      When DESC_METADATA_ENGINE mode is used the metadata area for the descriptor