From: Vinod Koul <vinod.koul@intel.com>
To: Frank Mori Hess <fmh6jj@gmail.com>
Cc: dmaengine@vger.kernel.org,
Dan Williams <dan.j.williams@intel.com>,
linux-kernel@vger.kernel.org
Subject: [v5] dmaengine: pl330: flush before wait, and add dev burst support.
Date: Wed, 25 Apr 2018 14:46:27 +0530 [thread overview]
Message-ID: <20180425091627.GM6014@localhost> (raw)
On Wed, Apr 18, 2018 at 08:31:06PM -0400, Frank Mori Hess 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.
Applied, thanks
WARNING: multiple messages have this Message-ID (diff)
From: Vinod Koul <vinod.koul@intel.com>
To: Frank Mori Hess <fmh6jj@gmail.com>
Cc: dmaengine@vger.kernel.org,
Dan Williams <dan.j.williams@intel.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5] dmaengine: pl330: flush before wait, and add dev burst support.
Date: Wed, 25 Apr 2018 14:46:27 +0530 [thread overview]
Message-ID: <20180425091627.GM6014@localhost> (raw)
In-Reply-To: <1643219.q45jaR7ETT@bear>
On Wed, Apr 18, 2018 at 08:31:06PM -0400, Frank Mori Hess 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.
Applied, thanks
--
~Vinod
next reply other threads:[~2018-04-25 9:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-25 9:16 Vinod Koul [this message]
2018-04-25 9:16 ` [PATCH v5] dmaengine: pl330: flush before wait, and add dev burst support Vinod Koul
-- strict thread matches above, loose matches on Subject: below --
2018-04-19 0:31 [v5] " Frank Mori Hess
2018-04-19 0:31 ` [PATCH v5] " Frank Mori Hess
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180425091627.GM6014@localhost \
--to=vinod.koul@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=fmh6jj@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.