Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
MIME-Version: 1.0
In-Reply-To: <2863317.1ZoR41yQkl@bear>
References: <20180311150151.GB15443@localhost> <2863317.1ZoR41yQkl@bear>
From:   Frank Mori Hess <fmh6jj@gmail.com>
Date:   Mon, 9 Apr 2018 20:41:18 -0400
Message-ID: <CAJz5OpdV1=L3fsQESZusAp8Cir9wE-VqPXqBa=zOGjBcPE78DA@mail.gmail.com>
Subject: Re: [PATCH v4] dmaengine: pl330: flush before wait, and add dev burst support.
To:     dmaengine@vger.kernel.org
Cc:     Vinod Koul <vinod.koul@intel.com>,
        Dan Williams <dan.j.williams@intel.com>,
        linux-kernel@vger.kernel.org
Content-Type: text/plain; charset="UTF-8"
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Tue, Mar 13, 2018 at 2:34 PM, Frank Mori Hess <fmh6jj@gmail.com> 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=*

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.