From mboxrd@z Thu Jan 1 00:00:00 1970 From: vkoul@infradead.org (Vinod Koul) Date: Sun, 11 Sep 2011 21:32:46 +0530 Subject: [PATCH] dmaengine: add CSR SiRFprimaII DMAC driver In-Reply-To: References: <1315374075-15479-1-git-send-email-Baohua.Song@csr.com> <438BB0150E931F4B9CE701519A4463010871804A46@bgsmsx502.gar.corp.intel.com> <438BB0150E931F4B9CE701519A4463010871804A48@bgsmsx502.gar.corp.intel.com> <1315518378.6638.2.camel@vkoul-mobl4> Message-ID: <1315756966.2246.3.camel@vkoul-mobl4> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Fri, 2011-09-09 at 16:18 +0800, Barry Song wrote: > 2011/9/9 Vinod Koul : > > On Thu, 2011-09-08 at 10:55 +0530, Jassi Brar wrote: > >> On Thu, Sep 8, 2011 at 8:47 AM, Jassi Brar wrote: > Jassi prefer to use a transfer type instead of a control command. > though we will not really change the interleaved setting for every > transfer(it is more possible for one device, we will not change the > xlen/ylen/dma_width setting in the whole life period), i do believe > the transfer type is enough flexible for my possible applications to > change xlen, ylen and dma_width in different transfers. Is this usually the assumption or yours is a special case, how about your's Jassi? -- ~Vinod Koul Intel Corp.