On Mon, Apr 09, 2018 at 08:41:18PM -0400, Frank Mori Hess wrote: > On Tue, Mar 13, 2018 at 2:34 PM, Frank Mori Hess <fmh6jj@xxxxxxxxx> wrote: > > Do DMAFLUSHP _before_ the first DMAWFP to ensure controller > > and peripheral are in agreement about dma request state before first > > transfer. Add support for burst transfers to/from peripherals. In the new > > scheme, the controller does as many burst transfers as it can then > > transfers the remaining dregs with either single transfers for > > peripherals, or with a reduced size burst for memory-to-memory transfers. > > Hi, what is the state of this patch? I just noticed in patchwork it > is now listed as "Not applicable"? The original broken-by-wordwrap > patch is listed as "Accepted"? > > https://patchwork.kernel.org/project/linux-dmaengine/list/?submitter=178687&state=* That is not correct state, my script would update as not applicable when it doesn't find patch in my queue.. > I found it has a bug handling dregs btw, I'll include a fix for that > in the next version or as a follow-on patch as appropriate. Looks like I have missed this one somehow, so please update the patch with fix and I shall look into it. Thanks -- ~Vinod -- 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
