Re: [RFC] dmaengine: Add metadata_ops for dma_async_tx_descriptor

2018-08-16 Thread Peter Ujfalusi
Radhey, On 2018-08-16 16:29, Radhey Shyam Pandey wrote: >> +/** >> + * enum dma_desc_metadata_mode - per descriptor metadata mode types >> supported >> + * @DESC_METADATA_CLIENT - the metadata buffer is allocated/provided by >> the >> + * client driver and it is attached (via the >> dmaengine_de

RE: [RFC] dmaengine: Add metadata_ops for dma_async_tx_descriptor

2018-08-16 Thread Radhey Shyam Pandey
> -Original Message- > From: Peter Ujfalusi > Sent: Wednesday, August 15, 2018 4:27 PM > To: dan.j.willi...@intel.com; vk...@kernel.org > Cc: dmaeng...@vger.kernel.org; linux-kernel@vger.kernel.org; > l...@metafoo.de; Radhey Shyam Pandey > Subject: [RFC] dmaengine:

[RFC] dmaengine: Add metadata_ops for dma_async_tx_descriptor

2018-08-15 Thread Peter Ujfalusi
The metadata is best described as side band data or parameters traveling alongside the data DMAd by the DMA engine. It is data which is understood by the peripheral and the peripheral driver only, the DMA engine see it only as data block and it is not interpreting it in any way. The metadata can b