[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJe_Zhc_GNNSDWNFuk+cMHEqxfSCJB_ey=Bf+SwJK-nS=u9ceg@mail.gmail.com>
Date: Mon, 17 Feb 2014 15:27:01 +0530
From: Jassi Brar <jaswinder.singh@...aro.org>
To: Srikanth Thokala <sthokal@...inx.com>
Cc: "Williams, Dan J" <dan.j.williams@...el.com>,
"Koul, Vinod" <vinod.koul@...el.com>, michal.simek@...inx.com,
grant.likely@...aro.org, robh+dt@...nel.org,
devicetree@...r.kernel.org, levex@...ux.com, lars@...afoo.de,
lkml <linux-kernel@...r.kernel.org>, dmaengine@...r.kernel.org,
andriy.shevchenko@...ux.intel.com,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH v3 1/3] dma: Support multiple interleaved frames with
non-contiguous memory
On 15 February 2014 17:30, Srikanth Thokala <sthokal@...inx.com> 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 linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists