On 15 February 2014 17:30, Srikanth Thokala <sthokal@xxxxxxxxxx> wrote: > The current implementation of interleaved DMA API support multiple > frames only when the memory is contiguous by incrementing src_start/ > dst_start members of interleaved template. > > But, when the memory is non-contiguous it will restrict slave device > to not submit multiple frames in a batch. This patch handles this > issue by allowing the slave device to send array of interleaved dma > templates each having a different memory location. > How fragmented could be memory in your case? Is it inefficient to submit separate transfers for each segment/frame? It will help if you could give a typical example (chunk size and gap in bytes) of what you worry about. Thanks, Jassi -- To unsubscribe from this list: send the line "unsubscribe dmaengine" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
